Files

T

Lap Tran bc7daf8590 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).

2026-06-26 10:05:18 -04:00

3.0 KiB

Raw Permalink Blame History

Implementation: Multi-Agent Support

Changes Made

1. Agent Configuration in `.agent.md`

Multi-agent mode is activated by adding an ## Agent Configuration section to .agent.md:

## Agent Configuration
Mode: multi-agent
Agents:
  - id: researcher
    phases: [research, decomposition, design, test_design]
  - id: implementer
    phases: [implement]
  - id: orchestrator
    phases: [new, complete, human_intervention]
    role: coordinator
Lock timeout: 30m

When this section is absent or Mode: single-agent (default), all multi-agent commands are no-ops.

2. Task claiming: `--claim` and `--release`

status.py --claim --task {name} --agent {id} creates .state.lock with agent ID, phase, claimed timestamp, and expiry
Atomic write (.state.lock.tmp → .state.lock)
Refuses if already claimed and not expired
Overclaims expired locks with warning
Validates agent is configured for the task's current phase
Default lock timeout: 30 minutes, configurable in .agent.md

3. Work discovery: `--next-available` and `--available`

--next-available --agent {id} returns the highest-priority unclaimed task matching the agent's allowed phases
Priority: tasks closest to completion first (referee > doc_review > ... > research > new)
--available --agent {id} lists all matching tasks
In single-agent mode, both return a message directing to --list

4. Single-agent zero-overhead guarantee

When no Agent Configuration exists, --claim, --release, --next-available, --available are no-ops or return guidance messages
No .state.lock files are created in single-agent mode
No performance overhead, no behavioral change from v1

5. Coordinator role

Agent with role: coordinator can:
- Claim tasks on behalf of other agents (--claim --agent {target} --as-coordinator)
- Force-release claims (--release --as-coordinator)
- Force-transition (--transition {phase} --force)

6. Lock expiry and conflict resolution

Locks expire after configurable timeout (default 30 min)
Any agent can overclaim expired locks
Atomic lock writes prevent race conditions
Locks auto-release on complete and human_intervention transitions

7. Role binding in phase prompts

When multi-agent mode is active and --agent is provided, status.py --task includes agent-specific ALLOWED/FORBIDDEN sections
Phase prompts include ## Agent Role section when agent is role-bound
TASK_HANDOFF signal defined for when agent can't perform a required phase

Files Modified

scripts/status.py (multi-agent commands implemented)
tests/test_status.py (existing tests cover single-agent; multi-agent requires Agent Configuration to test)

Notes

Multi-agent is opt-in: zero config changes needed for single-agent usage
The phase prompt ## Agent Role section is documented in the multi-agent-support/SPEC.md but will be dynamically generated by status.py --task output when multi-agent is active
Dashboard integration for multi-agent status display is future work

3.0 KiB Raw Permalink Blame History