Skip to content

docs(loop): LOOP-RULES says what master does after the NOW gate (Closes #6002) - #6004

Merged
gHashTag merged 1 commit into
masterfrom
docs/loop-rules-required-checks
Oct 4, 2026
Merged

gHashTag merged 1 commit into
masterfrom
docs/loop-rules-required-checks

Conversation

@gHashTag

@gHashTag gHashTag commented Oct 4, 2026

Copy link
Copy Markdown
Owner

Closes #6002. Refs #5935.

docs/loop/LOOP-RULES.md still described the NOW gate the owner removed on 2026-10-04 (PR #5951). Two files change: the rule text and its seal.

rule was now
R12 entry add a docs/now/ entry dated inside the gate's window no entry required; points at docs/now/README.md for an optional one
R12 archive "docs/NOW.md is now ENFORCED" (Archive-Repair) still frozen; the exception points at CONTRIBUTING.md; no workflow enforces it since #5951
R12 checks "Four required checks: check, validate, check-now-freshness, check-linked-issue" the ruleset query, plus its answer on 2026-10-04: validate, check-linked-issue, parse-ratchet
R10 now-sync-gate.yml listed; "Until that change is merged ..." the filter removal merged in bba0644 (#2169); now-sync-gate.yml is gone; the stacked-PR disclosure stays as a standing rule

Seal

docs/loop/LOOP-RULES.sha256: 6d68cc15... -> cc856a5c..., resealed for these four passages only (the commit message says so, as loop_rules.py asks).

Checked in a scratch copy of the two files plus master's scripts/tri_loop/loop_rules.py:

  • new text against new seal: OK -- the rule text is byte-identical to the sealed text., exit 0
  • negative control, master's text against the new seal: MISMATCH, exit 1
  • the query in the new text, run as written: validate, check-linked-issue, parse-ratchet
  • added lines are ASCII (the two pre-existing section signs at lines 139 and 141 are untouched)

No code reads the removed wording: git grep 'Four required checks' finds only this file, and rule_observance.py reads PR bodies, not the rules' text.

🤖 Generated with Claude Code

#6002)

The rules still told a loop tick to add a docs/now/ entry inside the NOW
gate's window and named four required checks, two of which belonged to
workflows #5951 deleted. A tick that follows them does work nothing asks
for and reads a wrong list of blocking checks.

- R12: no docs/now/ entry is required (owner decision 2026-10-04, #5935);
  points at docs/now/README.md for where an optional one goes.
- R12: docs/NOW.md stays frozen; the Archive-Repair exception points at
  CONTRIBUTING.md and says no workflow enforces it since #5951.
- R12: the required-check list is replaced by the ruleset query plus a
  dated answer (validate, check-linked-issue, parse-ratchet, 2026-10-04).
  The old line missed parse-ratchet and named `check` and
  `check-now-freshness`, the jobs of the two deleted workflows.
- R10: the branch-filter removal merged in bba0644 (#2169); the
  "until that change is merged" clause is now a standing rule for any
  gate that did not run on a stacked PR. now-sync-gate.yml is gone.

Resealed LOOP-RULES.sha256 6d68cc15... -> cc856a5c... because of the four
passages above and nothing else; `python3 scripts/tri_loop/loop_rules.py`
prints OK on this tree and MISMATCH on master's text against the new seal.

Refs #5935

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

github-actions Bot commented Oct 4, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-04 10:34:48 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 42
PRs with All Checks Green 8
READY 2
FAILING 42
PENDING 0
NO CHECKS YET 0

These columns do not partition: 2 + 42 + 0 + 0 = 44, and there are 50 open PRs. A PR is being counted twice or not at all.

Seal Status

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

This was referenced Oct 4, 2026
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.

LOOP-RULES.md names removed NOW checks as required

1 participant