Frontier survey did not complete: interrupted-run receipt (0 receipts) + roster provenance rung-inflation finding

dag/gunbc/ci_layer_roots.dag

@@ -868,7 +868,7 @@ fn known_red_probe_roster() -> List<ScheduleWitnessEntry> {
 
 data long_lane_exclusion_note: String = "test/claim/long/ is the LONG-test home (operator 5-second rule, 2026-07-12; authority + enforcement: gunbc_ci_fast_lane_rule_note / gunbc_ci_fast_lane_witness_eval_budget in v2.workflow.ci_floor_plan): a witness whose own eval reaches 5s does not run in per-PR discovery — the executor's cooperative eval deadline REDs it by name (EvalBudgetExceeded), and the fix is moving its file here (dag/test/claim/long/, src/v2/test/claim/long/), where discovery excludes it at dir grain and it runs via the local recipe (claim_batch --source-root dag --source-root src/v2 --entry <file> --functions <csv>) or the scheduled lane's future enrollment. First residents (receipted): s1_closure_receipt_test (whole-closure re-parse through the interpreted v2 frontend, 90+min eval, the run-29183446733 wedge class) and self_host_module_emit_derisk_test (~31s/witness). Named consumer with file-grain exclusion row: compiler_frontier_per_module_probe_test.dag (compiler_frontier_per_module_probe_exclusion_note). Membership here was called a HOME rather than a per-file ruling on the ground that the 5s deadline makes an over-budget fast-lane witness unwritable-in-place, so the roster could not silently grow stale. THAT SENTENCE WAS FALSE AND IS RETRACTED (2026-08-04). The deadline is evaluated only while a witness RUNS; relocating its file under this prefix is precisely what stops it running, so the claimed construction backstop is disarmed by the exact move it was supposed to govern, and the home grew by whatever anyone moved into it. BudgetExceeded is an interruption plus a measured lower bound on cost — never a semantic verdict on a witness, and never a discharge of one by causing its relocation. Receipt: gunbc#7762 commit 0cfd199f8, thirteen witnesses relocated here under the title fix CI fast-lane budget failures with a claim_batch command line as their only stated consumer and no cadence row. WHAT NOW HOLDS THE LINE: this prefix still organizes the files, but it no longer answers the admission question. gunbc.witness_deferral_freeze enumerates the exact legacy identities path policy had already admitted, and any offline-classified witness outside that frozen set and outside gunbc.explicit_witness_admission refuses as UnclassifiedPathDeferral, while a frozen row the tree no longer carries refuses as StaleFrozenPathDeferral. Dissolve-on: the freeze reaching empty — every resident carrying an exact admission with a declared purpose, cost and executing cadence — at which point the pass-through arm and this dir row delete together."
 
-data compiler_frontier_per_module_probe_exclusion_note: String = "src/v2/test/claim/long/compiler_frontier_per_module_probe_test.dag is operator-ruled OFFLINE (Lane 1 exact-head closeout): fixture-free per-module frontier_probe_emit_from_ingest receipts over all 27 compiler modules exceed the 5s per-PR fast-lane eval budget; discovery excludes via test/claim/long/ dir grain and per-PR CI never executes these witnesses — green CI says nothing about execution_measurement counts unless the local recipe below ran at a pinned FrontierSurveySubject. LOCAL RECIPE (authority): (1) predecessors #7776, #7762, and #7767 are merged; authoritative 27/27 remains on operator hold; (2) from a clean detached worktree at the selected commit, cargo build --release -p v1-compiler --bin frontier_probe_survey; (3) primary: target/release/frontier_probe_survey with every --source-root via v2.workflow.frontier_probe_survey_transport survey_manifest_emit_args (one-shot over compiler_frontier_sweep_order at one subject; OOM fallback: docs/probes/run_frontier_probe_survey_per_module.sh — TSV wire carries rejection_chain and overlap_roster_detail projections, not full detail/assemble_detail variant AST on manifest-only round-trip; every shard carries complete FrontierSurveySubject, all 27 subjects must compare exactly equal); (4) emit host_frontier_probe_survey_manifest FrontierSurveyManifest to target/frontier-probe-survey/; (5) claim_batch --source-root src/v2 --source-root dag --source-root target/frontier-probe-survey --entry src/v2/test/claim/long/compiler_frontier_per_module_probe_test.dag --functions compiler_frontier_per_module_probe_survey_holds,compiler_frontier_gap_clustering_common_root_at_blocker_class_holds,compiler_frontier_wave2_blocker_partition_totality_holds,compiler_frontier_roster_bidirectional_totality_live_survey_holds,compiler_frontier_receipt_totality_wall_live_survey_holds,compiler_frontier_wave2_emit_surface_dominates_holds,compiler_frontier_wave2_sizing_band_a_leaf_count_holds. Dissolve-on: execution_measurement=27 at one pinned FrontierSurveySubject, frontier.dag rows hand-authored from manifest, totality wall witnesses pass via this recipe — then this note, the file-grain exclusion row, and the probe scaffold delete together."
+data compiler_frontier_per_module_probe_exclusion_note: String = "src/v2/test/claim/long/compiler_frontier_per_module_probe_test.dag is operator-ruled OFFLINE (Lane 1 exact-head closeout): fixture-free per-module frontier_probe_emit_from_ingest receipts over all 27 compiler modules exceed the 5s per-PR fast-lane eval budget; discovery excludes via test/claim/long/ dir grain and per-PR CI never executes these witnesses — green CI says nothing about execution_measurement counts unless the local recipe below ran at a pinned FrontierSurveySubject. LOCAL RECIPE (authority): (1) predecessors #7776, #7762, and #7767 are merged; authoritative 27/27 remains on operator hold; (2) from a clean detached worktree at the selected commit, cargo build --release -p v1-compiler --bin frontier_probe_survey — WRAP IT AS ctrl-build --local, which is REQUIRED and not a preference: ctrl-build defaults to CTRL_BUILD_MODE=remote in session containers and BuildBuddy refuses a detached worktree ('remote config: get base branch and commit: unexpected branch state * (no branch)'), so step (2)'s mandated DETACHED worktree and the default remote build path are mutually exclusive and anyone following this recipe verbatim hits it first (measured tidy-bee-50 2026-08-06); (3) primary: target/release/frontier_probe_survey with every --source-root via v2.workflow.frontier_probe_survey_transport survey_manifest_emit_args (one-shot over compiler_frontier_sweep_order at one subject; OOM fallback: docs/probes/run_frontier_probe_survey_per_module.sh — TSV wire carries rejection_chain and overlap_roster_detail projections, not full detail/assemble_detail variant AST on manifest-only round-trip; every shard carries complete FrontierSurveySubject, all 27 subjects must compare exactly equal); (4) emit host_frontier_probe_survey_manifest FrontierSurveyManifest to target/frontier-probe-survey/; (5) claim_batch --source-root src/v2 --source-root dag --source-root target/frontier-probe-survey --entry src/v2/test/claim/long/compiler_frontier_per_module_probe_test.dag --functions compiler_frontier_per_module_probe_survey_holds,compiler_frontier_gap_clustering_common_root_at_blocker_class_holds,compiler_frontier_wave2_blocker_partition_totality_holds,compiler_frontier_roster_bidirectional_totality_live_survey_holds,compiler_frontier_receipt_totality_wall_live_survey_holds,compiler_frontier_wave2_emit_surface_dominates_holds,compiler_frontier_wave2_sizing_band_a_leaf_count_holds. RUNS INTERRUPTED, not only held: step (3) has not yet produced a receipt for ANY module — six probe invocations were SIGKILLed with zero receipts, on both the primary one-shot and the per-module path. The CAUSE IS OPEN and is NOT a demonstrated capacity limit: the cgroup never reached its own cap (memory.events max 0, oom 0; memory.peak 8.5 GiB against a 31.3 GiB memory.max), so the kills came from outside it and probe memory cost is UNMEASURED rather than high. 'Unreachable' is NOT established — treat this recipe as interrupted and retryable, and per operator ruling retry it in a fresh job or runner whose real kill boundary is observable rather than trimming the probe to fit. Authority for the measurements and the withdrawn earlier claims is v2.compiler.self_host.frontier_probe_survey frontier_probe_run_interruption_note, which this clause must not restate beyond pointing at it. Dissolve-on: execution_measurement=27 at one pinned FrontierSurveySubject, frontier.dag rows hand-authored from manifest, totality wall witnesses pass via this recipe — then this note, the file-grain exclusion row, and the probe scaffold delete together."
 
 data wet_integration_offline_note: String = "Four wet-integration entries above (host_effect_apply, deploy_access_privilege, ci_deploy_observed_wet, random_bytes_csprng) are OFFLINE per the hermetic-floor posture (operator 2026-07-11: integration-style witnesses must not run regularly; CI runs hermetic/mocked behavior checks). Each performs genuinely live host effects the hermetic envelope refuses by construction: host_effect_apply drives real LocalShell/SSH host effects (the 133s row atop the slow-witness census), deploy_access_privilege applies privileged shell mutations through fixture actors, ci_deploy_observed_wet shells whoami + sudo -n, random_bytes_csprng reads host entropy. Hermetic duals stay discovered where they exist (the ci_deploy split keeps the pure half; deploy_access_check(access, actor) is the mock-shaped dual). Local recipe: claim_batch --wet --source-root dag --source-root src/v2 --entry <entry> per file. Dissolve-on: the scheduled (nightly) lane un-darkens and admits wet integration rows under its own budget — then these four enroll there as declared execution rows and the exclusion rows delete."
 

dag/gunbc/doc_graph_roots.dag

@@ -315,6 +315,13 @@ data hand_authored_doc_binds: List<HandAuthoredDocBind> = [
     additional_works: [DeclarationRef { module_path: "v2.compiler.self_host.frontier", decl_name: "compiler_frontier_receipt_totality_wall_holds", field: WholeDeclaration }],
     dissolution: HasTrigger { text: "execution_measurement=27 at one pinned source_head in host_frontier_probe_survey_manifest, frontier.dag rows hand-authored from that manifest, compiler_frontier_per_module_probe_survey_holds greens, and totality wall witnesses pass — then this interim audit receipt deletes with this row" },
   },
+  HandAuthoredDocBind {
+    home: ProbeDoc,
+    slug: "frontier_probe_run_interrupted_2026-08-06",
+    primary_work: DeclarationRef { module_path: "v2.compiler.self_host.frontier_probe_survey", decl_name: "frontier_probe_run_interruption_note", field: WholeDeclaration },
+    additional_works: [DeclarationRef { module_path: "v2.compiler.self_host.frontier_probe_survey", decl_name: "frontier_roster_provenance_constructor_inflation_note", field: WholeDeclaration }],
+    dissolution: HasTrigger { text: "the probe emits a receipt for at least one module at a pinned FrontierSurveySubject and roster row provenance becomes structural — then this interrupted-run receipt deletes with this row" },
+  },
   HandAuthoredDocBind {
     home: ProbeDoc,
     slug: "srv2-05-native-agreement-divergence-diagnosis",