Add mandatory fresh WP04 implementation handover

handover/workpackages/20260905_1525_repository_convergence_issue_state_reconciliation.md

@@ -0,0 +1,177 @@
+# Handover — SCRUB-WP_REPOSITORY_CONVERGENCE_ISSUE_STATE_RECONCILIATION
+
+## Repository worked in
+
+`solidprivacy-nl/scrub`
+
+## Workpackage title
+
+`SCRUB-WP_REPOSITORY_CONVERGENCE_ISSUE_STATE_RECONCILIATION`
+
+Role: `implementation_operations`  
+Issue: #119  
+PR: #124  
+Branch: `wp/repository-convergence-issue-state-reconciliation-v2`  
+Exact starting main/base: `14baceb97b274de6ef35c42ce48441c4e74c5f08`
+
+## Status
+
+**RELEASE_CANDIDATE_READY subject to the mandatory final full `Tests` run on the handover-complete exact head and subsequent fresh blind independent assurance.**
+
+This handover is the final intended implementation file. The exact frozen candidate SHA is the PR #124 head produced by this handover commit. It must be read directly from GitHub and must not move after the final green full-suite run.
+
+## Business/current-truth outcome
+
+The governed recovery for the first WP04 release-ordering failure is complete and independently confirmed. The fresh retry now represents one narrow administrative reconciliation candidate from governed main rather than inheriting release authority from PR #120 or recovery PR #122.
+
+Reviewed disposition:
+
+### Keep open
+
+```text
+#96
+```
+
+#96 remains the residual Premium/App-Shell deployed live-verification gate. PR #104 V2, PR #108 marker/compact-placeholder repair and PR #111 Dutch-address precision repair are independently PASSed/merged, but the consolidated deployed live-app retest after both repairs **remains unproven**.
+
+### Close only after fresh PASS + guarded merge + exact-main verification
+
+```text
+#74 #75 #76 #77
+#79 #81 #84 #86 #88 #89
+#98 #100 #105
+#106 #107 #109 #112
+```
+
+No target issue in this set has been mutated by this implementation candidate.
+
+## Sequencing control
+
+The fresh retry intentionally uses a stricter action fence than the failed PR #120 lifecycle:
+
+```text
+exact candidate
+→ full exact-head Tests
+→ fresh blind governance_release_assurance
+→ PASS
+→ guarded merge of the exact reviewed head
+→ exact-main Tests + GitHub→Hugging Face verification
+→ only then close the reviewed 17 issues and reconcile #96 body while keeping it OPEN
+→ read back every issue state
+→ close #119 only after administrative outcome confirmation
+```
+
+This makes exact-main post-merge confirmation a prerequisite for target issue mutation.
+
+## Files added/changed
+
+Expected handover-complete PR #124 scope relative to base:
+
+```text
+CHANGELOG.md
+REPOSITORY_CONVERGENCE_DEBT_LEDGER.md
+RISK_REGISTER.md
+WORKPACKAGES.md
+handover/workpackages/20260905_1525_repository_convergence_issue_state_reconciliation.md
+tests/test_repository_convergence_issue_state_reconciliation_contracts.py
+tests/test_repository_convergence_issue_state_reconciliation_recovery_contracts.py
+workpackage_claims/SCRUB-WP_REPOSITORY_CONVERGENCE_ISSUE_STATE_RECONCILIATION.md
+workpackage_claims/SCRUB-WP_REPOSITORY_CONVERGENCE_ISSUE_STATE_RECONCILIATION_GOVERNANCE_RECOVERY.md
+```
+
+No application/runtime/UI/recognizer/profile/review/export/Scrub Key/reinsert/document-processing/dependency/workflow implementation file is intentionally changed.
+
+## Implementation summary
+
+- `WORKPACKAGES.md` records WP-CONVERGENCE-04R recovery as completed and fresh WP-CONVERGENCE-04 as the sole current executable package.
+- `CHANGELOG.md` preserves the PR #120 governance FAIL, records the independently confirmed PR #122 recovery, and records the fresh retry boundary.
+- `RISK_REGISTER.md` keeps R1/R2/R10 critical and aligns R11 to the recovered/fresh lifecycle; R6 continues to state the consolidated live-app retest is unproven.
+- `REPOSITORY_CONVERGENCE_DEBT_LEDGER.md` records the governed recovery base and freezes the fresh 17-close/1-keep evidence candidate while remaining explicitly temporary/non-authoritative.
+- the recovery claim is closed to factual PASS/merged/exact-main-verified state.
+- the fresh claim explicitly denies reuse of PR #120 or PR #122 assurance as WP04 release authority.
+- fresh contract tests protect exact issue disposition, exactly-one-current-WP state, the post-merge-before-issue-mutation sequence, Stage-2 block and human-review/safety boundaries.
+
+## Tests
+
+### Red cycle 1
+
+```text
+head: 4f9e85d87a4040b78b64f6689e23bfb8a67d179d
+run: 33968392839
+job: 101312453646
+result: 3 failed, 1275 passed in 14.22s
+```
+
+Cause: new governance tests were coupled to exact prose even though the policy semantics were present. Remediation changed only test semantics to assert the actual invariants and ordering; no issue target or product/runtime path changed.
+
+### Red cycle 2
+
+```text
+head: b654a287dd38d46eab6b974766cb68bdb1e031c8
+run: 33968545987
+job: 101312859816
+result: 1 failed, 1277 passed in 15.25s
+```
+
+Cause: the action parser expected the abstract label `issue mutation` inside the fenced action sequence, while the sequence uses the concrete operation `close the 17 reviewed issues`. The test was tightened to that concrete operation; the governance fence remained unchanged.
+
+### Pre-handover green
+
+```text
+head: bd44baaebd5a800fe38151495d7591db4eab78ac
+run: 33968625302
+job: 101313068109
+synthetic merge candidate: c1d9df47f91bc08eb2559d606e25d528fcada162
+result: SUCCESS — 1278 passed in 14.88s
+```
+
+A final full `Tests` run on the handover-complete PR head is mandatory after this file is committed.
+
+## Validation status
+
+- exact 17-close/1-keep disposition: contract-checked on pre-handover green candidate;
+- #96 excluded from closure: contract-checked;
+- consolidated deployed live-app retest: explicitly **unproven**;
+- recovery PASS not reused as WP04 assurance: contract-checked;
+- exact action sequencing through post-merge confirmation before issue mutation: contract-checked;
+- Stage 2: blocked;
+- mandatory human review: preserved;
+- product/runtime behavior: unchanged by intended scope;
+- final handover-complete exact-head regression: pending immediately after this commit;
+- independent governance assurance: pending.
+
+## GitHub Actions status
+
+Pre-handover full Tests: SUCCESS (`33968625302`, `1278 passed in 14.88s`).
+
+Final exact frozen-head Tests: must be read from the new PR head after this handover commit. Assurance must independently inspect the raw run/job rather than rely on this handover.
+
+## Hugging Face sync status
+
+No accepted-main deployment exists for PR #124 before merge. The candidate explicitly requires exact-main GitHub→HF sync/path-ignore verification **after** a future guarded merge and **before** target issue mutation.
+
+## App verification status
+
+**N/A for PR #124 itself** because the candidate changes governance/docs/contracts only and no application/runtime/UI behavior.
+
+This does not satisfy issue #96. Its separate consolidated deployed live-app retest remains unproven and #96 must stay open.
+
+## Remaining risks
+
+1. #96 remains a genuine user-visible live-verification gate.
+2. PR #124 must not inherit assurance authority from PR #120 or recovery PR #122.
+3. The repository currently has no technical branch protection enforcing the human governance sequence; exact-head guarded merge discipline and fresh assurance remain operationally critical.
+4. Historical issue closures must use evidence-aware comments so provenance remains discoverable.
+5. Stage-2 Private persistence/external-AI/content-log work remains deferred until Repository Convergence closes.
+
+## Next recommended step
+
+1. Read PR #124 exact handover-complete head, base, merge-base and changed-file set.
+2. Require a complete green `Tests` workflow on that exact head and inspect raw pytest output.
+3. Freeze the exact head with no further implementation mutations.
+4. Dispatch a genuinely fresh blind-first `governance_release_assurance` reviewer for PR #124 only.
+5. Only on exact-head PASS may assurance perform the guarded merge.
+6. After merge, independently verify exact-main Tests and GitHub→HF sync/path-ignore evidence.
+7. Only after that confirmation may the reviewed 17 issue closures and #96 body reconciliation be applied.
+8. Read back every final issue state; keep #96 open; close #119 only after confirmed administrative outcome.
+9. Assurance must stop after WP04 closeout and must not start the next implementation workpackage.