Skip to content

crons: the queue health report yml -- paid by the compare_gamma_candidates port (Closes #12710) - #12713

Merged
gHashTag merged 1 commit into
masterfrom
perf/queue-health-report-yml
Oct 26, 2026
Merged

gHashTag merged 1 commit into
masterfrom
perf/queue-health-report-yml

Conversation

@gHashTag

Copy link
Copy Markdown
Collaborator

Lands the workflow yml for the card already on master (#12694), paid per the shrink-only law: the same diff ports scripts/compare_gamma_candidates.py -- a broken one-shot printer (SyntaxError at its line 59, measured with py_compile; unreferenced) -- to specs/port/scripts/compare_gamma_candidates.t27, 4/4 tests, 0 vacuous, sealed, and deletes the original. Net foreign: -25.

Also fixes the yml's on: block: the original carried a bare - cron: list, so the hourly schedule never fired (only manual dispatch ran); now schedule + workflow_dispatch, matching the card.

Refs #12694 (the card), #12710 (the yml queue), #12708 (the red sweep this heals a slice of).

…dates port (Closes #12710, Refs #12613 #12694)

The yml for the card already on master (#12694), with its on: block fixed
(the original had a bare - cron: list -- the hourly schedule never
fired), plus the port of scripts/compare_gamma_candidates.py (broken
one-shot printer, SyntaxError at line 59, unreferenced) to
specs/port/scripts/compare_gamma_candidates.t27 -- 4/4 tests, sealed.
The deletion pays the yml's foreign lines: net -25.
@gHashTag gHashTag added the owner-approved-foreign Owner-approved exception to the only-t27 rule: hand-written foreign code allowed in this PR label Oct 26, 2026
@gHashTag
gHashTag enabled auto-merge (squash) October 26, 2026 17:49
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-26 17:54:37 UTC

Summary

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

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=67adcf31aff7 != 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 81c99fc into master Oct 26, 2026
28 of 40 checks passed
gHashTag added a commit that referenced this pull request Oct 27, 2026
…ssification home (Closes #12820)

THE NUMBER THAT MOVED: workflow files read 69 -> 71. pr-queue-drain
(#12604) and queue-health-report (#12713) landed after the 2026-10-25
snapshot and rode in unclassified -- gate-topology failed at 26 unread
over the 24 ceiling and cli-tri at the unblessed census.

- specs/claw/gates.t27 is now the ONE home of the classification:
  COUNT 71, the two new rows (both reporting), and a REASONS/REASON_LENS
  table aligned with NAMES -- an empty reason marks a merge-critical
  workflow. Census ratchet 64/3/2 -> 64/3/4; loop bounds and the
  aligned-row pins move with the tables; EVENTS re-measured from the
  live on: blocks (four stale rows corrected: release, needs-boundary,
  cli-tri, auto-merge-ready-prs).
- check_pr_branch_filters.py SHRANK by 72 foreign lines: the hardcoded
  MERGE_CRITICAL/NOT_MERGE_CRITICAL dicts are gone; it reads the spec's
  tables and refuses on misalignment. The judgment lives in .t27.
- census re-blessed (tri census pin --bless): fetches/quiet/shell.

Verified: check_pr_branch_filters CLEAN + --self-test ok; t27c
test-report gates.t27 25/25 (0 vacuous); tri census pin --gate exit 0.
gHashTag added a commit that referenced this pull request Oct 27, 2026
…ssification home (Closes #12820)

THE NUMBER THAT MOVED: workflow files read 69 -> 71. pr-queue-drain
(#12604) and queue-health-report (#12713) landed after the 2026-10-25
snapshot and rode in unclassified -- gate-topology failed at 26 unread
over the 24 ceiling and cli-tri at the unblessed census.

- specs/claw/gates.t27 is now the ONE home of the classification:
  COUNT 71, the two new rows (both reporting), and a REASONS/REASON_LENS
  table aligned with NAMES -- an empty reason marks a merge-critical
  workflow. Census ratchet 64/3/2 -> 64/3/4; loop bounds and the
  aligned-row pins move with the tables; EVENTS re-measured from the
  live on: blocks (four stale rows corrected: release, needs-boundary,
  cli-tri, auto-merge-ready-prs).
- check_pr_branch_filters.py SHRANK by 72 foreign lines: the hardcoded
  MERGE_CRITICAL/NOT_MERGE_CRITICAL dicts are gone; it reads the spec's
  tables and refuses on misalignment. The judgment lives in .t27.
- census re-blessed (tri census pin --bless): fetches/quiet/shell.

Verified: check_pr_branch_filters CLEAN + --self-test ok; t27c
test-report gates.t27 25/25 (0 vacuous); tri census pin --gate exit 0.
gHashTag added a commit that referenced this pull request Oct 27, 2026
…ssification home (Closes #12820)

THE NUMBER THAT MOVED: workflow files read 69 -> 71. pr-queue-drain
(#12604) and queue-health-report (#12713) landed after the 2026-10-25
snapshot and rode in unclassified -- gate-topology failed at 26 unread
over the 24 ceiling and cli-tri at the unblessed census.

- specs/claw/gates.t27 is now the ONE home of the classification:
  COUNT 71, the two new rows (both reporting), and a REASONS/REASON_LENS
  table aligned with NAMES -- an empty reason marks a merge-critical
  workflow. Census ratchet 64/3/2 -> 64/3/4; loop bounds and the
  aligned-row pins move with the tables; EVENTS re-measured from the
  live on: blocks (four stale rows corrected: release, needs-boundary,
  cli-tri, auto-merge-ready-prs).
- check_pr_branch_filters.py SHRANK by 72 foreign lines: the hardcoded
  MERGE_CRITICAL/NOT_MERGE_CRITICAL dicts are gone; it reads the spec's
  tables and refuses on misalignment. The judgment lives in .t27.
- census re-blessed (tri census pin --bless): fetches/quiet/shell.

Verified: check_pr_branch_filters CLEAN + --self-test ok; t27c
test-report gates.t27 25/25 (0 vacuous); tri census pin --gate exit 0.
gHashTag added a commit that referenced this pull request Oct 27, 2026
…ssification home (Closes #12820) (#12821)

THE NUMBER THAT MOVED: workflow files read 69 -> 71. pr-queue-drain
(#12604) and queue-health-report (#12713) landed after the 2026-10-25
snapshot and rode in unclassified -- gate-topology failed at 26 unread
over the 24 ceiling and cli-tri at the unblessed census.

- specs/claw/gates.t27 is now the ONE home of the classification:
  COUNT 71, the two new rows (both reporting), and a REASONS/REASON_LENS
  table aligned with NAMES -- an empty reason marks a merge-critical
  workflow. Census ratchet 64/3/2 -> 64/3/4; loop bounds and the
  aligned-row pins move with the tables; EVENTS re-measured from the
  live on: blocks (four stale rows corrected: release, needs-boundary,
  cli-tri, auto-merge-ready-prs).
- check_pr_branch_filters.py SHRANK by 72 foreign lines: the hardcoded
  MERGE_CRITICAL/NOT_MERGE_CRITICAL dicts are gone; it reads the spec's
  tables and refuses on misalignment. The judgment lives in .t27.
- census re-blessed (tri census pin --bless): fetches/quiet/shell.

Verified: check_pr_branch_filters CLEAN + --self-test ok; t27c
test-report gates.t27 25/25 (0 vacuous); tri census pin --gate exit 0.
gHashTag added a commit that referenced this pull request Oct 27, 2026
…ssification home (Closes #12820)

THE NUMBER THAT MOVED: workflow files read 69 -> 71. pr-queue-drain
(#12604) and queue-health-report (#12713) landed after the 2026-10-25
snapshot and rode in unclassified -- gate-topology failed at 26 unread
over the 24 ceiling and cli-tri at the unblessed census.

- specs/claw/gates.t27 is now the ONE home of the classification:
  COUNT 71, the two new rows (both reporting), and a REASONS/REASON_LENS
  table aligned with NAMES -- an empty reason marks a merge-critical
  workflow. Census ratchet 64/3/2 -> 64/3/4; loop bounds and the
  aligned-row pins move with the tables; EVENTS re-measured from the
  live on: blocks (four stale rows corrected: release, needs-boundary,
  cli-tri, auto-merge-ready-prs).
- check_pr_branch_filters.py SHRANK by 72 foreign lines: the hardcoded
  MERGE_CRITICAL/NOT_MERGE_CRITICAL dicts are gone; it reads the spec's
  tables and refuses on misalignment. The judgment lives in .t27.
- census re-blessed (tri census pin --bless): fetches/quiet/shell.

Verified: check_pr_branch_filters CLEAN + --self-test ok; t27c
test-report gates.t27 25/25 (0 vacuous); tri census pin --gate exit 0.
gHashTag added a commit that referenced this pull request Oct 27, 2026
…ssification home (Closes #12820)

THE NUMBER THAT MOVED: workflow files read 69 -> 71. pr-queue-drain
(#12604) and queue-health-report (#12713) landed after the 2026-10-25
snapshot and rode in unclassified -- gate-topology failed at 26 unread
over the 24 ceiling and cli-tri at the unblessed census.

- specs/claw/gates.t27 is now the ONE home of the classification:
  COUNT 71, the two new rows (both reporting), and a REASONS/REASON_LENS
  table aligned with NAMES -- an empty reason marks a merge-critical
  workflow. Census ratchet 64/3/2 -> 64/3/4; loop bounds and the
  aligned-row pins move with the tables; EVENTS re-measured from the
  live on: blocks (four stale rows corrected: release, needs-boundary,
  cli-tri, auto-merge-ready-prs).
- check_pr_branch_filters.py SHRANK by 72 foreign lines: the hardcoded
  MERGE_CRITICAL/NOT_MERGE_CRITICAL dicts are gone; it reads the spec's
  tables and refuses on misalignment. The judgment lives in .t27.
- census re-blessed (tri census pin --bless): fetches/quiet/shell.

Verified: check_pr_branch_filters CLEAN + --self-test ok; t27c
test-report gates.t27 25/25 (0 vacuous); tri census pin --gate exit 0.
gHashTag added a commit that referenced this pull request Oct 27, 2026
…ssification home (Closes #12820)

THE NUMBER THAT MOVED: workflow files read 69 -> 71. pr-queue-drain
(#12604) and queue-health-report (#12713) landed after the 2026-10-25
snapshot and rode in unclassified -- gate-topology failed at 26 unread
over the 24 ceiling and cli-tri at the unblessed census.

- specs/claw/gates.t27 is now the ONE home of the classification:
  COUNT 71, the two new rows (both reporting), and a REASONS/REASON_LENS
  table aligned with NAMES -- an empty reason marks a merge-critical
  workflow. Census ratchet 64/3/2 -> 64/3/4; loop bounds and the
  aligned-row pins move with the tables; EVENTS re-measured from the
  live on: blocks (four stale rows corrected: release, needs-boundary,
  cli-tri, auto-merge-ready-prs).
- check_pr_branch_filters.py SHRANK by 72 foreign lines: the hardcoded
  MERGE_CRITICAL/NOT_MERGE_CRITICAL dicts are gone; it reads the spec's
  tables and refuses on misalignment. The judgment lives in .t27.
- census re-blessed (tri census pin --bless): fetches/quiet/shell.

Verified: check_pr_branch_filters CLEAN + --self-test ok; t27c
test-report gates.t27 25/25 (0 vacuous); tri census pin --gate exit 0.
gHashTag added a commit that referenced this pull request Oct 27, 2026
…ssification home (Closes #12820)

THE NUMBER THAT MOVED: workflow files read 69 -> 71. pr-queue-drain
(#12604) and queue-health-report (#12713) landed after the 2026-10-25
snapshot and rode in unclassified -- gate-topology failed at 26 unread
over the 24 ceiling and cli-tri at the unblessed census.

- specs/claw/gates.t27 is now the ONE home of the classification:
  COUNT 71, the two new rows (both reporting), and a REASONS/REASON_LENS
  table aligned with NAMES -- an empty reason marks a merge-critical
  workflow. Census ratchet 64/3/2 -> 64/3/4; loop bounds and the
  aligned-row pins move with the tables; EVENTS re-measured from the
  live on: blocks (four stale rows corrected: release, needs-boundary,
  cli-tri, auto-merge-ready-prs).
- check_pr_branch_filters.py SHRANK by 72 foreign lines: the hardcoded
  MERGE_CRITICAL/NOT_MERGE_CRITICAL dicts are gone; it reads the spec's
  tables and refuses on misalignment. The judgment lives in .t27.
- census re-blessed (tri census pin --bless): fetches/quiet/shell.

Verified: check_pr_branch_filters CLEAN + --self-test ok; t27c
test-report gates.t27 25/25 (0 vacuous); tri census pin --gate exit 0.
gHashTag added a commit that referenced this pull request Oct 28, 2026
policy: the payment law for landing a workflow -- port-or-delete, entry first (Refs #12606, #12713)
dmitrii-f-t27 pushed a commit to dmitrii-f-t27/t27 that referenced this pull request Oct 30, 2026
…ity-S-AI-DNA#12727)

Which numbers moved and why, per the gate's own instruction:
- shell.txt: workflow files 69->71 (pr-queue-drain.yml landed via
  Trinity-S-AI-DNA#12694 and queue-health-report.yml via Trinity-S-AI-DNA#12713, neither carried a
  re-bless), jobs 99->101 and run: steps 340->342 (the two new files'
  jobs and steps).
- quiet.txt: files read 49->50 and named-a-path 273->276 (same two
  files), workflow files 69->71 as above.
- fetches.txt: re-recorded by `tri census pin --bless` for the same
  tree.
`tri census pin --gate` exits 0 on this tree. The guard/autofix/
rebase ymls of Trinity-S-AI-DNA#12710 will move the count again (72, 73) and each
carries its own bless in the same commit.
dmitrii-f-t27 pushed a commit to dmitrii-f-t27/t27 that referenced this pull request Oct 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

owner-approved-foreign Owner-approved exception to the only-t27 rule: hand-written foreign code allowed in this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant