4 Commits

Include renames

Author	SHA1	Message	Date
gitea	21f16b7da2	Fix verdict parsing + plug stale-task enforcement hole ... - task.py: remove naive substring fallback from parse_verdict_status(), only parse ## Status: header; no header → ambiguous (REFEREE) - status.py: add _auto_update_verdict_on_complete() — when transitioning human_intervention→complete, auto-update VERDICT.md to PASS - status.py: add stale-task detection to --can-edit — deny edits if all edit tasks have .state mtime >30 min old (reason: stale_task) - status.py: add --touch command to reset task activity clock - guard plugin: handle stale_task reason with specific error message - Update test to match new verdict parsing behavior	2026-06-15 21:55:17 -04:00
gitea	af66f5081d	Fix pre-existing issues and update README for v2.0 ... - Fix _infer_state_from_artifacts: SPEC-only maps to research (was bug_find) - Fix cmd_validate_folder: corrupted .state files now error instead of silent fallback - Fix upgrade.sh: remove || true, add python3 check, use git rev-parse --git-dir - Update README.md with --project flag, --can-edit modes, --upgrade, enforcement layers - Add 6 new tests for inference and validation fixes - Complete hook-install-process and readme-upgrade-docs tasks	2026-06-15 14:56:33 -04:00
gitea	05c76852a2	v2.0: state enforcement, project scoping, harness integration ... State Enforcement (v2.0): - .state file as single source of truth for task phase - Approval gates for research, decomposition, design, test_design - status.py --transition refuses illegal phase transitions - status.py --validate-folder detects out-of-order artifacts - status.py --audit checks all tasks for violations - status.py --create-task is the only valid way to create tasks - Pre-v2.0 tasks without .state are UNTRACKED -- all commands refuse them - New --upgrade command bootstraps .state files for existing tasks Project Scoping: - --project flag added to all status.py commands across 16+ files - _find_project_dir errors instead of silently falling back to ~/.automaton/ - --scope-check marks framework files OUT_OF_SCOPE when working on a project - Dashboard handlers use stored project_root instead of re-detecting from CWD - Prompts reference ~/.automaton/scripts/vram_detect.py (not {project}/.automaton/) Harness Integration: - status.py --can-edit now supports project-level checks (no --task required) - --can-edit --file checks file scope without --task - --json output for machine-readable harness integration - opencode plugin (plugins/automaton-guard/plugin.ts) intercepts edit/write - Git pre-commit hook (scripts/git-hooks/pre-commit) blocks commits without task - Formal integration contract (contracts/harness-integration.md) Other: - upgrade.sh delegates to status.py --upgrade instead of manual heuristics - Phase prompts reference --project {project} for multi-project scoping - 200 tests passing (14 new)	2026-06-15 14:16:46 -04:00
gitea	79b783864e	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	2026-06-14 11:24:36 -04:00