Skip to content

feat(t27b): tri t27b ready -- the steward's merge gate decided in steward.t27 - #6246

Merged
gHashTag merged 3 commits into
masterfrom
claude/t27b-ready
Oct 4, 2026
Merged

gHashTag merged 3 commits into
masterfrom
claude/t27b-ready

Conversation

@gHashTag

@gHashTag gHashTag commented Oct 4, 2026

Copy link
Copy Markdown
Owner

Closes #6244
Refs #6063 #6198

Stacked on #6242 (its commit is the first one here). Merge #6242 first, and this diff then shrinks to slice 6.

What

  • specs/tri/t27b/steward.t27 gains:
    • check-state codes
    • check_effect(state, master, required)
    • effect_fold
    • pr_ready(open, mergeable, base_master, required, other), which returns READY, WAIT, RED, CONFLICT, RETARGET, BLOCKED or CLOSED
  • tri t27b ready [N ...] [--json] prints one line per PR: the verdict and the checks that decided it. Exit 0 only when every listed PR is READY. It never merges.
  • Rule Q16 is now tested: a non-required check blocks only if it is red here and its newest verdict on master is success. Required checks are validate, check-linked-issue and parse-ratchet, plus loop-tools-tracked once it reports.

Found while building it

Master's newest runs are often cancelled by the next push. I first counted "cancelled" as master's result. That made five checks that are red on #6206 and green on master look red on master too, so #6206 read READY. fold_master now skips cancelled, skipped and neutral runs, and reads 12 master commits back. After the fix, #6206 is BLOCKED by scan (job secret-scan) FAILURE while master's scan is SUCCESS. Spot-checked by hand with gh pr view.

Evidence

🤖 Generated with Claude Code

…ward.t27

check_effect / effect_fold / pr_ready in steward.t27 (80 tests, both
compilers). `tri t27b ready [N ...]` prints READY / WAIT / RED / CONFLICT /
RETARGET / BLOCKED / CLOSED per PR with the deciding checks; Q16 (a red
non-required check blocks only if green on master) is now a tested rule.
Master's verdict per check skips cancelled/skipped/neutral runs: counting
cancelled made red-here/green-on-master checks look red on master.

Closes #6244
Refs #6063 #6198

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 19:30:56 UTC

Summary

Status Count
Total Open PRs 45
PRs with Failing Checks 30
PRs with All Checks Green 15
READY 12
FAILING 30
PENDING 0
NO CHECKS YET 0

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

Seal Status

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

…going (Closes #6244)

A non-required check red on the PR was judged against master's last
verdict even when a newer master run of it was still in progress, so a
stale SUCCESS blocked #6249. fold_master now reports PENDING for a run
still going on a newer commit, and check_effect (steward.t27) makes such
a red check WAIT. 81 tests on t27b and the t27c lab; gen-c byte-equal.

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 20:21:12 UTC

Summary

Status Count
Total Open PRs 47
PRs with Failing Checks 33
PRs with All Checks Green 14
READY 12
FAILING 33
PENDING 0
NO CHECKS YET 0

These columns do not partition: 12 + 33 + 0 + 0 = 45, and there are 47 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=8597b6ded596 != 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 Oct 4, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-04 20:21:29 UTC

Summary

Status Count
Total Open PRs 47
PRs with Failing Checks 33
PRs with All Checks Green 14
READY 12
FAILING 33
PENDING 0
NO CHECKS YET 0

These columns do not partition: 12 + 33 + 0 + 0 = 45, and there are 47 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=8597b6ded596 != 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 b2f9dc5 into master Oct 4, 2026
25 of 27 checks passed
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.

tri t27b ready: the steward's merge gate decided in steward.t27

1 participant