claudomator.git/docs, branch main

docs: fix workflow diagram — create_story does not auto-spawn a builder task

2026-07-11T09:52:47+00:00

The StoryOrchestrator skips stories with no root_task_id (if st.RootTaskID == "") so create_story / POST /api/stories do not trigger Builder spawning on the next tick as the diagram incorrectly claimed. Corrected the flowchart node, the entry-point table rows, and added an explanatory note on the story lifecycle kickoff flow. Co-Authored-By: Claude Sonnet 4.6

docs: fix workflow diagram — webhook and spawn_subtask don't auto-submit to pool

2026-07-11T07:46:30+00:00

- GitHub webhook (createCIFailureTask) only calls store.CreateTask with PENDING state; it never calls Pool.Submit. Previous diagram said "creates task + auto-runs" which was wrong. - spawn_subtask (both role= and no-role= variants) only calls store.CreateTask with PENDING state via storeChannel.SpawnSubtask. The pool is not called. Previous diagram labelled this "Pool.Submit() for new child/sibling" which was wrong. - Both spawn_subtask variants always set parent_task_id. The "sibling with depends_on" description for the role= case was misleading. - propose_epic and propose_role_config are storage-only writes with no connection to the pool at all. Previous diagram drew arrows from these to executor.Pool; removed and replaced with a STORAGE node. - Added explicit note that PENDING children need a separate /run call (scripts/start-next-task, StoryOrchestrator.spawnRoleTask, or manual). - StoryOrchestrator's spawnRoleTask correctly creates + QUEUED + Pool.Submit in one step; that path remains accurate. Co-Authored-By: Claude Sonnet 4.6

docs: add workflow and entry points diagram

2026-07-11T01:19:24+00:00

Covers all entry points verified against current code: - REST API (POST /api/tasks + /run), chatbot MCP (submit_task, create_story, accept_story), GitHub webhook, Story REST API, agent spawn_subtask (parent_task_id vs depends_on/role paths), propose_epic, propose_role_config, StoryOrchestrator's internal spawning (ensureEvaluators/ensureArbitration/ensureFixAttempt/ spawnNestedFixAttempt/processRetro), Scheduler retry/escalation and ask_user-timeout escalation, claudomator run CLI. Includes task state machine diagram and recursive arbitrated-review cycle showing that builder-role READY means awaiting arbitration, not done. All diagrams use Mermaid (renders on GitHub). Co-Authored-By: Claude Sonnet 4.6

docs: rewrite piece 5 plan as a code-based SeedRoleConfigs (mirrors SeedProjects) instead of a manual API call

2026-07-10T20:17:33+00:00

docs: add implementation plan for recurse-processstory-tree-walk (piece 4b-3)

2026-07-10T06:30:02+00:00

docs: add piece 4b-3 plan (tree-walk arbitrated review)

2026-07-10T06:27:24+00:00

docs: add implementation plan for generalize-finalize-arbitration (piece 4b-2)

2026-07-10T03:30:37+00:00

docs: add implementation plan for nested-builder-completion-follows-arbitration (piece 4b-1)

2026-07-10T02:41:01+00:00

docs: fix piece-4a plan's Step 14 -- do not attempt git push in-container (lesson from piece 3's dispatch saga)

2026-07-09T20:44:45+00:00

docs: add implementation plan for root-completion-follows-arbitration (piece 4a)

2026-07-09T20:42:27+00:00