- Rewrite vram_detect in Python with fixed config parsing and 10KB read limit
- Add pytest suite (72 tests) covering dashboard core, app security, and VRAM
- Standardize all prompts to .automaton/tasks/{task-name}/ path
- Reconcile dashboard spec with web implementation; remove themes.py
- Remove half-implemented refresh.py file watcher
- Harden dashboard static-file serving and task-name validation
- Add uncommitted-change guard to update.sh and real Gitea URLs
- Add AGENTS.md, Gitea CI workflow, and template documentation
26 lines
881 B
Markdown
26 lines
881 B
Markdown
# Task Templates
|
|
|
|
This directory contains example task structures for reference and testing.
|
|
|
|
## Templates
|
|
|
|
### `tasks/bad-impl/`
|
|
A deliberately broken task used to test the dashboard's handling of failed verdicts.
|
|
- Contains a `VERDICT.md` with `FAIL`.
|
|
- Useful for verifying that the dashboard correctly shows blocked tasks.
|
|
|
|
### `tasks/research-task/`
|
|
A minimal example of a research-phase task.
|
|
- Contains only a `SPEC.md`.
|
|
- Useful as a starting point for new research tasks.
|
|
|
|
### `tasks/subtask-parent/`
|
|
An example of a decomposed parent task with sub-tasks.
|
|
- Contains `SPEC.md` and `DECOMPOSITION.md`.
|
|
- Includes sub-task folders under `subtasks/`.
|
|
- Useful for testing sub-task visualization in the dashboard.
|
|
|
|
## Usage
|
|
|
|
These templates are not used automatically by the framework. Copy and adapt them when creating new tasks, or use them as fixtures for dashboard tests.
|