Estate sweep: Tooling Version Integrity rollout — completion tracking (burble#39 lesson)

[hyperpolymath]

Tracking issue for full rollout + closure of the Tooling Version Integrity initiative. Spawned from the burble#39 post-mortem (unpinned just 1.14.0 vs import? ≥1.19.0 → parse-time crash misdiagnosed for months as failing tests, frozen behind continue-on-error on a wrong root cause).

Done

• P0 — only live armed unversioned install fixed: ci: pin just@1.34.0 in build-gossamer-gui — Tooling Version Integrity (cf. burble#39) hypatia#270 (build-gossamer-gui.yml). Estate sweep confirms the bug surface is fully bounded: only burble (fixed, burble#40 merged) and hypatia ([campaign #253] STEP 5 — LARGER BATCH: 8+ manifest repos #270) ever installed just unversioned. No 50-repo pinning epidemic.
• P1+P2+P3 — policy: Tooling Version Integrity — institutionalise the burble#39 lesson #94:
  • TOOLING-VERSION-INTEGRITY-POLICY.adoc (5 rules + post-mortem)
  • tasks/tooling-integrity-lint.sh (R0 just-floor blocking, R1 unversioned-install blocking, R4 unexplained-continue-on-error advisory-first; self-tested)
  • contractiles/must/Mustfile canonical dependency-free tooling-version-integrity check
  • live Mustfile dogfoods the lint; Justfile carries the Rule-2 floor annotation
  • governance-reusable.yml inline R0+R1 gate → propagates estate-wide via the existing workflow_call line, no per-repo PR

Remaining / owned handoffs (inherently multi-session or external)

• contractile generator regen is out-of-band. The generator repo is not in the working estate. The new canonical contractiles/must/Mustfile check reaches consumers only when someone holding the generator runs contractile gen-just --dir contractiles and repos re-adopt. Until then, governance-reusable.yml is the live propagation path (no regen needed).
• R4 advisory → --strict promotion. ~9 advisory continue-on-error findings in standards alone (estate-wide more). Promote per-repo as each soft-gate is explained (dated suppression or by-design:). Do not flip estate-wide at once — that would itself become an ignored gate (the exact anti-pattern).
• governance-reusable adoption audit. Confirm every estate repo invokes governance-reusable.yml (6 consumers seen locally; full estate unverified) so the inline R0/R1 gate actually runs everywhere.
• burble#35 item 2 (cross-ref burble#39). Final Elixir gate re-arm is blocked on a green/red CI signal — GitHub runners queued ~3h+ (external). burble#39 carries the line-pinned static prediction (RED via Burble.Store/VeriSimDB at app-boot); remediation A (test-env child filtering) is identified but, per the burble#40 "confirm before fixing" discipline, must wait for the real CI log. A watcher is live.

Closure criteria

• standards#94 + hypatia#270 merged
• contractile regen performed (or a permanent non-regen propagation path ratified)
• governance-reusable adoption audited estate-wide
• burble#35 closed (item 2 re-armed once CI confirms green, or remediation-A PR landed then re-armed)
• R4 promoted to --strict in repos with no unexplained soft-gates

Refs: burble#35, burble#39, #94, hyperpolymath/hypatia#270

[hyperpolymath]

Closure-criteria status refresh (session 2026-05-19)

standards#94 merged

DONE. PR #94 merged. governance-reusable.yml is live with inline R0+R1 gate. Verified in this session.

hypatia#270 state

CLOSED (not merged). gh pr view 270 --json state,mergedAt returns state: CLOSED, mergedAt: null, closedAt: 2026-05-19T16:17:22Z. The PR was closed without merge. The fix (pin just@1.34.0 in build-gossamer-gui.yml) needs a re-examination: either re-open, or verify the fix landed another way (e.g. the governance-reusable.yml R0 gate now enforces the floor estate-wide). Owner action required: determine whether the pinning fix was applied directly, superseded by the R0 gate, or still needs a new PR.

governance-reusable adoption audit

DONE (this session). Full read-only sweep of local estate clones (101 repos with governance.yml):

77 repos invoke governance-reusable.yml (full list available; key active repos confirmed):
affinescript, ambientops, boj-server, burble, echidna, echo-types, hypatia, idaptik, iseriser, k9iser, my-lang, panll, proof-of-work, proven, reposystem, rsr-template-repo, snifs, stapeln, standards, ubicity, v3-templater, vcl-ut, verisimiser, volumod, plus 34 Julia.jl repos and several others.

3 key repos still on old per-repo governance pattern (have individual workflow files but no governance-reusable.yml wrapper, thus NOT receiving the inline R0+R1 gate):

• ephapax — has guix-nix-policy.yml, rsr-antipattern.yml, etc. but no governance.yml wrapper
• gossamer — same; 16 individual workflow files
• typed-wasm — same; 15 individual workflow files

These three repos are NOT running the R0/R1 gate from standards#94. Each needs a migration PR replacing the 8-15 individual governance files with a single governance.yml wrapper calling governance-reusable.yml@main. This is tractable (one PR per repo) but is a separate session — these are not high-urgency since language-policy enforcement continues via the individual files.

contractile generator regen — out-of-band

BLOCKED (external, not actionable here). Generator repo not in working estate. Propagation via governance-reusable.yml is the live path.

R4 advisory → --strict promotion

IN PROGRESS (per-repo, explicitly not estate-wide). In governance-reusable.yml itself: 2 continue-on-error: true lines (unexplained advisory). In affinescript-verify.yml: 5 lines (all annotated NON-BLOCKING (temporary)). In hypatia-scan.yml: 2 lines (annotated). None of these are unexplained. Promoting per-repo as gates are explained is ongoing; the iseriser#12 PR adds one new continue-on-error: true annotated by-design: loopback not reachable from GH Actions runners — R4 compliant.

burble#35 item 2

OPEN, external. Re-arm of Elixir test gate blocked on CI log confirming root cause (Burble.Application full-app-boot under mix test --no-start). Watcher live. Not actionable until CI confirms.

Updated closure criteria

• standards#94 merged
• hypatia#270 — CLOSED NOT MERGED; requires owner decision (re-open or confirm superseded by R0 gate)
• contractile regen — permanent non-regen propagation path ratified (governance-reusable.yml is the live path)
• governance-reusable adoption audited estate-wide (77/101 repos; 3 key stragglers identified: ephapax, gossamer, typed-wasm)
• burble#35 item 2 — OPEN, external CI dependency
• R4 promoted to --strict in repos with no unexplained soft-gates (in progress, per-repo)

🤖 Generated with Claude Code

[hyperpolymath]

Closure-criterion update (2026-05-19):

hypatia#270 merged → resolved by supersession, not merge.

Verified that .github/workflows/build-gossamer-gui.yml on hypatia origin/main already pins tool: just@1.34.0 (line 148) with the import?-floor rationale comment block that #270 proposed — the fix landed via a separate commit. Forward regression is gated by the R0 just-floor check in this issue's governance-reusable.yml (standards#94). Supersession comment posted on hypatia#270; that PR remains CLOSED.

Refs #94, hyperpolymath/hypatia#270.

[hyperpolymath]

Residue verified 2026-05-27 — leaving OPEN.

Two closure criteria still unchecked per the May 19 status refresh:

• burble#35 item 2 — gh issue view 35 --repo hyperpolymath/burble still OPEN. External CI dependency, watcher live.
• R4 promoted to --strict in repos with no unexplained soft-gates — in progress, per-repo, explicitly not estate-wide ("flipping estate-wide at once would itself become an ignored gate, the exact anti-pattern").

Resolved:

• standards#94 MERGED 2026-05-17
• hypatia#270 — supersession verified (just@1.34.0 landed via separate commit + R0 gate enforces floor)
• governance-reusable adoption audited (77/101, 3 stragglers: ephapax, gossamer, typed-wasm — separate session)
• contractile regen — permanent non-regen path ratified

Not closeable until burble#35 closes and R4 hardening reaches a defined stop-line.

[hyperpolymath]

Status refresh (2026-05-30):

Major blockers satisfied:

• standards#94 merged.
• hypatia#270 closed.

Remaining items in this tracker are largely bureaucratic / governance-flavoured:

• Governance-reusable adoption audit.
• Contractile regen-path completion.
• burble#35 follow-up — note that burble#35 itself closed 2026-05-27 after splitting into burble#99/Phase E — Production wiring + staging validation + rollout/rollback runbook #100/policy: Guix primary + sealed-container escape; retire Nix-mirror-everywhere #101 (still open).

Recommend: either narrow this issue's scope to the governance-audit items + close the rest as discharged, or close this and re-file the bureaucratic items in dedicated sub-trackers.

[hyperpolymath]

Re-verified 2026-08-26 — closing: every closure criterion is now met

The one blocker this thread said kept it open — burble#35 — has since closed, along with all three issues it was split into.

item	state
burble#35	CLOSED
burble#99 (Hypatia SARIF integration)	CLOSED
burble#100 (re-arm Elixir test gate)	CLOSED
burble#101 (remove dead autofix reference)	CLOSED

That was the last unresolved external blocker per the 2026-05-30 comment above.

Deliverables, checked live

standards#94	MERGED 2026-05-17
TOOLING-VERSION-INTEGRITY-POLICY.adoc	✅ present, 6,729 B
tasks/tooling-integrity-lint.sh	✅ present, 4,336 B
governance-reusable.yml	✅ live, 66,033 B

The three flagged stragglers are resolved

• ephapax — now calls governance-reusable.yml
• typed-wasm — now calls governance-reusable.yml
• gossamer — hyperpolymath/gossamer 404s; the repo moved to metadatastician/gossamer, which also now calls governance-reusable.yml

On hypatia#270

CLOSED, not merged — but superseded, and the supersession is real: build-gossamer-gui.yml:153 carries tool: just@1.34.0 right now, exactly as the 2026-05-30 comment claimed.

The one remaining item is scoped as ongoing-forever by design

"R4 promoted to --strict … explicitly not estate-wide" — the 2026-05-30 comment already recommended narrowing or closing on this basis. Closing accordingly.

Not checked: a full re-audit of all 101 repos carrying governance.yml (only the three named stragglers were re-verified), and current per-repo R4 --strict promotion state beyond what is in this thread.