R20: Repin reconciliation from RC19 to stable v1.6.10

[100yenadmin]

Wait for stable v1.6.10. Verify tag provenance and review the complete RC-to-stable delta. Rebuild the reconciliation branch from the stable tag and replay only reviewed capability commits; never merge the old fork or RC branch wholesale.

Acceptance: exact stable base is recorded, replay list matches the disposition ledger, and focused tests cover every upstream subsystem changed after RC19.

Stop if stable is absent or materially invalidates a retained patch.

Parent epic: #39

Tracking ID: R20

[100yenadmin]

Product release decision (2026-07-13): upstream acceptance and release timing are non-blocking for the internal fork. Live provenance remains upstream main c6445096eb3fdfa70bc1d13995918e0cbd783a38; RC19 peels to d43c479ac58c18d397958f48a99465d6c3110b1d and is one version-only commit ahead; no upstream v1.6.10 tag exists. R20 will re-check provenance immediately before promotion, retain RC19 as the truthful internal base, and record later stable as a future reconciliation input rather than waiting or inventing a stable base. Evidence: /Volumes/LEXAR/Codex/session-notes/2026-07-13/gitnexus-fork-upstream-reconciliation/internal-fork-release-decision.md.

[100yenadmin]

R20 disposition (internal release authority): a fresh remote provenance check on 2026-07-14 found no v1.6.10 tag; upstream main remains c6445096eb3fdfa70bc1d13995918e0cbd783a38.

The product owner explicitly approved the fork as its own internal release authority and directed that upstream timing must not block reconciliation. We therefore retain the peeled v1.6.10-rc.19 commit d43c479ac58c18d397958f48a99465d6c3110b1d as the truthful integration base, preserve the complete commit-disposition ledger, and treat any later stable tag as future reconciliation input rather than a prerequisite for this internal release.

This closes R20 by documented gate disposition, not by claiming a stable rebase occurred. No history, tag, package, runtime, live index, or preserved dirty workspace was changed. Final promotion still requires exact-head CI/review and the two disposable OpenClaw canaries.

[100yenadmin]

Closed because the required upstream stable tag does not exist and the product owner approved RC19 as the truthful internal-fork base. Stable reconciliation remains future input when upstream publishes it; this is not a claim that stable was tested.