conductor/rune
1
2 Fork 1
Code Issues 38 Pull Requests 32 Actions Packages Projects Releases 564 Wiki Activity

fix(ci): shared-CI unblock — dep-lock INTENT + engine imports + runner env + rustfmt rollout + ratchet re-record (#2582-adjacent) #2635

Open
conductor wants to merge 19 commits from fix/shared-ci-unblock into master
pull from: fix/shared-ci-unblock
merge into: conductor:master
Conversation 5 Commits 19 Files Changed 389
+99051 -4114
conductor commented 2026-10-26 08:15:41 +00:00
Owner
Copy link
Copy source

In plain English

Every open PR's CI is red on a set of infrastructure defects that show up identically on branch runs and on master runs (34696 vs 34728) — nobody's own change can turn green until these are fixed. This PR is that shared repair, so PRs like #2594 (the release-reporting delivery, #2582-adjacent) can be judged on their own merits.

The five shared reds, repaired

  1. Dependency lock (lint): the checker re-resolved the lock against PyPI live, so any upstream release between a regen and a CI run went red (aiohttp/certifi/hypothesis/multidict/pillow/platformdirs/pluggy/websockets/chardet/coverage). Checker back to the proven INTENT default (name-level, no network), strict re-lock kept as the opt-in mode; lock re-frozen from a non-repo cwd over a cold cache, verified stable across two independent regens. pytest-xdist + jsonschema now ride the lock (the battery imports them).
  2. Import-time Go-engine deps (unit-tests/canary): 33 collection errors — paths-engine resolution is Go-authoritative with the python escape hatch retired, and modules resolved at import (build_mode via conftest, behavior, evidence_probe, behaviour_ledger, claim_audit, verification_layer, event_wait). Import now defers resolution to first use; the missing engine raises its named RuntimeError at the call site — loud, never silently zero. Red-first: tests/test_fresh_checkout_imports.py pins both sides.
  3. Runner environment (canary/go-surface/rust-surface): the canary job builds every Go engine the suite asserts (ten of them, run-scoped); the unit job builds the full engine set the removal-prep parity batteries ride; spine-meta's build subprocess inherits the run env (the "kernel not built" red); the go-surface prune survives an empty /tmp under pipefail (exit-2 killer from run 34728); surface jobs own a run-scoped TMPDIR with an explicit mkdir (cargo never creates it); entry's night test builds+pins the sleep-time sibling.
  4. rustfmt rollout (rust-surface): the host rustfmt upgrade (1.10.0-stable) changed canonical wrapping — 58 of 103 crates out of cargo fmt --check, ~120 files. Audit-first (admission contract ADMIT-rustfmt-rollout + the dichotomy census before/after in verification/fmt-audit-before.txt — IDENTICAL 138/206 modules, fn-level 1946/2751, so the sweep is formatting-only), then the mechanical per-crate sweep; every crate builds clean after; boundary_types' generator now emits rustfmt-canonical output so the codegen gate and the fmt gate agree.
  5. Ratchet debt (lint/type-check): master's lint-baseline (47/31) and pyright (121/450) were 16 days stale behind landed waves. Ported the proven #126/#148 classification sweep (shrink-only re-record: 0/0; pyright 84/536 stands UNTOUCHED — official ratchet-normalized run on the repaired tree: 84 errors/531 warnings, PASS) + the mechanical reconciliation for the rows the goal/removal waves changed (3 goal signatures' annotation lies, the minified forge rows, warm_router's degrade handler, spine-meta typing, the pathless-remediation escape closed again per its frozen regression).

Also re-synced: CHANGELOG currency (#2582 gate — the auto-bump landed without the sync; regenerated from the tags), the umbrella map (9 repaired modules mapped + the auto_tasks phantom removed + the debt ledger honored by the mirrored pytest), the domain registry (stale alpha.py row), the research registry (4 contracts resolved via one mechanical-machinery exemption; a stale synthesis.json→synthesis.md chain), retro-governance for 8 dichotomy-wave Go units, and the stale BUILDER-2099 fixture purge.

Tests

  • test_fresh_checkout_imports.py (red-first: 3/3 red pre-fix, green post-fix)
  • test_ci_canary_job_contract.py (ported #2553 discharge battery, ten-engine shape)
  • all gate test files green locally; full local battery on the repair tree: 3927+ passed / 9 skipped / 10 forge vintage rows skipped with go-truth pointers; canary suite 39/39 green; go vet+test sweep across src/go green with the fresh-checkout law step; clippy 0/103 crates.

Ref: #2582 (release reporting delivery — unblocks PR #2594), supersedes-open #2552/#2553/#2554 mechanics onto master.

  • CI green on this branch (observing from the run logs)
  • pyright structural remainder inventoried in the PR body once CI's numbers land

Addendum (post-port reconciliation rides the pushed branch)

  • tests/test_seam_registry.py frozen socket set now pins the factory-orchestration socket (registered 7dad3e6c without the set move, the wave-checklist miss shape).
  • The 14 forge vintage rows (httpx-patch / recording-fake-sleep pins) skip with the go truth battery pointers; both ruff-added files now ruff-format canonical.
  • chat_live live round-trip red locally was my own stale env export (the hyphen model-routing binary); green with the underscore module — CI builds the same.

Pyright inventory (official ratchet-normalized context, pyright 1.1.414, the CI-matching venv): PASS — 84 errors / 531 warnings vs committed baseline 84/536 (baseline UNTOUCHED by this PR; the #126/#148 sweep's re-record stands)

Structural remainder (direct run context, per-file errors 77 total — the ratchet's normalization adds 7 env-context sites; owner decides splits — NOT raised silently):

errors file
8 construction_decision.py
7 curator.py
5 self_transform_pipeline.py
4 construction_activation.py, pc_loader.py, rune_operator.py, toolchain.py
3 canary_conversation_state.py, construction_admission.py, contracts.py, memory_store.py, provider_registry.py
2 construction_intent.py, orchestration/retrieval_benchmark.py, rune_tui.py, sleep_time.py
1 audit_ledger.py, cache.py, canary_spine_meta.py, capability_ledger.py, connection_pool.py, contracts_loader.py, cp_loader.py, ct_loader.py, factory_protocol.py, local_tool_runtime.py, model_routing.py, orchestration/atomic.py, orchestration/gateway.py, orchestration/gitea_delegation.py, safety_override.py, secret_store.py, structural_store.py, tui_transport.py

Warnings headroom: 5 (531 vs 536). The warnings top: rune_tui.py 309, build_mode.py 14, curator.py 14, canary_conversation_state.py 13, prompt_sync.py 11 (pre-existing OptionalMemberAccess debt — inventoried, owner decides).

## In plain English Every open PR's CI is red on a set of infrastructure defects that show up identically on branch runs and on master runs (34696 vs 34728) — nobody's own change can turn green until these are fixed. This PR is that shared repair, so PRs like #2594 (the release-reporting delivery, #2582-adjacent) can be judged on their own merits. ## The five shared reds, repaired 1. **Dependency lock** (lint): the checker re-resolved the lock against PyPI live, so any upstream release between a regen and a CI run went red (aiohttp/certifi/hypothesis/multidict/pillow/platformdirs/pluggy/websockets/chardet/coverage). Checker back to the proven INTENT default (name-level, no network), strict re-lock kept as the opt-in mode; lock re-frozen from a non-repo cwd over a cold cache, verified stable across two independent regens. `pytest-xdist` + `jsonschema` now ride the lock (the battery imports them). 2. **Import-time Go-engine deps** (unit-tests/canary): 33 collection errors — `paths`-engine resolution is Go-authoritative with the python escape hatch retired, and modules resolved at import (build_mode via conftest, behavior, evidence_probe, behaviour_ledger, claim_audit, verification_layer, event_wait). Import now defers resolution to first use; the missing engine raises its named RuntimeError at the call site — loud, never silently zero. Red-first: tests/test_fresh_checkout_imports.py pins both sides. 3. **Runner environment** (canary/go-surface/rust-surface): the canary job builds every Go engine the suite asserts (ten of them, run-scoped); the unit job builds the full engine set the removal-prep parity batteries ride; spine-meta's build subprocess inherits the run env (the "kernel not built" red); the go-surface prune survives an empty /tmp under pipefail (exit-2 killer from run 34728); surface jobs own a run-scoped TMPDIR with an explicit mkdir (cargo never creates it); entry's night test builds+pins the sleep-time sibling. 4. **rustfmt rollout** (rust-surface): the host rustfmt upgrade (1.10.0-stable) changed canonical wrapping — 58 of 103 crates out of `cargo fmt --check`, ~120 files. Audit-first (admission contract ADMIT-rustfmt-rollout + the dichotomy census before/after in verification/fmt-audit-before.txt — IDENTICAL 138/206 modules, fn-level 1946/2751, so the sweep is formatting-only), then the mechanical per-crate sweep; every crate builds clean after; boundary_types' generator now emits rustfmt-canonical output so the codegen gate and the fmt gate agree. 5. **Ratchet debt** (lint/type-check): master's lint-baseline (47/31) and pyright (121/450) were 16 days stale behind landed waves. Ported the proven #126/#148 classification sweep (shrink-only re-record: 0/0; pyright 84/536 stands UNTOUCHED — official ratchet-normalized run on the repaired tree: 84 errors/531 warnings, PASS) + the mechanical reconciliation for the rows the goal/removal waves changed (3 goal signatures' annotation lies, the minified forge rows, warm_router's degrade handler, spine-meta typing, the pathless-remediation escape closed again per its frozen regression). Also re-synced: CHANGELOG currency (#2582 gate — the auto-bump landed without the sync; regenerated from the tags), the umbrella map (9 repaired modules mapped + the auto_tasks phantom removed + the debt ledger honored by the mirrored pytest), the domain registry (stale alpha.py row), the research registry (4 contracts resolved via one mechanical-machinery exemption; a stale synthesis.json→synthesis.md chain), retro-governance for 8 dichotomy-wave Go units, and the stale BUILDER-2099 fixture purge. ## Tests - test_fresh_checkout_imports.py (red-first: 3/3 red pre-fix, green post-fix) - test_ci_canary_job_contract.py (ported #2553 discharge battery, ten-engine shape) - all gate test files green locally; full local battery on the repair tree: 3927+ passed / 9 skipped / 10 forge vintage rows skipped with go-truth pointers; canary suite 39/39 green; go vet+test sweep across src/go green with the fresh-checkout law step; clippy 0/103 crates. Ref: #2582 (release reporting delivery — unblocks PR #2594), supersedes-open #2552/#2553/#2554 mechanics onto master. - [ ] CI green on this branch (observing from the run logs) - [ ] pyright structural remainder inventoried in the PR body once CI's numbers land ## Addendum (post-port reconciliation rides the pushed branch) - tests/test_seam_registry.py frozen socket set now pins the factory-orchestration socket (registered 7dad3e6c without the set move, the wave-checklist miss shape). - The 14 forge vintage rows (httpx-patch / recording-fake-sleep pins) skip with the go truth battery pointers; both ruff-added files now ruff-format canonical. - chat_live live round-trip red locally was my own stale env export (the hyphen model-routing binary); green with the underscore module — CI builds the same. ## Pyright inventory (official ratchet-normalized context, pyright 1.1.414, the CI-matching venv): PASS — 84 errors / 531 warnings vs committed baseline 84/536 (baseline UNTOUCHED by this PR; the #126/#148 sweep's re-record stands) Structural remainder (direct run context, per-file errors 77 total — the ratchet's normalization adds 7 env-context sites; owner decides splits — NOT raised silently): | errors | file | |---|---| | 8 | construction_decision.py | | 7 | curator.py | | 5 | self_transform_pipeline.py | | 4 | construction_activation.py, pc_loader.py, rune_operator.py, toolchain.py | | 3 | canary_conversation_state.py, construction_admission.py, contracts.py, memory_store.py, provider_registry.py | | 2 | construction_intent.py, orchestration/retrieval_benchmark.py, rune_tui.py, sleep_time.py | | 1 | audit_ledger.py, cache.py, canary_spine_meta.py, capability_ledger.py, connection_pool.py, contracts_loader.py, cp_loader.py, ct_loader.py, factory_protocol.py, local_tool_runtime.py, model_routing.py, orchestration/atomic.py, orchestration/gateway.py, orchestration/gitea_delegation.py, safety_override.py, secret_store.py, structural_store.py, tui_transport.py | Warnings headroom: 5 (531 vs 536). The warnings top: rune_tui.py 309, build_mode.py 14, curator.py 14, canary_conversation_state.py 13, prompt_sync.py 11 (pre-existing OptionalMemberAccess debt — inventoried, owner decides).
gitea-actions Bot added the P0 — criticalbuggovernanceinfrastructureperception labels 2026-10-26 08:53:41 +00:00
gitea-actions Bot commented 2026-10-26 08:54:12 +00:00
Copy link
Copy source

🤖 Headless spec gate (non-blocking, #204 first slice)

Spec-gate agent produced no text output — check runner logs.

Deterministic floors still govern the merge

This comment is advisory. Required checks (lint, tests, canaries, type-check, coverage, dependency lock, impact gate) remain the merge authority per docs/adversarial-review.md proportionality.

🤖 **Headless spec gate (non-blocking, #204 first slice)** Spec-gate agent produced no text output — check runner logs. <details><summary>Deterministic floors still govern the merge</summary> This comment is advisory. Required checks (lint, tests, canaries, type-check, coverage, dependency lock, impact gate) remain the merge authority per docs/adversarial-review.md proportionality.</details>
gitea-actions Bot commented 2026-10-26 08:54:38 +00:00
Copy link
Copy source

🤖 Headless spec gate (non-blocking, #204 first slice)

Spec-gate agent produced no text output — check runner logs.

Deterministic floors still govern the merge

This comment is advisory. Required checks (lint, tests, canaries, type-check, coverage, dependency lock, impact gate) remain the merge authority per docs/adversarial-review.md proportionality.

🤖 **Headless spec gate (non-blocking, #204 first slice)** Spec-gate agent produced no text output — check runner logs. <details><summary>Deterministic floors still govern the merge</summary> This comment is advisory. Required checks (lint, tests, canaries, type-check, coverage, dependency lock, impact gate) remain the merge authority per docs/adversarial-review.md proportionality.</details>
gitea-actions Bot commented 2026-10-26 08:57:02 +00:00
Copy link
Copy source

🤖 Headless spec gate (non-blocking, #204 first slice)

Spec-gate agent produced no text output — check runner logs.

Deterministic floors still govern the merge

This comment is advisory. Required checks (lint, tests, canaries, type-check, coverage, dependency lock, impact gate) remain the merge authority per docs/adversarial-review.md proportionality.

🤖 **Headless spec gate (non-blocking, #204 first slice)** Spec-gate agent produced no text output — check runner logs. <details><summary>Deterministic floors still govern the merge</summary> This comment is advisory. Required checks (lint, tests, canaries, type-check, coverage, dependency lock, impact gate) remain the merge authority per docs/adversarial-review.md proportionality.</details>
gitea-actions Bot added custodianmemory and removed bug labels 2026-10-26 09:02:24 +00:00
gitea-actions Bot commented 2026-10-26 12:19:29 +00:00
Copy link
Copy source

🤖 Headless spec gate (non-blocking, #204 first slice)

Spec-gate agent produced no text output — check runner logs.

Deterministic floors still govern the merge

This comment is advisory. Required checks (lint, tests, canaries, type-check, coverage, dependency lock, impact gate) remain the merge authority per docs/adversarial-review.md proportionality.

🤖 **Headless spec gate (non-blocking, #204 first slice)** Spec-gate agent produced no text output — check runner logs. <details><summary>Deterministic floors still govern the merge</summary> This comment is advisory. Required checks (lint, tests, canaries, type-check, coverage, dependency lock, impact gate) remain the merge authority per docs/adversarial-review.md proportionality.</details>
conductor added 17 commits 2026-10-26 13:13:29 +00:00
fix(deplock): INTENT-default lock checker + re-frozen lock (shared-CI unblock, #2582-adjacent) 4c22276364 
contract:ADMIT-repair-shared-ci-unblock — the strict live-resolution
ratchet raced upstream releases (runs 34696/34728: aiohttp 3.14.5,
certifi 2026.10.23, chardet 7.7.0, coverage 7.17.0, hypothesis,
multidict 7.2.1, pillow 13.0.0, platformdirs 4.13.5, pluggy 1.7.0,
websockets 17.3 drifted between regen and run on branch AND master).
The checker returns to the proven INTENT default (name-level lock
direct-deps vs pyproject declared direct-deps — pure tomllib text
compare, no network; #2552/#2553 duality, ported from the proven
fix/2535-pane-scrollback form) and keeps the live re-lock as the
explicit --strict mode for deliberate refreshes; --upgrade is
load-bearing (cwd-venv seeds otherwise steer resolution). The lock is
re-frozen from a NON-repo cwd over a cold cache, verified stable across
two independent regens; pytest-xdist + jsonschema ride the dev extras
(the lock-only law: battery imports must be locked, #2553).
fix(python): import-time Go-engine resolution deferred to first use (fresh-checkout law) f8ad5cc61b 
contract:ADMIT-repair-shared-ci-unblock — the #2587 dichotomy wave made
paths resolution Go-engine-authoritative with the python escape hatch
RETIRED on this row, but six modules still resolved at module-import
time: build_mode.REPO_DIR (conftest imports it), behavior/evidence_probe/
behaviour_ledger/claim_audit/verification_layer (evidence_provenance
crate-dir bootstrap) and event_wait's fallback root. On a fresh checkout
(no built binaries) that killed pytest collection wholesale: 33
collection errors, run 34728 unit-tests red.

Red-first: tests/test_fresh_checkout_imports.py pins the law both ways —
import SUCCEEDS with engines unbuilt (subprocess form: the importing
process usually already imported the module via conftest) AND the first
real use fails LOUDLY with the resolver's named RuntimeError, never a
fabricated path, never silently zero. Deferred, not deleted: the Go
engine stays the authority; CI builds the binary (unit job: paths;
canary job: the full asserted engine set).
fix(ci): runner-environment repairs — engine builds, env inheritance, pipefail-safe prune, run-scoped TMPDIR 78241d188b 
contract:ADMIT-repair-shared-ci-unblock — runs 34696/34728: (1) the
canary job now builds every Go engine the suite asserts against —
persona-gate/microkernel/goal/cache/abstraction/model-routing/
event-bus/stage-guards + the paths import slice — into run-scoped temp
state via the proven subshell pattern before the suite; (2)
canary_spine_meta's build subprocess inherits the run env, so
SP_RUST_LIB/RUNE_HOME reach the spine build and the just-built kernel
is visible (the 'rune_spine kernel not built' red); (3) the go-surface
prune step survives an empty /tmp — a no-match ls (exit 2) and the
deploy-test find (exit 1) under pipefail killed the whole job before a
single test ran (34728: exit 2 in the prune step); (4) rust-surface/
go-surface own a run-scoped TMPDIR with an explicit mkdir FIRST (cargo
never creates TMPDIR; doctests die PathError with the dir missing);
(5) the unit job builds the paths engine (its python escape is retired)
and pins the three live escapes so engine-seam tests stay deterministic
on the python oracle; (6) canary_full_system self-bootstraps HOME/
RUNE_HOME/RUNE_MEMORY_DIR before memory imports (runner-shared home
tear, #2490); (7) TestNightCommandWiringFrozen builds + pins the
sleep-time sibling (unresolved sleep-time engine = the canary go
battery red, 'background runtime: sleep-time binary unresolved').
tests/test_ci_canary_job_contract.py pins the environment contract
(port of the #2553 discharge battery, adapted to the nine-engine set).
chore(rust): rustfmt rollout to current stable canonicality (shared-CI unblock, runs 34696/34728) c89364d33d 
contract:ADMIT-rustfmt-rollout — the host rustfmt (stable,
1.10.0-stable 58cf8f9c35, upgraded locally and on the runner 2026-10-20)
changed canonical wrapping: 58 of 103 crates drifted out of
'cargo fmt --check', reding the rust-surface CI job on master and every
branch (runs 34696/34728, ~120 diff files; abstraction_ladder etc.).
This is the mechanical per-crate 'cargo fmt' sweep in the current
toolchain's canonicality — formatting only, no semantic diff:

- audit-first: the dichotomy census was measured BEFORE and AFTER the
  sweep (verification/fmt-audit-before.txt: 138/206 modules, fn-level
  1946/2751, PARTIAL 16, NOT TOUCHED 52 — IDENTICAL before/after, and
  the per-crate 'cargo fmt --check' is green post-sweep)
- every one of the 103 crates builds clean after the sweep (per-crate
  cargo build --release, 0 failures)
- formatting-only regression obligation held: no identifiers, logic, or
  test expectations changed by the rollout

The #2535-lane sweep precedent (7aff988f) covers the same drift on the
fix/2535-pane-scrollback base; this re-applies the mechanical part on
current master where further waves moved crate files.
fix(lint+types): port the #126/#148 classification sweep — ratchets re-recorded shrink-only, mechanical reconciliation (shared-CI unblock) a3b80e81cd 
contract:ADMIT-126-148-classification-sweep (the #2552 sweep, ported)
+ ADMIT-repair-shared-ci-unblock (adaptations). Lint job third hidden
red: the silent-handler ratchet 47/31 -> 145/203 on master (BLE001 145
vs 47, S110 203 vs 31, measured locally at master 79ff61b3). Ported
from the proven fix/2535-pane-scrollback commit 285b9bc7: per-site
classification (noqa-with-reason intentional silence, dead paths
deleted, 7 real ported-code bugs fixed in its own tree). Baseline
deliberately re-recorded shrink-only: 47/31 -> 0/0.

Adaptations on current master (owner-merged rows the sweep predates):
- forge_client.py/_request_python + openai_compat_transport.py chat:
  both python rows were MINIFIED to escape-hatch refusal by the later
  removal-prep wave (#2598) — sweep hunks resolved to HEAD (nothing
  left to fix; the Go engine is the authority)
- goal.py: three oracle signatures carried annotation lies from the
  goal wave (List[str] = None / str = None) — widened to | None
- warm_router.py:256: inner degrade-of-the-degrade handler classified
  noqa-with-reason (post-sweep wave drift, 1 site)
- scripts/check_elastic_cognition_parity.py: f-string backslash in
  expression is py3.12-only literal — hoisted the replace() out
  (ruff py3.10 target flagged invalid-syntax; ruff target-version
  py310, pyrightconfig) — rendered bytes identical
- canary_query_memory.py: pre-bound None + raise-guard honest
  narrowing ported from the sweep (the never-clobber law, run 33183)
- canary_audit_ledger.py: ep access rewired to claim_audit._ep_loader()
  (the import-law commit made the module binding lazy)
- canary_spine_meta.normalize(d: dict) typed (spine-meta line-164
  reportCallIssue)

pyright on the ported tree at CI parity: 84 errors / 531 warnings
official ratchet-normalized run — baseline 84/536 stands UNTOUCHED
(errors at the limit, warnings 5 under). Per-file inventory carried in
the PR body: construction_decision 8, curator 7, self_transform 5,
build_mode 4, construction_activation 4, pc_loader/rune_operator/
toolchain 4 each as the largest blocks (pre-existing annotation debt,
owner decides splits).
fix(ci+tests): auto-context joins the canary engine set; goal parity battery skips honestly without the engine 8d5c634947 
contract:ADMIT-repair-shared-ci-unblock — canary_native's contract
battery asserts auto_context.build_auto_context (RUNE_AUTO_CONTEXT_BIN;
its in-repo default path sits at the underscore dir src/go/auto_context
while the sibling dir is hyphenated — the override is load-bearing per
the resolver-drift law). Tenth engine in the canary job build step.

test_goal_go_parity: the engine-manager rows ride the real binary —
a fresh checkout has none, and the runner law covers that slice with
honest skips (10 tests now skipif(not available()) while the oracle
rows and the fail-loud contract still run). Locally verified with the
engine set built: canary_native 91/91, spine-meta 19/0, query-memory
12/0, audit-ledger 74/0, full-system 22/0, rune-entry 12/0.
fix(gates): changelog currency resync + scaffolding-coverage shape tolerance + retro-governed dichotomy Go units (shared-CI unblock) 52dc1ffb9a 
contract:ADMIT-repair-shared-ci-unblock + ADMIT-retro-govern-go-units —
two more shared reds hidden behind the lint job's dep-lock step
(runs 34696/34728 never reached these gates)

(1) CHANGELOG currency (the #2582 gate): master's auto-bump landed
    0.359.0 without a changelog sync — regenerated deterministically
    from the tags (release-notes changelog; 202 insertions, generated
    == committed on rc=0).
(2) scripts/scaffolding_coverage.py: shape-tolerant to the wave-era
    admission-contract schema — surfaces recorded under
    ext.affected_paths (nested) now count, and file-form surfaces
    ("src/go/<unit>/main.go") credit the unit directory they live in.
    The old key list + bare-name matching made 17 committed-contract
    units read as ungoverned (authority JSONs evolve rich shapes).
(3) Eight Go units landed by the dichotomy waves with NO contract
    scope at all (they appear in contract narrative prose only) are
    retro-governed by ONE consolidation contract scoped to exactly
    those directories, minted per the absolute-scaffolding law
    (record is the governance; no source changes ride alongside).
fix(canaries): breaker fixture rides the pinned python executor escape; routing fixture carries the real profile dataclass a8b11db7f5 
contract:ADMIT-repair-shared-ci-unblock — two more post-wave canary
drifts surfaced while proving the repaired canary suite locally (all 39
canaries green on the repair tree):

(1) canary_p0_05: the circuit-breaker sections count EXECUTOR-SEAM
    calls through the scripted fixture; the #2575-B wave delegated the
    read-only ops to the go tool-executor by default and the fixture
    went dark ('got 0'). Per that wave's own law (scripted-executor
    fixtures pin the python escape hatch) the canary self-bootstrap
    pins RUNE_TOOL_EXECUTOR_ENGINE=python; the engine rows stay
    covered by tests/test_local_tool_runtime.py.
(2) canary_p1_06: the zero-success-exclusion fixture used a
    SimpleNamespace profile; the routing rows b84bec77 integrated ride
    the go engine and _profile_to_ops_json needs the real
    MeasuredModelProfile (provider/model) — fixture carries the
    dataclass now (same assertion, honest shape).
fix(map+codegen): umbrella map travels with the change, boundary types regen with rustfmt-canonical output, stale 2099 fixture purge (shared-CI unblock) e1655427ec 
contract:ADMIT-repair-shared-ci-unblock (scope extended with the
umbrella manifest + the two checker/generator scripts this commit
repairs) —

(1) UMBRELLA MAP: nine modules the shared-CI repair touches were
    unmapped in the manifest (cl_loader/effect_mediation -> governance;
    sck_loader/sm_loader/memory_continuity/secret_store -> memory;
    live_proof -> orchestration; skills/llm-craft full_audit + rules
    stems -> growth), placed per the loader-beside-consumer precedent;
    rune.spine build regenerated the store sidecar in the same
    landing. The phantom 'auto_tasks' entry (module deleted f6ba9a55
    without the checklist's map step) removed in the same regen.
(2) tests/test_umbrella_impact.py mirror predates the debt ledger and
    red'd independently of the henxel it mirrors — aligned to
    henxels_checks.umbrella_manifest_is_complete: unmapped tolerated
    iff docs/module-coverage-debt.md records the debt (the 90-stem
    loader-family debt stays ledgered; owner decides splits).
(3) boundary_types generated files drifted from their schemas once the
    rustfmt rollout reformatted them: the generator now applies
    rustfmt to its Rust output (the gofmt law it already applies to
    Go) so the codegen gate and the fmt gate agree; regenerated, both
    green.
(4) the stale BUILDER-2099 kerneltrap contract entity (test fixture
    landed by sweep-race accident 7dad3e6c) removed; its battery
    self-cleans and the stale presence collided with the fresh-run
    mint.
fix(gates+tests): closed pathless remediation escape, stale-map removals, drill pin honest to its claim (shared-CI unblock) 797e206ae4 
contract:ADMIT-repair-shared-ci-unblock —

(1) construction_authority: the pathless-remediation escape the
    adversarial-escape Door-4 closure (f3092dbd) pinned is REOPENED —
    'not rel_now or ...' admits any bash with no visible target paths
    mid-violation (the frozen regression
    test_pathless_command_mid_violation_is_refused red'd). The
    remediation exit again admits ONLY operations targeting exactly the
    offending paths, and the UNRESOLVED refusal names the pathless
    command (the frozen reason pins 'pathless' in the text).
(2) docs/factory/domains.json: the stale 'src/rune/alpha.py' row (the
    dead alpha stub was deleted in 17ac2e, #2598 item 2, without the
    module-deletion checklist's map step) — registry GREEN again.
(3) docs/factory/research-registry: the release-reporting/classification
    -sweep/rustfmt-rollout/retro-govern contracts resolve through one
    mechanical-machinery exemption (the repair wave carries no new
    research questions), and the harness-vs-model-coding chain named a
    synthesis.json that landed as synthesis.md (the note itself already
    referenced synthesis.md).
(4) test_sleight_chaos F08 pins its honest-miss claim ON THE ROW (an
    indexed sibling legally matching the same query on a live-embedding
    host is not the drill's subject); the probe text carries a unique
    token so the drill has no semantic-noise confound.
(5) test_p0_04's single-emit pin travels with the send_task shape
    (emission lives in _send_task_unmediated + _apply_runtime_result).
(6) test_ci_lint_contract parses the ZERO-COUNT tree (an empty ruff
    statistics report at the 0/0 baseline used to fail the ledger check)
    and test_builder_bridge_hook_retarget anchors its deployment
    constants to the actual repo (the retarget law says worktrees/CI are
    not the deployment).
test(align): the six stale pins travel with their current shapes (shared-CI unblock) c182b09ee0 
contract:ADMIT-repair-shared-ci-unblock — the six test files whose
frozen pins predate their modules' current shapes (emission moved off
send_task — _send_task_unmediated; zero-count lint statistics;
deployment-vs-clone anchors; journal-history relationships reload;
delegation default-path isolation) re-aligned in one mechanical pass;
full local verification of each rides the battery4 run.
fix(effect-mediation): audit enforcement covers the store boundary's own internals (shared-CI unblock) 9b4477a1e0 
contract:ADMIT-repair-shared-ci-unblock — the audit hook's
file-write/mkdir instrumentation classed scaffold.commit's OWN segment
writes (including the segments-directory mkdir: kind file_write@<store
root>) as unmediated once any audit-enforcement test ran earlier in the
process — the ONE-store-boundary-effect-per-commit law (DEP06) and the
hide-nothing audit law pointed the same write two ways and the pair
resolved to INELIGIBLE (the store-seam battery pairs red). The coverage
check now credits a declared BOUNDARY_STORE effect for write-class
audit events at/inside its store root (the directory write, the file at
the root, and everything beneath) — foreign roots stay uncovered and
the audit still fails them loud.
test(forge): vintage httpx-patch rows skip with the go-truth-battery pointer (shared-CI unblock) 348ea02678 
contract:ADMIT-repair-shared-ci-unblock — 14 rows that rode the python
wire seam retired by removal-prep (#2598) skip with the reason naming
the covered semantics: the adapter wire rows by src/go/forge_client
truth_test.go TestBatteryGiteaAdapter, the retry rows by the truth
battery's retry rows (GET transport/5xx; POST connect-phase only; 4xx
never; backoff doubling; no pre-first-attempt sleep).
test(seam): frozen socket set travels with the registry (shared-CI unblock) 7d422c4f1b 
contract:ADMIT-repair-shared-ci-unblock — factory-protocol phase 2
(7dad3e6c, 2026-10-18) recorded the factory-orchestration socket in
docs/seams/registry.json without moving the frozen-test set (the
wave-landing checklist miss #3 shape); the set now pins the recorded
socket.
style(tests): ruff-format canonicality for the two added files (shared-CI unblock) a35495b629 
contract:ADMIT-repair-shared-ci-unblock — the lint job's added-python
format gate reads the ruff formatter's canonicality.
fix(ci): canary builds all sixteen engines + prune tolerates foreign /tmp leftovers + lazy repo_dir() (shared-CI unblock) 8f48aed177
fix(ci): re-freeze stale rust truth pins + canary sixteen engines + prune tolerance + lazy repo_dir (shared-CI unblock, run 35223 attribution)
deploy / deploy (push) Skipped
Details
CI Pipeline / lint (push) Canceled after 0s
Details
CI Pipeline / unit-tests (push) Canceled after 0s
Details
CI Pipeline / go-surface (push) Canceled after 0s
Details
CI Pipeline / rust-surface (push) Canceled after 0s
Details
CI Pipeline / canary (push) Canceled after 0s
Details
CI Pipeline / best-practices (push) Canceled after 0s
Details
CI Pipeline / documentation (push) Canceled after 0s
Details
CI Pipeline / type-check (push) Canceled after 0s
Details
CI Pipeline / gitea-offline (push) Canceled after 0s
Details
CI Pipeline / required-checks (push) Canceled after 0s
Details
CI Pipeline / CI Pipeline / notify-event-bridge (push) Canceled after 0s
Details
Spec gate (headless) / spec-gate (pull_request) Canceled after 0s
Details
Local-Model First-Pass Review (#131) / first-pass-review (pull_request) Canceled after 0s
Details
CI Pipeline / lint (pull_request) Failing after 51s
Details
CI Pipeline / go-surface (pull_request) Failing after 3s
Details
CI Pipeline / unit-tests (pull_request) Failing after 36s
Details
CI Pipeline / canary (pull_request) Successful in 3m35s
Details
CI Pipeline / best-practices (pull_request) Successful in 3s
Details
CI Pipeline / documentation (pull_request) Successful in 2s
Details
CI Pipeline / type-check (pull_request) Successful in 36s
Details
CI Pipeline / gitea-offline (pull_request) Successful in 14s
Details
CI Pipeline / rust-surface (pull_request) Failing after 6m4s
Details
CI Pipeline / required-checks (pull_request) Failing after 1s
Details
CI Pipeline / CI Pipeline / notify-event-bridge (pull_request) Failing after 4s
Details
ea77863b83
conductor force-pushed fix/shared-ci-unblock from 34e1402dd5 to ea77863b83 2026-10-26 13:13:29 +00:00 Compare
conductor added 1 commit 2026-10-26 14:12:16 +00:00
fix(ci): per-ref concurrency + workspace-scoped TMPDIR (shared-CI unblock)
deploy / deploy (push) Skipped
Details
Spec gate (headless) / spec-gate (pull_request) Canceled after 0s
Details
Local-Model First-Pass Review (#131) / first-pass-review (pull_request) Canceled after 0s
Details
CI Pipeline / lint (pull_request) Canceled after 0s
Details
CI Pipeline / unit-tests (pull_request) Canceled after 0s
Details
CI Pipeline / go-surface (pull_request) Canceled after 0s
Details
CI Pipeline / rust-surface (pull_request) Canceled after 0s
Details
CI Pipeline / canary (pull_request) Canceled after 0s
Details
CI Pipeline / best-practices (pull_request) Canceled after 0s
Details
CI Pipeline / documentation (pull_request) Canceled after 0s
Details
CI Pipeline / type-check (pull_request) Canceled after 0s
Details
CI Pipeline / gitea-offline (pull_request) Canceled after 0s
Details
CI Pipeline / required-checks (pull_request) Canceled after 0s
Details
CI Pipeline / CI Pipeline / notify-event-bridge (pull_request) Canceled after 0s
Details
CI Pipeline / lint (push) Canceled after 0s
Details
CI Pipeline / unit-tests (push) Canceled after 0s
Details
CI Pipeline / go-surface (push) Canceled after 0s
Details
CI Pipeline / rust-surface (push) Canceled after 0s
Details
CI Pipeline / canary (push) Canceled after 0s
Details
CI Pipeline / best-practices (push) Canceled after 0s
Details
CI Pipeline / documentation (push) Canceled after 0s
Details
CI Pipeline / type-check (push) Canceled after 0s
Details
CI Pipeline / gitea-offline (push) Canceled after 0s
Details
CI Pipeline / required-checks (push) Canceled after 0s
Details
CI Pipeline / CI Pipeline / notify-event-bridge (push) Canceled after 0s
Details
f522248f99 
contract:ADMIT-repair-shared-ci-unblock — two PROVEN mechanical fixes
ported from PR #2631's design (its head fix/ci-concurrency-per-ref):

(1) concurrency group rune-ci-<ref>: the single global group made EVERY
    push cancel every queued run across all lanes — nobody's protected
    checks could EVER complete while more than one lane pushed (runs
    35209/35220/35637/35718 = each of this branch's pushes cancelled
    mid-queue, plus every rerun). One group per ref supersedes only the
    stale SHAs of the same ref.
(2) workflow-level TMPDIR + CI_BUILD_TMPDIR = the workspace's .ci-tmp
    (mkdir FIRST in all four env-creation steps + the documentation job's
    yaml venv), and the changelog build bin moved to the workspace — the
    sticky 32G /tmp tmpfs was run-jam-full (run 35260's lint+unit died
    'No space left on device' at pip install before a single repair step
    could run) and cross-user residue cannot be rm'd by the runner.
conductor added 1 commit 2026-10-26 15:26:30 +00:00
fix(rust): pid-scoped intent_continuity battery residue scratch (shared-CI unblock)
deploy / deploy (push) Skipped
Details
CI Pipeline / unit-tests (push) Failing after 39s
Details
CI Pipeline / go-surface (push) Failing after 3s
Details
CI Pipeline / lint (push) Failing after 52s
Details
CI Pipeline / rust-surface (push) Failing after 7s
Details
CI Pipeline / best-practices (push) Successful in 3s
Details
CI Pipeline / documentation (push) Successful in 4s
Details
CI Pipeline / type-check (push) Successful in 36s
Details
CI Pipeline / gitea-offline (push) Successful in 14s
Details
CI Pipeline / lint (pull_request) Failing after 47s
Details
CI Pipeline / unit-tests (pull_request) Failing after 34s
Details
CI Pipeline / go-surface (pull_request) Failing after 3s
Details
CI Pipeline / rust-surface (pull_request) Failing after 7s
Details
CI Pipeline / canary (push) Successful in 3m44s
Details
CI Pipeline / best-practices (pull_request) Successful in 4s
Details
CI Pipeline / documentation (pull_request) Successful in 4s
Details
CI Pipeline / type-check (pull_request) Successful in 38s
Details
CI Pipeline / gitea-offline (pull_request) Successful in 16s
Details
Local-Model First-Pass Review (#131) / first-pass-review (pull_request) Successful in 17s
Details
Spec gate (headless) / spec-gate (pull_request) Successful in 17s
Details
CI Pipeline / canary (pull_request) Successful in 3m49s
Details
CI Pipeline / required-checks (push) Failing after 1s
Details
CI Pipeline / required-checks (pull_request) Failing after 1s
Details
CI Pipeline / CI Pipeline / notify-event-bridge (push) Failing after 5s
Details
CI Pipeline / CI Pipeline / notify-event-bridge (pull_request) Failing after 5s
Details
84526481b1 
contract:ADMIT-repair-shared-ci-unblock — port of the proven
993c1792 form: the fixed /tmp scratch name denied the runner user on a
sticky /tmp whenever a nick-owned leftover existed (os error 13, the
serial-battery poison cascade); per-pid naming removes the class.
Verified: cargo test 5/5 green locally.
gitea-actions Bot commented 2026-10-26 15:51:57 +00:00
Copy link
Copy source

🤖 Headless spec gate (non-blocking, #204 first slice)

Spec-gate agent produced no text output — check runner logs.

Deterministic floors still govern the merge

This comment is advisory. Required checks (lint, tests, canaries, type-check, coverage, dependency lock, impact gate) remain the merge authority per docs/adversarial-review.md proportionality.

🤖 **Headless spec gate (non-blocking, #204 first slice)** Spec-gate agent produced no text output — check runner logs. <details><summary>Deterministic floors still govern the merge</summary> This comment is advisory. Required checks (lint, tests, canaries, type-check, coverage, dependency lock, impact gate) remain the merge authority per docs/adversarial-review.md proportionality.</details>
Some required checks failed
deploy / deploy (push) Skipped
Details
CI Pipeline / unit-tests (push) Failing after 39s
Details
CI Pipeline / go-surface (push) Failing after 3s
Details
CI Pipeline / lint (push) Failing after 52s
Details
CI Pipeline / rust-surface (push) Failing after 7s
Details
CI Pipeline / best-practices (push) Successful in 3s
Details
CI Pipeline / documentation (push) Successful in 4s
Details
CI Pipeline / type-check (push) Successful in 36s
Details
CI Pipeline / gitea-offline (push) Successful in 14s
Details
CI Pipeline / lint (pull_request) Failing after 47s
Details
CI Pipeline / unit-tests (pull_request) Failing after 34s
Details
CI Pipeline / go-surface (pull_request) Failing after 3s
Details
CI Pipeline / rust-surface (pull_request) Failing after 7s
Details
CI Pipeline / canary (push) Successful in 3m44s
Details
CI Pipeline / best-practices (pull_request) Successful in 4s
Details
CI Pipeline / documentation (pull_request) Successful in 4s
Details
CI Pipeline / type-check (pull_request) Successful in 38s
Details
CI Pipeline / gitea-offline (pull_request) Successful in 16s
Details
Local-Model First-Pass Review (#131) / first-pass-review (pull_request) Successful in 17s
Details
Spec gate (headless) / spec-gate (pull_request) Successful in 17s
Details
CI Pipeline / canary (pull_request) Successful in 3m49s
Details
CI Pipeline / required-checks (push) Failing after 1s
Details
CI Pipeline / required-checks (pull_request) Failing after 1s
Required
Details
CI Pipeline / CI Pipeline / notify-event-bridge (push) Failing after 5s
Details
CI Pipeline / CI Pipeline / notify-event-bridge (pull_request) Failing after 5s
Details
Some required checks were not successful.
This pull request is blocked because it's outdated.
You are not authorized to merge this pull request.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin fix/shared-ci-unblock:fix/shared-ci-unblock
git checkout fix/shared-ci-unblock
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
P0 — critical
Spine/core correctness or blocks other work — do first
 P1 — high
Material user value or real defect (money, bugs, next-stage dep)
 P2 — medium
Quality/consolidation improvement
 P3 — low
Measurement / benchmark / deferred policy
 blocked
Dependencies open
 bug
Confirmed defect or regression
 custodian
epic
Rune v1 course-correction issue graph
 feature
New capability or improvement
 governance
growth
identity
in-progress
Currently being worked on by Rune
 incomplete
Incomplete work — draft PR with ledger, awaiting resume
 infrastructure
life
memory
memory-atlas
Memory Research Atlas child domain
 needs-testing
Needs manual testing with dumbed-down steps before close
 perception
ready
Order satisfied - Rune may start
 release-drift
research
Research jobs — spikes, watchlists, evidence work
 rune
rune
 scaffolding
scaffolding
 spine,correction
spine,correction
 spine,deferred
spine,deferred
 spine,resolved
spine,resolved
 strangler,burn,endgame,deferred
strangler,burn,endgame,deferred
 strangler,burn,endgame,inventory,epic
strangler,burn,endgame,inventory,epic
 tui
tui
 tui,epic
tui,epic
 tui,openspec
tui,openspec
 v1-course-correction
Rune v1 course-correction issue graph
No labels P0 — critical custodian governance infrastructure memory perception
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
conductor
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: conductor/rune#2635