- **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).
34 lines
873 B
Markdown
34 lines
873 B
Markdown
# SPEC: Changelog and Release Notes Process
|
|
|
|
## Overview
|
|
|
|
There's no changelog or release note process. Completed tasks produce a VERDICT.md but there's no aggregate record of what changed. This makes it hard to generate release notes or see the project's history at a glance.
|
|
|
|
## Changes
|
|
|
|
### 1. `CHANGELOG.md` at `~/.automaton/`
|
|
|
|
Root-level changelog file with entries appended on task completion:
|
|
|
|
```markdown
|
|
# Changelog
|
|
|
|
## [unreleased]
|
|
|
|
### Added
|
|
- description (#task-name)
|
|
|
|
### Fixed
|
|
- description (#task-name)
|
|
```
|
|
|
|
### 2. Update `.rules.md`
|
|
|
|
Add a rule: "When a task reaches Resolution (VERDICT.md written), append an entry to CHANGELOG.md."
|
|
|
|
## Acceptance Criteria
|
|
|
|
- [ ] `~/.automaton/CHANGELOG.md` exists with [unreleased] header
|
|
- [ ] `.rules.md` mentions changelog updates as part of task completion
|
|
- [ ] Format is clean enough to use as release notes source
|