diff options
Diffstat (limited to 'project_claudomator_claude_md_staleness.md')
| -rw-r--r-- | project_claudomator_claude_md_staleness.md | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/project_claudomator_claude_md_staleness.md b/project_claudomator_claude_md_staleness.md new file mode 100644 index 0000000..db6667d --- /dev/null +++ b/project_claudomator_claude_md_staleness.md @@ -0,0 +1,12 @@ +--- +name: claudomator-claude-md-staleness +description: "FIXED 2026-07-10 (commit 6214aa8) — CLAUDE.md's Story orchestrator section rewritten to describe the finished recursive arbitrated-review design" +metadata: + node_type: memory + type: project + originSessionId: 560b9055-7a3f-483e-b1a0-1a4c70419390 +--- + +**Status: fixed**, commit `6214aa8` on `main` (2026-07-10). `CLAUDE.md`'s "Story orchestrator" section now describes the actual current mechanism: builder-role nodes at any depth (root or nested) only reach `COMPLETED` via `finalizeArbitration`'s approval, the tree-walk trigger (`processStory`/`processBuilderNode`), `task.CurrentAttempt` resolution, root-vs-nested fix-attempt plumbing (`ensureFixAttempt` vs. `spawnNestedFixAttempt`), and `SeedRoleConfigs` seeding the `builder` role's prompt. The stale "Arbitration outcome always routes to REVIEW_READY" Design Debt entry was removed entirely (the gap it described — a dedicated verdict-reporting tool — was already closed before this session started). + +Original finding (2026-07-10, before the fix): the section described pre-piece-4a behavior (root auto-accepted eagerly on `READY`) and a since-closed Design Debt item, and didn't mention nested builder-role subtasks, `task.CurrentAttempt`, or `SeedRoleConfigs` at all. Every piece's plan this session updated `story_orchestrator.go`'s own doc comments carefully but never included a CLAUDE.md update step — worth remembering as a gap in plan-writing discipline generally, not just for this one file: **a plan that changes a subsystem's documented behavior should include a CLAUDE.md check as a step**, not rely on a separate retro to catch it later. |