Harden framework: tests, VRAM Python, dashboard spec, security, CI
- 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
This commit is contained in:
@@ -0,0 +1,25 @@
|
||||
# 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.
|
||||
@@ -1,35 +0,0 @@
|
||||
# Contract: {task-name}
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] {Criterion 1: e.g., All tests pass}
|
||||
- [ ] {Criterion 2: e.g., Feature X works with empty input}
|
||||
- [ ] {Criterion 3: e.g., API returns correct status codes}
|
||||
- [ ] {Criterion 4: e.g., No new lint errors}
|
||||
- [ ] {Criterion 5: e.g., Documentation updated}
|
||||
|
||||
## Tests
|
||||
|
||||
- {List all tests that must pass}
|
||||
- {List any new tests that must be added}
|
||||
|
||||
## Screenshots (if UI)
|
||||
|
||||
- {Describe what screenshots are needed}
|
||||
|
||||
## Files Modified
|
||||
|
||||
- {List exact files changed}
|
||||
|
||||
## Risks & Mitigations
|
||||
|
||||
- {Risk 1}
|
||||
- Mitigation: {how to handle}
|
||||
|
||||
## Notes
|
||||
|
||||
- {Any additional notes or constraints}
|
||||
|
||||
## Stop Condition
|
||||
|
||||
When all checkboxes are checked and tests pass, output "CONTRACT_MET" and stop.
|
||||
Reference in New Issue
Block a user