autonomous-sdlc-harness 0.6.2 → 0.6.4

package/templates/state-dir/user_reviews/README.md

@@ -2,7 +2,7 @@
 
 Two kinds of file under one root, both suffixed by round: the operator's hands-on review of a finished branch at `<branch>_review[_<n>].md`, and the fix plan it produces — a `<branch>_fix_plan[_<N>].md` index plus one `finding_<K>.md` per finding — written by the fix-plan writer and worked through by the implementers, reviewers and committer. Round 1 is unsuffixed and later rounds carry `_2`, `_3`, … A fix plan takes the **same** round number as the review it was written from, and its per-finding folder mirrors its index suffix exactly. So a `<branch>_fix_plan_2.md` found alone is round 2: it was written from `<branch>_review_2.md` in this directory, and its findings sit in `<branch>_fix_plan_2/finding_<K>.md` beside it.
 
-The review is written by hand after the hands-on pass, in the format `${CLAUDE_PLUGIN_ROOT}/samples/sample_user_review.md` fixes — or dropped through the unattended loop, which copies it here under its original name before launching the fix flow — or submitted on GitHub as a pull-request review requesting changes on the run's branch, which becomes the next round. Its layout — one section per review — every review requesting changes, and every other review that carries a summary — with a provenance line naming its state, each inline comment with its file, line, commit, author and diff hunk, and a closing marker line — is set by the `control` paragraph of `remote-run.sh`'s header in the configured scripts directory. The fix plan is the fix-plan writer's: it discovers the latest review here, derives both output paths from that round, and writes the index to the format `${CLAUDE_PLUGIN_ROOT}/samples/sample_user_review_fix_plan.md` fixes with per-finding files shaped like `${CLAUDE_PLUGIN_ROOT}/samples/sample_user_review_fix_plan/finding_1.md`. The drafted plan is then graded by the plan-review gates before any of its fixes is implemented, and walked item by item by the fix loop.
+The review is written by hand after the hands-on pass, in the format `${CLAUDE_PLUGIN_ROOT}/samples/sample_user_review.md` fixes — or dropped through the unattended loop, which copies it here under its original name before launching the fix flow — or submitted on GitHub as a pull-request review requesting changes on the run's branch, which becomes the next round. Its layout — one section per review — every review requesting changes, and every other review that carries a summary — with a provenance line naming its state, each inline comment with its file, line, commit, author and diff hunk, and a closing marker line — is set by the `control` paragraph of `remote-run.sh`'s header in the configured scripts directory. The fix plan is the fix-plan writer's: it discovers the latest review here, derives both output paths from that round, and writes the index to the format `${CLAUDE_PLUGIN_ROOT}/samples/sample_user_review_fix_plan.md` fixes with per-finding files shaped like `${CLAUDE_PLUGIN_ROOT}/samples/sample_user_review_fix_plan/finding_1.md`. For a round placed from a pull-request review, the fix plan records which collected inline comments each finding came from, and the run workflow's `deliver` step reads those lines when the round completes, to reply to and resolve the threads the round fixed. The drafted plan is then graded by the plan-review gates before any of its fixes is implemented, and walked item by item by the fix loop.
 
 The unattended drop for a **local** run deliberately does **not** commit the review — unlike a prompt or a checklist it is not a precondition of the first step, and the fix flow's own first commit stages the review beside the fix-plan index and its per-finding folder. A round for a run executing on GitHub — dropped, sent by the local command, or arriving as a pull-request review — is committed as `chore: add user review for <branch>` and pushed before its dispatch, because a job boundary before the fix flow's own commit would lose it. Nothing supersedes either file afterwards: a further round is written beside them under the next suffix, and the accumulated rounds are the branch's hands-on-review history. The whole directory is committed with the branch, since no ignore rule reaches it.