Skip to content

docs(loop): R12 denied a spelling the gate accepts - #3369

Merged
gHashTag merged 2 commits into
masterfrom
s2-r12
Sep 6, 2026
Merged

docs(loop): R12 denied a spelling the gate accepts#3369
gHashTag merged 2 commits into
masterfrom
s2-r12

Conversation

@gHashTag

@gHashTag gHashTag commented Sep 6, 2026

Copy link
Copy Markdown
Owner

Refs #3368

Two sentences in R12 contradicted machine-readable truths in this repository, and both were wrong on the day they were written.

1. Refs #N DOES satisfy check-linked-issue

R12 said it does not. The gate at .github/workflows/issue-gate.yml:69:

grep -oiE '(Closes?|Fixes?|Resolves?|Refs?|Updates?)\s*#[0-9]+'

Refs? landed 2026-07-07 (5850c302e). The R12 denial was written 2026-08-20 — 44 days late on arrival, not stale. Seven readers in this tree carry that dictionary; R12 was the sole dissenter. And it demanded the one spelling R11 forbids nineteen lines above ("AUTOCLOSING ISSUES IS FORBIDDEN"), since Closes autocloses on merge.

The file's own history is the sharpest evidence: the most recent commit to LOOP-RULES.md is bb60ddc03, "docs(loop): R17 … (Refs #3357) (#3358)". The PR that last edited the rules file disproved line 230 while merging, and left it standing.

The repair does not re-transcribe the dictionary — it points at issue-gate.yml:69. A hand-copied copy missing Refs once matched 4 references where the gate matched 33, and this sentence was the next copy to go wrong; the rule now says so, so the third copy is not written either.

2. R12 pointed authors at a frozen archive

It told authors to add a section to docs/NOW.md, whose first line is "FROZEN ARCHIVE -- do not add entries here" — frozen in f5be7dc1c (#2298) for exactly the collision reason R12 exists to avoid. .claude/skills/spec-first-ternary-nn.md:62 carried the same instruction and is corrected with it.

The guard is declined, on a measurement

Every mention of docs/NOW.md under .github/workflows/, scripts/ and .githooks/ is a comment — zero lines reject an edit, so the freeze is prose only and an author following the stale instruction passes all four required checks.

But the obvious rule — fail any diff containing the fileis too broad. Of the 600 commits since the freeze, 2 touched it, and one (458ec0bd6) repairs damaged entries in the archive. The banner forbids adding entries, not touching the file. A guard that blocks a legitimate repair is the shape this repository documents as one that gets muted.

The narrow rule that would work — fail a diff that adds a ## heading — is still a change to a required context, so it is filed in #3368 rather than done here.

Seal

LOOP-RULES.sha256 moves with the rule text in the same commit (R6 — the seal certifies identity, not correctness).

Provenance

Found by the adversarial sweep for #3355. These two are the mirror of that class: the truth is machine-readable and the prose is the stale transcription.

Two sentences in R12 contradicted machine-readable truths in this repository,
and both were wrong on the day they were written.

`Refs #N` DOES satisfy `check-linked-issue`. The matcher at
`.github/workflows/issue-gate.yml:69` is
`(Closes?|Fixes?|Resolves?|Refs?|Updates?)\s*#[0-9]+` and has carried `Refs?`
since `5850c302e` (2026-07-07). R12's denial was written 2026-08-20: 44 days
late on arrival, not stale. Seven readers in this tree carry that dictionary and
R12 was the only dissenter -- while demanding the one spelling R11 forbids
nineteen lines above, since `Closes` autocloses on merge.

The repair does NOT re-transcribe the dictionary; it points at the gate. A
hand-copied copy missing `Refs` once matched 4 references where the gate matched
33, and this sentence was the next copy to go wrong. Recorded in the rule itself
so the third copy is not written either.

R12 also still told authors to add a section to `docs/NOW.md`, whose first line
reads FROZEN ARCHIVE -- do not add entries here, frozen in `f5be7dc1c` (#2298)
on 2026-08-21 for exactly the collision reason R12 exists to avoid.
`.claude/skills/spec-first-ternary-nn.md:62` carried the same instruction and is
corrected with it.

The guard is deliberately NOT added, on a measurement rather than on caution.
Every mention of `docs/NOW.md` under `.github/workflows/`, `scripts/` and
`.githooks/` is a comment: zero lines reject an edit, so the freeze is prose
only. But the obvious rule -- fail any diff containing the file -- is too broad:
of the 600 commits since the freeze, 2 touched it and one (`458ec0bd6`) REPAIRS
damaged entries. The banner forbids ADDING entries, not touching the file, and a
guard that blocks a legitimate repair is the shape this repository documents as
one that gets muted. The narrow rule is filed in #3368.

Resealed: the rule text changed, so `LOOP-RULES.sha256` moves with it in this
commit. R6 -- the seal certifies identity, not correctness.

Found by the adversarial sweep for #3355. These two are the MIRROR of that
class: the truth is machine-readable and the prose is the stale transcription.

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

github-actions Bot commented Sep 6, 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 6, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-09-06 06:52:20 UTC

Summary

Status Count
Total Open PRs 16
PRs with Failing Checks 10
PRs with All Checks Green 6
READY 4
FAILING 10
PENDING 0
NO CHECKS YET 0

These columns do not partition: 4 + 10 + 0 + 0 = 14, and there are 16 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=23f03e8a97d5 != 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 6, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-09-06 07:07:47 UTC

Summary

Status Count
Total Open PRs 16
PRs with Failing Checks 10
PRs with All Checks Green 6
READY 4
FAILING 10
PENDING 0
NO CHECKS YET 0

These columns do not partition: 4 + 10 + 0 + 0 = 14, and there are 16 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=23f03e8a97d5 != 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 6, 2026

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 4d2f936 into master Sep 6, 2026
28 checks passed
@gHashTag
gHashTag deleted the s2-r12 branch September 6, 2026 07:14
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