Skip to content

ci-gates 208: a tightened pattern is not a second opinion - #2808

Merged
gHashTag merged 1 commit into
masterfrom
w709-scanner-artifact-lesson
Aug 29, 2026
Merged

ci-gates 208: a tightened pattern is not a second opinion#2808
gHashTag merged 1 commit into
masterfrom
w709-scanner-artifact-lesson

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

Refs #2807

A scanner hunting for the adamw.t27 defect elsewhere reported 91 files with repeated top-level definitions, worst specs/numeric/gf16.t27 at 561 extras. Tightening the pattern to module indentation gave 43 files and 539 extras — close enough to feel confirmed.

Both runs were the same ruler. gf16.t27 has 110 Zig test blocks, each opening:

test "gf16_max_returns_greater" {
    const a = gf16_encode_f32(2.0);

const a at four spaces, inside a test body. The scanner had found local variables. Its real count is zero, and the corpus-wide number is withdrawn.

What settled it was a signal that does not pass through the name scanner at all: duplicated section banners. adamw.t27 carries // 1. Constants / // 2. Types / // 3. Core Functions twice (11/25/54 and 414/470/509); gf16.t27 has none. Exactly one file in specs/ fires both signals, and it is the one already read by hand.

The lesson, recorded as ci-gates 208: tightening a pattern is not a second opinion. Both runs shared the assumption that a const at module indentation is a module-scope declaration, and that assumption was the bug, so the stricter run inherited it intact.

Third scanner artifact this session — the for all census matching prose, the type reader dropping every pub field, and now this. All three produced a confident number; none was caught by re-reading the scanner.

Refs #2807

A scanner hunting for the adamw.t27 defect reported 91 files with repeated
top-level definitions. Tightening it to module indentation gave 43 and a
barely-moved count, which read as corroboration. Both runs shared the bug:
specs/numeric/gf16.t27 has 110 Zig test blocks each opening `const a` at four
spaces, and the scanner was counting local variables. Its real count is zero.

Settled by duplicated section banners -- a signal that does not pass through
the name scanner. Exactly one file in specs/ fires both, and it is the one
already read by hand. The corpus-wide number is withdrawn.

Third scanner artifact this session; none was caught by re-reading the scanner.
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-08-29 11:48:36 UTC

Summary

Status Count
Total Open PRs 9
PRs with Failing Checks 7
PRs with All Checks Green 2
READY 0
FAILING 7
PENDING 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=d25ac0cc159e != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@github-actions

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@gHashTag
gHashTag merged commit b01ecb5 into master Aug 29, 2026
23 checks passed
@gHashTag
gHashTag deleted the w709-scanner-artifact-lesson branch August 29, 2026 11:50
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