Files
stack/docs/plans/CURRENT.md
T
jason.woltje 439bea6915 ui(test): green OK/PASS, red FAIL - terminal-only, NO_COLOR-aware
Owner feedback: grep match-highlighting made the word 'policy' red while
status words were plain - counter-indicative. Suites + verify now emit
ANSI colors (green success, red failure) when stdout is a terminal;
piped/machine-parsed output stays plain, honoring NO_COLOR. Word 'ok'
promoted to 'OK' for scannability.

Verified byte-level via forced-pty run; piped output unchanged; suites
41/24/14 + verify green.
2026-09-03 06:23:47 -05:00

2.1 KiB

CURRENT — single source of "what happens next"

This file always names exactly one next action. Any "continue" / "next" / "proceed" message means: execute the action below, fully (implement → test → verify against its acceptance criteria → commit → push → close the issue → update this file to the next action). No ambiguity, no re-planning.

Next action

Owner review of M9 (mission capability policy) — then name the next target.

Queue (ordered, not started)

  1. Run-record retention/pruning policy
  2. Second real adapter (parked — owner focused on Pi)
  3. Auto-apply policy for worker patches (capability policy now exists as its substrate)
  4. Session forking from a common ancestor (pi JSONL trees make this native)

Rules

  • One action in flight. Update this file at the END of every action.
  • Blocked? Move the item to "Blocked" below with the reason and stop.
  • Completed actions move to the log at the bottom (date + issue + result).

Blocked

(none)

Completed log

  • 2026-09-03 — M5 workspaces + capability envelope (#20, #21) — merged, tests green
  • 2026-09-03 — M6 named sessions + resume (#22, #23) — merged, teach/recall verified
  • 2026-09-03 — M7 run inspection + release 0.0.6 (#24) — merged, activated
  • 2026-09-03 — M8 conductor loop + worker-built retry (#25, #26, #27) — merged; worker authored retry in 2 refinement rounds, conductor fixed a 3-line interpolation rename; live retry verified
  • 2026-09-03 — retry lineage + relative mission resolution (#28) — merged, 36/24/14 suites + verify green
  • 2026-09-03 — M9 mission capability policy (#30) — merged, least-privilege intersection, 41/36/14 + verify green
  • 2026-09-03 — M8 conductor loop + worker-built retry (#25, #26, #27) — merged; worker authored retry in 2 refinement rounds, conductor fixed a 3-line interpolation rename; live retry verified
  • 2026-09-03 — retry lineage + relative mission resolution (#28) — merged, 36/24/14 suites + verify green
  • 2026-09-03 — M8 conductor loop + worker-built retry (#25, #26, #27) — merged; worker authored retry in 2 refinement rounds, conductor fixed a 3-line interpolation rename; live retry verified