Restore archived tasks, fix dashboard scroll-reset, bind ornith, add Playwright smoke test
- **Restore 82 completed tasks** from tasks/complete/ back to tasks/ top level (all <7 days old per the cleanup policy; premature bulk archive was fixed). - **Dashboard: fix scroll-reset on auto-refresh** — renderBoard rebuilds the board via innerHTML every 2s, destroying each column-body's scrollTop. Now snapshots column-body scrollTop + board.scrollLeft + view.scrollTop before rebuild and restores after (matched by PHASE_GROUPS index). - **Dashboard UI additions** (pre-existing unstaged work): approval section cards, transition buttons, inline artifact editor (textarea for writing missing SPEC/VERDICT/etc from the detail modal). - **Bind ornith as Implement model** — config.md: Model explicit to omlx/Ornith-1.0-35B-4bit-mlx, context window 32768. Interactive autopilot already used ornith via opencode default; now explicit. - **Fix cleanup stub** — automaton-cleanup.sh had a stale --project arg pointing at a pytest temp dir (test isolation leak). Rewired to point at ~/.automaton. - **Fix plist-isolation test** — test asserted host plist doesn't exist, but a real install creates it. Now snapshots mtime before run, asserts unchanged after (only a write during the test counts as bleed). - **New Playwright smoke test** (tests/test_dashboard_ui.py) — 2 tests: board renders tasks, column scroll survives auto-refresh tick. Verified the test fails without the scroll fix (scrollTop resets to 0). Skipped via importorskip when playwright is absent (main CI stays green). - **Clarify SI loop scope in README** — new-project onboarding section documents the framework-scoped self-improvement loop and options (leave/pause/create project loop). - **CHANGELOG** documents all changes including the known model-divergence gap (mde tasks marked complete but per-role model binding was never implemented).
This commit is contained in:
@@ -0,0 +1 @@
|
||||
complete
|
||||
@@ -0,0 +1,17 @@
|
||||
# Implementation: Remove File System Watcher
|
||||
|
||||
## Summary
|
||||
Removed the half-implemented `refresh.py` file system watcher module and updated the dashboard README to reflect the actual client-side polling refresh mechanism.
|
||||
|
||||
## Files Changed
|
||||
- `automaton/dashboard/core/refresh.py` — deleted
|
||||
- `automaton/dashboard/README.md` — removed watcher from architecture diagram, fixed tree formatting
|
||||
|
||||
## Verification
|
||||
- `automaton/dashboard/core/refresh.py` no longer exists.
|
||||
- `python -m automaton.dashboard` still starts and refreshes via JS polling.
|
||||
- `python -m pytest tests/` still passes.
|
||||
|
||||
## Decisions
|
||||
- The dashboard uses client-side polling (`setInterval`) for auto-refresh.
|
||||
- No replacement watcher was implemented.
|
||||
@@ -0,0 +1,4 @@
|
||||
# Review
|
||||
- **Status**: approved
|
||||
- **Timestamp**: 2026-06-14T09:59:40.721019
|
||||
- **Comment**:
|
||||
@@ -0,0 +1,20 @@
|
||||
# SPEC: Remove File System Watcher
|
||||
|
||||
## Goal
|
||||
Resolve the half-implemented `refresh.py` module by removing it and documenting the polling-based refresh behavior.
|
||||
|
||||
## Requirements
|
||||
1. Delete `automaton/dashboard/core/refresh.py`.
|
||||
2. Update `automaton/dashboard/README.md` to state that auto-refresh uses client-side polling.
|
||||
3. Ensure no imports or references to `refresh.py` remain.
|
||||
|
||||
## Acceptance Criteria
|
||||
- [ ] `automaton/dashboard/core/refresh.py` does not exist.
|
||||
- [ ] `README.md` accurately describes the polling refresh mechanism.
|
||||
- [ ] `python -m automaton.dashboard` still starts and refreshes correctly.
|
||||
|
||||
## Non-Goals
|
||||
- Implementing Server-Sent Events or WebSocket push.
|
||||
|
||||
## Stop Condition
|
||||
When all acceptance criteria are met, output "CONTRACT_MET".
|
||||
@@ -0,0 +1,18 @@
|
||||
# Verdict: Remove File System Watcher
|
||||
|
||||
## Status: PASS
|
||||
**Completion Date**: 2026-06-14
|
||||
|
||||
## Summary
|
||||
The unused file system watcher module has been removed and documentation now accurately describes the polling-based refresh behavior.
|
||||
|
||||
## Findings
|
||||
- `refresh.py` deleted.
|
||||
- README architecture diagram cleaned up.
|
||||
- Tests still pass.
|
||||
|
||||
## Remaining Issues
|
||||
None.
|
||||
|
||||
## Score
|
||||
+10 PASS
|
||||
Reference in New Issue
Block a user