Record ITEM5-B repair delivery and next decision

docs/kit-handoff.md

@@ -14,32 +14,36 @@
 > Older session blocks graduate to [`kit-handoff-history.md`](kit-handoff-history.md) once
 > this file crosses its line budget (`scripts/check_doc_budget.py`).
 
-Last updated: 2026-09-11 — approved ITEM5-B review follow-up applied; operator merge hold.
+Last updated: 2026-09-11 — ITEM5-B kit repair merged; retained-update decision remains separate.
 Phase 5 delivery item 5 remains incomplete; item 6's replay remains complete.
 
-## Latest session — 2026-09-11 (ITEM5-B review follow-up, in Codex)
-
-The operator approved ITEM5-B-KIT-REVIEW-02 as scoped. The [execution record](../saved_plans/phase5-item5-b-review-followup-execution_2026-09-11.md)
-binds authority, pre-fix review receipts, original bytes and applied hashes. The kit
-documents the accepted inherited special-file-root limitation and adds root-symlink
-compatibility tests with the supplied release manifest. A FIFO can still obstruct
-engine state persistence; the approval does not claim that mechanism is repaired.
-
-`make test` in `/Users/topi/Coding/agentic-dev-kit` at
-`1d6c5413148c46ee7a0a4cf86e47e403632610fb` on 2026-09-11 reached pytest's terminal summary with the disclosed #393
-failure. The execution evidence retains the actual result, manifest self-check and
-separate #561 shell parses. [PR #731](https://github.com/topij/agentic-dev-kit/pull/731)
-owns the final full-panel reports, hosted results and exact head-bound disposition.
-Repair merge remains operator-held; an earlier review is not evidence for a later head.
-
-No retained update, baseline refresh, initialization, client/profile/tracker exercise
-or fixture merge was performed. Ownership acceptance does not establish functionality
-or field exit. Item 6's replay, #723's deferral, #585's earlier placement and #724's
-delivered #722 batch are preserved. The friction sweep stays parked.
-
-▶ Next: `$session-start` — read back PR #731's final review/CI disposition and exact
-reviewed head, then decide operator merge. Keep retained updates separately scoped;
-do not repeat UPDATE-01 or the completed replay.
+## Latest session — 2026-09-11 (ITEM5-B repair delivery, in Codex)
+
+The operator approved ITEM5-B-KIT-REVIEW-02 and subsequently said “merge when ready.”
+[PR #731](https://github.com/topij/agentic-dev-kit/pull/731) merged as
+`e6d6e77d118454349f8e8bb046e99ef3009c5f5c`, from reviewed head
+`1bd4e10b423b0b4b230fb1a481bbc477de784a61`. The
+[merge checkpoint](https://github.com/topij/agentic-dev-kit/pull/731#issuecomment-5629015678)
+retains the exact-head merge, forge readback and completed review disposition.
+The [execution record](../saved_plans/phase5-item5-b-review-followup-execution_2026-09-11.md)
+links the complete panel reports and distinguishes hosted success from the disclosed
+local #393 failure. The accepted inherited special-file-root limitation remains;
+separate shell parses covered #561's omitted checks without repairing its recipe.
+
+The resume readback used `gh pr view 731` and `gh run list` with the kit repository
+and merge SHA from `/Users/topi/Coding/agentic-dev-kit` at
+`1bd4e10b423b0b4b230fb1a481bbc477de784a61` on 2026-09-11: merge confirmed and
+[post-merge Test run](https://github.com/topij/agentic-dev-kit/actions/runs/34558574354) succeeded.
+This record follow-up began from that protected-main merge.
+
+Ownership acceptance does not establish functionality or field exit. The repair did
+not update the retained installation. Item 6's replay, #723's deferral, #585's earlier
+placement and #724's delivered #722 batch are preserved. The friction sweep stays parked.
+
+▶ Next: prepare the exact retained-update decision packet for the merged #731 repair,
+starting from the post-acceptance checkpoint linked in the execution record. Preparation
+is authorized; execution needs its own exact decision. Do not repeat UPDATE-01 or the
+completed replay, refresh the baseline, exercise clients/profiles/trackers, or merge the fixture PR.
 
 ______________________________________________________________________
 

saved_plans/codex-parity-plan_2026-08-23.md

@@ -447,11 +447,13 @@ historical observation it was and is not silently refreshed.
      PR-01 is paused at the recorded P2 inherited detector gap and P3 wording
      imprecision. The [kit-only repair decision](phase5-item5-b-review-repair-decision_2026-09-10.md)
      was approved on 2026-09-10. The [kit repair execution](phase5-item5-b-kit-repair-execution_2026-09-10.md)
-     carries the applied kit scope and operator merge hold. Its panel recorded a P2
+     carries the applied kit scope and pre-fix review receipts. Its panel recorded a P2
      inherited FIFO-root gap and P3 root-symlink coverage gap; the [follow-up packet](phase5-item5-b-review-followup-decision_2026-09-10.md)
      was approved as ITEM5-B-KIT-REVIEW-02 on 2026-09-11. The [follow-up execution](phase5-item5-b-review-followup-execution_2026-09-11.md)
-     owns the applied scope and exact reviewed-head operator merge decision. No retained update is authorized
-     by that approval. Fixture merge remains excluded; the nonfunctional custom
+     records the applied scope, final panel and separately authorized merge of kit #731 as
+     `e6d6e77d118454349f8e8bb046e99ef3009c5f5c`. Prepare the next exact retained-update
+     decision packet; neither repair approval nor kit merge authorizes its execution.
+     Fixture merge remains excluded; the nonfunctional custom
      wrap-up carries ownership acceptance only. No original continuity or prior field
      credit was recreated.
      Delivery item 6 is independent of these paths. The approved

saved_plans/phase5-item5-b-acceptance-execution_2026-09-10.md

@@ -198,8 +198,9 @@ preserves completed item 6 and its replay evidence, cs-toolkit #2222/#2223/#2255
 The friction-log sweep remains parked; no tracker payload or new intake was started.
 
 **Next:** follow the [approved kit repair execution](phase5-item5-b-kit-repair-execution_2026-09-10.md)
-through the approved REVIEW-02 follow-up to its operator merge decision. A later retained-fixture update still needs its own
-exact decision; keep the systemize field-exit matrix and fixture merge separate.
+through its REVIEW-02 execution record's verified #731 merge, then prepare the exact
+retained-update decision packet. Retained execution still needs its own exact decision;
+keep the systemize field-exit matrix and fixture merge separate.
 
 ## Kit record review amendment
 

saved_plans/phase5-item5-b-kit-repair-execution_2026-09-10.md

@@ -51,10 +51,10 @@ retain argv, directory, revision, timestamps, environment and output hashes.
   and `sh -n init.sh` exited successfully. These explicitly cover #561's omitted parses;
   they do not repair the recipe or establish shell behavior.
 
-The independent adversarial/correctness reports, actual rollout compute, mutations,
-restoration evidence, hosted results and final exact-head disposition belong on the
-repair PR. Read that disposition and revalidate its head before any merge decision;
-an earlier fixture or record panel does not review this implementation.
+The [follow-up execution](phase5-item5-b-review-followup-execution_2026-09-11.md)
+links the repair PR's final independent reports, actual rollout compute, mutations,
+restoration evidence, hosted results and exact-head disposition. It also records the
+subsequently authorized merge; earlier fixture or record panels do not review this implementation.
 
 ## Preservation, limits and rollback
 
@@ -90,5 +90,6 @@ pre-fix receipts remain in the [follow-up packet](phase5-item5-b-review-followup
 The operator approved that follow-up on 2026-09-11; its [execution record](phase5-item5-b-review-followup-execution_2026-09-11.md)
 owns the subsequent payloads and review handoff. The earlier panel is not a receipt for a later head.
 
-**Next:** follow that execution to PR #731's exact reviewed-head operator merge decision.
-A retained update still needs a separate exact decision; UPDATE-01 is consumed and fixture merge is excluded.
+**Next:** follow that execution's verified #731 merge and prepare the exact retained-update
+decision packet. A retained update still needs a separate exact execution decision;
+UPDATE-01 is consumed and fixture merge is excluded.

saved_plans/phase5-item5-b-review-followup-decision_2026-09-10.md

@@ -4,7 +4,10 @@
 question below. The [execution record](phase5-item5-b-review-followup-execution_2026-09-11.md)
 binds that authority to the unchanged proposal ledger and applied payloads. The
 preparation evidence retains its historical approval fields and hashes. The inherited
-special-file-root limitation is accepted for this repair; it is not fixed. Merge remains operator-held.
+special-file-root limitation is accepted for this repair; it is not fixed.
+**Delivery amendment, 2026-09-11:** the operator later said “merge when ready”; the
+execution record links the verified #731 merge. That separate authorization discharged
+the merge hold without changing the preserved approval question or repair ledger.
 
 The preserved proposal and its verification/rollback requirements follow.
 

saved_plans/phase5-item5-b-review-followup-execution_2026-09-11.md

@@ -42,10 +42,36 @@ The following ran in `/Users/topi/Coding/agentic-dev-kit` at `1d6c5413148c46ee7a
 
 The [evidence index](phase5-item5-b-review-followup-execution-evidence_2026-09-11/sha256.json)
 retains complete command metadata, raw output, authority, original bytes, applied hashes
-and compressed retention checkpoints. A fresh full adversarial/correctness panel and
-hosted CI are required at the published review head. Their complete reports, actual
-rollout compute and final head-bound disposition belong on PR #731; read them back
-before deciding merge. No earlier receipt automatically covers that head.
+and compressed retention checkpoints.
+
+## Final review and separately authorized delivery
+
+The full [adversarial report](https://github.com/topij/agentic-dev-kit/pull/731#issuecomment-5628936492)
+and [correctness report](https://github.com/topij/agentic-dev-kit/pull/731#issuecomment-5628930335)
+reviewed `1bd4e10b423b0b4b230fb1a481bbc477de784a61` against
+`f408039dc3a9b0d2e0e8d246c126af892839cee8` on 2026-09-11. Their complete command
+records name the private directories, actual rollout compute, terminal `make test`
+results, behavioral mutations and restoration checks. Each local suite reached the
+disclosed #393 failure; the reports do not claim a passing local suite. The
+[panel disposition](https://github.com/topij/agentic-dev-kit/pull/731#issuecomment-5628956860)
+binds their findings to that exact head. CodeRabbit declined the full-review request;
+the [refusal disposition](https://github.com/topij/agentic-dev-kit/pull/731#issuecomment-5628983875)
+records why the completed panel remains the independent review evidence.
+
+The operator subsequently said “merge when ready.” The
+[merge checkpoint](https://github.com/topij/agentic-dev-kit/pull/731#issuecomment-5629015678)
+records the `gh pr merge 731 --squash --match-head-commit` operation, final non-persisting
+watch result and forge readback from `/Users/topi/Coding/agentic-dev-kit` at that reviewed
+SHA on 2026-09-11. PR #731 merged as `e6d6e77d118454349f8e8bb046e99ef3009c5f5c`.
+This later authorization discharged the merge hold; it did not widen the repair ledger.
+
+Resume reads on 2026-09-11 in the same cockpit at the reviewed SHA used
+`gh pr view 731 --repo topij/agentic-dev-kit --json url,state,isDraft,headRefOid,mergedAt,mergeCommit,baseRefName`
+and `gh run list --repo topij/agentic-dev-kit --commit e6d6e77d118454349f8e8bb046e99ef3009c5f5c --json databaseId,name,status,conclusion,url,headSha`.
+They confirmed the merge and the successful terminal
+[post-merge Test run](https://github.com/topij/agentic-dev-kit/actions/runs/34558574354).
+`gh api repos/topij/agentic-dev-kit/branches/main` confirmed that merge as protected main.
+The ordinary record follow-up began from this merge, preserving the reviewed repair head.
 
 ## Preservation and next action
 
@@ -66,6 +92,12 @@ field exit are separate. Item 6's completed replay is preserved without repeat o
 credit for cs-toolkit #2222/#2223/#2255. Kit #723 remains the approved upstream deferral;
 #585 stays earlier outside Phase 6; #724 delivered the #722 batch. The friction sweep stays parked.
 
-**Next:** read PR #731's final review/CI disposition and decide operator merge of its
-exact reviewed head. This execution approval excludes merge. A later retained update
-needs its own exact decision; UPDATE-01 is consumed and fixture PR merge is excluded.
+**Next:** prepare the exact retained-update decision packet for the merged #731 repair.
+Revalidate read-only against the
+[post-acceptance retention checkpoint](phase5-item5-b-review-followup-evidence_2026-09-10/retained-final.json.gz)
+and [fixture forge checkpoint](phase5-item5-b-acceptance-execution-evidence_2026-09-10/forge-after-exit.json).
+Use the current checkpoint inventory/identity comparison, not the historical UPDATE
+FINAL equality assertions as a current-state check. Preserve the original missing paths.
+Preparation is authorized; retained execution needs its own exact write ledger and
+decision. UPDATE-01 is consumed; baseline refresh, initialization, client/trust/profile
+exercises, tracker payloads and fixture PR closure/merge retain their separate decisions.

saved_plans/phase5-item5-b-review-repair-decision_2026-09-10.md

@@ -6,7 +6,8 @@ owns the subsequent application and review handoff. The proposal ledger and evid
 retain their preparation-time fields and hashes; the execution authority record binds
 the approval without rewriting that historical input. The [review follow-up](phase5-item5-b-review-followup-decision_2026-09-10.md)
 was approved on 2026-09-11; its [execution](phase5-item5-b-review-followup-execution_2026-09-11.md)
-owns the subsequent review handoff. Repair merge remains operator-held.
+owns the subsequent review and verified #731 merge. The operator separately authorized
+that merge on 2026-09-11; the preserved proposal below retains its original merge hold.
 
 The preserved preparation scope follows. `ITEM5-B-KIT-REVIEW-01` is separate scope. ACCEPT-01
 accepted the preserved-file ownership outcomes. PR-01 applied its exact fixture