Skip to content

chore: label-hygiene F1c+F1d — rename phase1 gate and m0/m1 probe vocabulary - #4755

Merged
briansrls merged 3 commits into
mainfrom
session/gentle-hawk-530
Jun 12, 2026
Merged

briansrls merged 3 commits into
mainfrom
session/gentle-hawk-530

Conversation

@briansrls

@briansrls briansrls commented Jun 12, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Behavior-neutral label-hygiene (operator F1c+F1d, census docs/planning/label-hygiene-census-2026-06-12.md).

F1c — gate scripts + env vars (atomic per family)

Old New Rationale
scripts/v4-phase1-nat-semiring-rung-gate.sh scripts/v4-nat-semiring-rung-gate.sh Orchestrates rungs 0–2 acceptance matrix (dag parse + rust/python/go compile) for the phase1/nat_semiring fixture
scripts/v4-phase1-nat-semiring-python-runtime-gate.sh scripts/v4-nat-semiring-python-runtime-gate.sh Chained L1 gate: executes emitted Python laws after py_compile (runtime fixture exec)
scripts/v4-phase1-nat-semiring-go-compiler-slice-gate.sh scripts/v4-nat-semiring-go-compiler-slice-gate.sh Chained L1 gate: go build verdict for go_l1_nat_semiring_rung2 compiler-slice
V4_PHASE1_NAT_SEMIRING_OUT V4_NAT_SEMIRING_RUNG_GATE_OUT Emit tree shared by the rung-gate family
V4_PHASE1_NAT_SEMIRING_STRICT V4_NAT_SEMIRING_RUNG_GATE_STRICT Fail-closed on any rung/L1 failure in the parent gate
V4_PHASE1_NAT_SEMIRING_PYTHON_RUNTIME_STRICT V4_NAT_SEMIRING_PYTHON_RUNTIME_GATE_STRICT Fail-closed on L1 Python runtime gate alone
V4_PHASE1_NAT_SEMIRING_GO_COMPILER_SLICE_STRICT V4_NAT_SEMIRING_GO_COMPILER_SLICE_GATE_STRICT Fail-closed on L1 Go compiler-slice gate alone
V4_PHASE1_NAT_SEMIRING_{TIMEOUT,PYTHON,GO,RUSTC,GOFMT} V4_NAT_SEMIRING_GATE_{TIMEOUT,PYTHON,GO,RUSTC,GOFMT} Shared host-toolchain knobs for the gate family

F1d — ci-floor probes

Old New Rationale
v4-m1-rust-emit-probe.sh v4-rust-full-tree-emit-probe.sh CI fail-closed: gunbc compile --target rust over full src/v4 with zero diagnostics
V4_M1_RUST_EMIT_* / V4_M1_DAG_EMIT_* V4_RUST_FULL_TREE_EMIT_PROBE_* / V4_RUST_DAG_SHARED_CLOSURE_* Env vars name the rust full-tree probe and optional rust+dag shared-closure path
v4-m0-ts-emit-probe.sh deleted Dead script: not in ci.yml, zero bash invocations in repo (only a comment cite in comprep_add_body_emit_typescript.dag); gap unchanged, comment updated

Grep verification (zero remaining old names)

rg 'v4-phase1-nat-semiring|V4_PHASE1_NAT_SEMIRING|v4-m0-ts-emit-probe|v4-m1-rust-emit-probe|V4_M0_TS_EMIT|V4_M1_RUST_EMIT|V4_M1_DAG_EMIT|V4_M1_RUST_EMIT_PROBE|v4-typescript-structural-emit-probe'
# → no matches

Scope guards

CI exercise check (silent-disable audit)

Renamed surface Exercised in CI? Job / evidence
v4-rust-full-tree-emit-probe.sh + V4_RUST_* env vars Yes — executed ci_floor_emit step runs bash .github/ci-floor/v4-rust-full-tree-emit-probe.sh (wired in ci.yml)
scripts/v4-nat-semiring-*-gate.sh + V4_NAT_SEMIRING_* env vars No CI bash invoke Pre-rename state too: host transport scripts are not wired in ci.yml. Exercised locally by v4_emit_host_harness_test.rs (parse asserts + v4_nat_semiring_l1_go_compiler_slice_strict_missing_go_fails_closed runs rung gate with renamed env vars).
.dag host-gate path strings (rung_l1_go_compiler_slice.dag) Parse-only in CI ci_floor_emit compiles full src/v4 tree (module must parse/typecheck); does not execute bash gate paths at runtime.
v4_lens_gate / v4_lens_ci No — not in scope These jobs run v4-lens-ci-gate.sh + node-frontier witnesses only; they do not reference nat_semiring gate scripts or host-gate path strings.

Conclusion: F1d rust probe rename is CI-executed. F1c gate renames are grep-atomic + locally tested; the .dag path-string change rides the existing ci_floor_emit compile path (not lens jobs). No new silent-disable introduced vs pre-rename baseline (gates were already off-CI).

Test plan

  • bash -n on renamed gate scripts + rust probe
  • cargo test -p v3-compiler v4_nat_semiring_rung_gate
  • cargo test -p ci_affected_components
  • grep verification above

Brian Searls and others added 2 commits June 12, 2026 17:34
…robe vocabulary

Drop phase1/m0/m1 codenames from gate scripts, env vars, and ci-floor probes;
update all reader sites atomically (behavior-neutral).

Co-authored-by: Cursor <cursoragent@cursor.com>
@briansrls briansrls changed the title Label-hygiene F1c+F1d (ASAP, operator-mandated): rename phase1 gate vocabulary — V4_PHASE1_* env vars + 3 gate scripts, ALL reader sites + CI workflows updated atomically, behavior-neutral, named for what each gate actually toggles; plus m0/m1 probe scripts to descriptive names. Normal bar; do not t chore: label-hygiene F1c+F1d — rename phase1 gate and m0/m1 probe vocabulary Jun 12, 2026
@briansrls
briansrls marked this pull request as ready for review June 12, 2026 17:41
…ons)

Label-hygiene disposition: script was never wired in ci.yml and had zero
bash invocations — only a comment cite. Gap receipt unchanged in claim comment.

Co-authored-by: Cursor <cursoragent@cursor.com>
@briansrls
briansrls merged commit a260576 into main Jun 12, 2026
12 checks passed
@briansrls
briansrls deleted the session/gentle-hawk-530 branch June 12, 2026 19:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant