4 Commits

Include renames

Author	SHA1	Message	Date
Nick	f85c654d9d	fix(release): §14B/§14C — stale-publisher race repaired + convergence-intent ledger eliminated ... 14B: the out-of-lock publisher (publish_out_of_lock) no longer trusts the originating job's SHA. It re-reads CURRENT deployment authority immediately before publishing and constructs the note from the authority's identity. Adversarial race held-out: A promotes → B supersedes → B publishes → A resumes → final history says B, A's SHA never enters. Unreadable authority → no publication (never fabricate an identity). Body parsers (summary_from_body / sha_from_body) moved to release_notes.py as the single authority; release_history_cli.py delegates. 14C: .convergence-intent.json ELIMINATED (1 writer, 0 readers, non-atomic write, bogus recorded_at). Pending convergence is derived from the deployment authority itself (atomic symlink + build identity): restart- readable, corruption-immune, monotonic, idempotent by construction. T11 stale-refusal invariant preserved (CLI revalidation unchanged).	2026-09-14 23:30:51 +01:00
Nick	fa51b96ca7	feat(release): race-safe eventual-convergence revalidation + 12C test plan (SCAFFOLD-TRANCHE-0012 §12C) ... The deploy workflow's promotion gate (steps.promotion_truth.outputs) is necessary but not sufficient: two overlapping deploys can both observe promoted=true at their own moments, and the STALE one's refresh could overwrite the newer converged identity. release_history_cli.py refresh now REVALIDATES against the deployment authority at refresh time: if current's build identity differs from the candidate, the stale refresh is REFUSED (T11 invariant preserved) and the WINNING deploy's refresh converges the release to the final truth. 12C test plan: clean promotion refresh, already-current idempotence, A→B race final-B convergence, candidate/authority disagreement refusal, no-duplicate, missing-release explicit failure, evidence-derived notes.	2026-09-14 05:39:01 +01:00
Nick	2a7e9dcfcf	feat(release): automatic release-history wiring — init on version/tag, convergence refresh on same-version deploy (SCAFFOLD-TRANCHE-009B) ... §1 HELD-OUT CONVERGENCE DEFECT confirmed live: v0.66.45 release recorded deployed ce328a80 while the deployment authority had converged to e3263ef9/0.66.45 — repaired via the new refresh path; the release now states BOTH honestly (tag commit ce328a80 · final deployed e3263ef9). §2 audit answers: NO workflow invoked release_notes.py; release creation used PR title/body paste (empty '##' bodies on direct pushes); nothing refreshed after same-version deploys. T9 proved the mechanism, not automatic adoption — recorded, history not rewritten. §4 WIRING (one note-generation authority, no YAML logic): - auto-version.yml: old PR-paste release step REMOVED (§6); replaced by release_history_cli.py init — evidence-derived notes from the governed scaffold store, fail-closed on publication failure (§5/§16: Rune cannot silently create another empty historical release) - deploy.yml: convergence refresh after successful promotion — same release PATCHed with the converged deployed identity + newly-governed facts; visible non-blocking failure (documentation failure never rolls back valid software; retry converges) - release_notes.py: auto_initial_note (no hand-written prose, §7) + convergence_refresh (evidence accumulates, tag SHA never changes, idempotent) + build_from_deployment - §11 ledger-only: maintenance:builder-interaction-ledger created; §16: release-history backlog entry amended (health indicator), no duplicates Tests: 10 new (§13 A-L incl. 0.66.45 convergence fixture, idempotence, failure visibility, retry recovery, no-duplicate guarantee, unsupported- claim exclusion through the auto path); suite 1620 green.	2026-09-14 02:07:06 +01:00
Nick	4df1f6f23f	feat(release): evidence-derived release history + T8 evidence correction (SCAFFOLD-TRANCHE-009) ... - release_notes.py: deterministic extraction from governed records → structured ReleaseNote → Markdown → Gitea API. Idempotent (PATCH update for existing tags — never duplicates). Version/tag/release-commit/ converged-deployed-identity distinction exposed honestly (§6). - §24F unsupported-claim filter: extras AND extracted facts pass the same exclusion surface — the retracted T8 close-refusal claim cannot enter generated notes (test-proven). - §1/§23: T8 evidence correction recorded with full provenance (original claim, correction, reason, evidence); process-defect:unsupported- causal-claim logged. MiMo maturity survives on supported evidence only. - §18 backfill: 0.66.35→0.66.43 published from closed-contract release_evidence records, marked historical backfill. Pre-0.66.35 skipped (weak evidence — honest limitation). - §19: 0.66.44 notes published to real Gitea (release 89): tag commit f86b2d1eec vs final deployed d84060cc02 distinction, capabilities improvement, bounded MiMo adoption proof (corrected basis), lock-drift fix, external-project limitation. - Gitea 400-tolerance: plain-text error bodies handled (actual behavior, not assumed GitHub semantics). Tests: 17 new (§24/§25/§26 plans); suite 1608 green; henxels rc=0; pyright clean.	2026-09-14 01:10:42 +01:00