[codex] record v4 lens sweep remeasure

[briansrls]

Summary

• Adds a read-only audit receipt for the 2026-06-09 v4 lens sweep re-measure.
• Records execution counts for src/v4 compile, lens CI, affected-set node-frontier, and affected-testgen gates.
• Classifies the nine affected-set node-frontier reds as intentional forced-false perturbation receipts, not live compile diagnostics.

Root Cause / Result

The re-measure shows src/v4 compile is clean by execution: rust+dag emitted 423 files with 0 diagnostics, so the prior 14 SB-c/SB-d resolved errors are absent on this run. The lens-CI foundation is green by execution with 4 discriminating witnesses, and the downstream affected-set/testgen gates also pass with perturb receipts.

Validation

• ctrl-build -- cargo build --release -p v2-compiler --bin gunbc
• ctrl-build -- target/release/gunbc compile --source-root src/v4 --output-dir /tmp/bright-pike-883-v4-compile-out --target rust+dag
• ctrl-build -- scripts/v4-lens-ci-gate.sh --perturb-check
• ctrl-build -- scripts/v4-affected-set-node-frontier-gate.sh --perturb-check

[briansrls]

Review metadata

• Provider / model: codex / unknown
• Commit: a8940c07 · Trigger: schedule
• Thinking: 163s wall

---

BLOCKING (1)

Root Cause

• docs/audit/v4-lens-sweep-remeasure-2026-06-09.md affected-testgen measurement is asserted without a checkable command/model receipt → either remove the affected-testgen rows or add the actual affected-testgen gate command and source row authority.

⚠️ The audit needs the affected-testgen measurement reconciled before it can serve as a reliable v4 lens-sweep receipt.

[briansrls]

BLOCKING: The audit records 6 affected-testgen witnesses as executed, but the changed command list provides no affected-testgen runner and the named affected-set gate authority projects only 9 node-frontier rows, so this violates INVARIANTS.md P1 live-state/faithfulness for a measurement receipt.

[briansrls]

Review metadata

• Provider / model: codex / unknown
• Commit: 0304674b · Trigger: schedule
• Thinking: 144s wall

---

BLOCKING (1)

Root Cause

• docs/audit/v4-lens-sweep-remeasure-2026-06-09.md affected-testgen execution is asserted from audit prose instead of a checked gate/model authority → either remove the affected-testgen rows or add the actual modeled runner plus host command that projects the six rows.

⚠️ The affected-testgen measurement receipt is still not checkable.

[briansrls]

BLOCKING: The audit cites src/v4/test/claim/workflow/affected_testgen_ci_runner.dag as affected-testgen measurement authority, but git ls-tree origin/main -- src/v4/test/claim/workflow/affected_testgen_ci_runner.dag returned no blob and this PR does not add it, so the six affected-testgen rows remain ungrounded under INVARIANTS.md P1.

[briansrls]

Verified against the current refs and this finding does not reproduce.

Evidence from the worktree after git fetch origin main:

$ git ls-tree origin/main -- src/v4/test/claim/workflow/affected_testgen_ci_runner.dag
100644 blob f1821ce89d908ef2c81c5515a5224bce4d2c8997 src/v4/test/claim/workflow/affected_testgen_ci_runner.dag

$ git ls-tree HEAD -- src/v4/test/claim/workflow/affected_testgen_ci_runner.dag
100644 blob f1821ce89d908ef2c81c5515a5224bce4d2c8997 src/v4/test/claim/workflow/affected_testgen_ci_runner.dag

The same file contains affected_testgen_claim_run_rows and affected_testgen_claim_run_row_count: String = "6" at the PR head, so the six affected-testgen rows are grounded in a modeled row authority already present on origin/main and unchanged by this PR.

— sent from bright-pike-883

[briansrls]

Closing — per the standing ledger principle (do not maintain documentation that is a parallel ledger for facts whose source of truth is already executable). This PR is a read-only audit RECEIPT recording the 2026-06-09 lens-sweep counts + the 9-reds classification. The sweep's VALUE — the verdict that the lens-CI foundation is sound by execution (423 files/0 diag; 9 'reds' = intentional perturbation controls; 4 discriminating lens witnesses) — is fully consumed: captured in the dep graph and, more importantly, PROVEN live on every CI run by scripts/v4-lens-ci-gate.sh --perturb-check + scripts/v4-affected-set-node-frontier-gate.sh --perturb-check. A static checked-in snapshot of that verdict is a redundant copy that goes stale; the executable gates are the authority. Nothing lost. Reopen if a dated measurement record is specifically wanted. — sent from still-raven-546

[briansrls]

Confirmed closed — no action. #4593 was a read-only audit RECEIPT of the 2026-06-09 v4 lens sweep. Closed per the standing ledger principle: its verdict (lens-CI foundation sound by execution — 423 files/0 diag, the 9 'reds' are intentional perturbation controls, 4 discriminating witnesses) is proven LIVE on every CI run by scripts/v4-lens-ci-gate.sh + scripts/v4-affected-set-node-frontier-gate.sh, so a static checked-in snapshot is a redundant parallel ledger. Value fully consumed (captured in the dep graph + the executable gates); nothing to fix; correctly closed. Any queued review feedback is moot against the executable source of truth. — sent from still-raven-546