Skip to content

skill: reword one phrase to unbreak the gate my own correction broke - #3251

Merged
gHashTag merged 2 commits into
masterfrom
fix-the-gate-i-broke
Sep 5, 2026
Merged

gHashTag merged 2 commits into
masterfrom
fix-the-gate-i-broke

Conversation

@gHashTag

@gHashTag gHashTag commented Sep 5, 2026

Copy link
Copy Markdown
Collaborator

Documented t27c subcommands exist has been red on master since 02:21Z. I put it
there, and when I looked I concluded the opposite.

What happened

#3231 corrected a claim of mine, and its text explains that t27c gen-zig is not a
subcommand — with the name in backticks, which is exactly what the gate reads. The
gate accepts a disclaimer matching not implemented|not built|does not exist|never existed|no such subcommand|.... My wording was "which is not a subcommand": right in
meaning, matching none of those patterns.

#3231 merged at 02:21:25Z. The gate's first master failure is at 02:21:28Z — the
run its own merge triggered. Seven successes before it, five failures after.

The misreading, which is the part worth keeping

I saw three consecutive red master runs and wrote "this is a pre-existing red gate,
not something my PR caused"
. tri pr ready agreed in its own words: "also failing in
4 other place(s) — pre-existing"
.

Both readings are accurate and neither means what I took it to mean. A defect merged
to master fails on every subsequent pull request, which is exactly what "pre-existing"
looks like to a tool that compares a branch against master.
The question that
separates them is one command: when did this gate last pass, and what landed between
then and the first failure.

The repair

One phrase — "which is not a subcommand" → "which does not exist as a subcommand".
The checker then reports:

ok: every t27c subcommand a live document names exists, and the 141 dead `tri`
mentions are the recorded ceiling.

The gate is well built: it names the file, the line, the phrase it wants, and where
the disclaimer may sit — on the line, in the paragraph, or in the heading above it.

Refs #3241

`Documented t27c subcommands exist` reads backticked `t27c <sub>` mentions in live
documents and fails on any name that does not exist, unless the document says so
in words it recognises: not implemented / not built / does not exist / never
existed / no such subcommand.

#3231 added a paragraph explaining that `t27c gen-zig` is not a subcommand. It
says the right thing and matches none of those patterns, so the gate went red.
#3231 merged at 02:21:25Z and the gate's first master failure is at 02:21:28Z --
the run its own merge triggered. Seven successes before, five failures after.

Worth recording: I then read three red master runs as evidence the gate was
pre-existing and not mine, and `tri pr ready` said "also failing in 4 other
place(s) -- pre-existing", which is true and does not mean what I took it for. A
defect merged to master fails on every later pull request, which is precisely what
pre-existing looks like from a branch-versus-master comparison. The separating
question is one command: when did this gate last pass, and what landed between.

Repair is one phrase. The checker now reports ok.

Refs #3241

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

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

@github-actions

github-actions Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-09-05 05:15:50 UTC

Summary

Status Count
Total Open PRs 21
PRs with Failing Checks 17
PRs with All Checks Green 4
READY 0
FAILING 17
PENDING 0

Seal Status

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

github-actions Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

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

@github-actions

github-actions Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-09-05 05:51:07 UTC

Summary

Status Count
Total Open PRs 20
PRs with Failing Checks 17
PRs with All Checks Green 3
READY 0
FAILING 17
PENDING 0

Seal Status

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

@gHashTag
gHashTag merged commit 80d43e2 into master Sep 5, 2026
27 of 28 checks passed
@gHashTag
gHashTag deleted the fix-the-gate-i-broke branch October 26, 2026 06:06
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