Skip to content

skill(ci-gates) 366: the largest first-error family is not the largest lever - #2927

Merged
gHashTag merged 2 commits into
masterfrom
w761
Aug 30, 2026
Merged

skill(ci-gates) 366: the largest first-error family is not the largest lever#2927
gHashTag merged 2 commits into
masterfrom
w761

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

A compiler stops reporting somewhere. Rank a backlog by first error and you
rank by position in the file, not by blocking power.

Measured on the C backend — 404 specs generate C that cc refuses:

rejected files                                   404
  ... carrying a scaffold error                  166
  ... where that is the ONLY family                0

The top family by first error was default_input/valid_input, 74 specs, with
a precedent already in the tree: W585 solved exactly this for Zig, and its own
comment names the C side — "75 of 296 C header failures". Fixing it perfectly
moves the accept count by zero.

The distribution nobody had printed:

distinct error families per file
  1 family:  20 files      <- the only real levers
  2:  42   3:  31   4:  78   5:  52   6:  45   7:  40   8+:  96

The median file carries four or five independent families. A backlog shaped like
this has no big lever, and knowing that is worth more than any single fix.

Among those twenty single-family files were four reporting "integer literal is
too large to be represented in any integer type"
— which became #2925. The
most-blocked family was noise and a least-blocked one was a real type-checker
defect.

Corollary for peer-backend oracles

Agreement is not evidence. Three backends emitted a 185-digit constant into a
u32 and agreed with each other; cc was the outlier and the only one that was
right. When the outlier has an independent standard behind it — a C compiler, a
proof assistant, a linker — weigh it above the majority rather than below.

Refs #2925

…t lever

A compiler stops reporting somewhere, so ranking a backlog by FIRST error ranks
by position in the file rather than by blocking power.

Measured on the C backend: 404 specs generate C that cc refuses. By first error
the top family was `default_input`/`valid_input`, 74 specs, with a precedent
already in the tree -- W585 solved exactly this for Zig and its own comment names
the C side. The question that killed it, asked before writing anything:

    rejected files                                   404
      ... carrying a scaffold error                  166
      ... where that is the ONLY family                0

The distribution nobody had printed:

    1 family:  20 files      <- the only real levers
    2: 42   3: 31   4: 78   5: 52   6: 45   7: 40   8+: 96

Among those twenty single-family files were four reporting "integer literal is
too large to be represented in any integer type" -- the defect that became
#2925. The most-blocked family was noise and a least-blocked one was real.

The section also records the corollary for peer-backend oracles: agreement is
not evidence. Three backends emitted a 185-digit constant into a u32 and agreed;
cc was the outlier and the only one that was right. When the outlier has an
independent standard behind it, weigh it above the majority rather than below.

Refs #2925
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-08-30 00:19:32 UTC

Summary

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

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=82e020cf95b2 != 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.

# Conflicts:
#	.claude/skills/ci-gates/SKILL.md
@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 94345c0 into master Aug 30, 2026
24 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-08-30 00:27:05 UTC

Summary

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

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=82e020cf95b2 != 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).

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