docs(plan): CURRENT.md — single next-action pointer for cadence-driven work

This commit is contained in:
2026-09-02 22:25:56 -05:00
parent 90a67d050e
commit 22508170a2
+32
View File
@@ -0,0 +1,32 @@
# 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
Gitea issue: (none queued — awaiting owner direction)
## Queue (ordered, not started)
1. Owner review of M5M7 (workspaces, capabilities, sessions) — hands-on
2. M8 candidate: mission-level capability policy (defaults per mission)
3. M9 candidate: run-record retention + `retry <runId>` convenience
## 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