From 9186816bed143bbef5643b6b6f1986f9f309b87e Mon Sep 17 00:00:00 2001 From: Dmitrii Vasilev Date: Sun, 18 Oct 2026 15:04:59 +0700 Subject: [PATCH] census: re-bless gates quiet and gates shell after the claw-t27f job (Closes #10303) Master's cli-tri step "No census moved without saying so" has been red since 834f25839, because #10283 moved two pinned censuses without re-blessing them. That was my miss. Re-blessed with `tri census pin --bless` on the Railway lab, from master dc4ea956b. What moved, and why: - gates shell, jobs 88 -> 89: #10283 added the claw-t27f job to gate-topology.yml. - gates shell, run steps 314 -> 316 (runner-named 293 -> 295): the claw-t27f job's steps, as of #10299, which made the check-run POST plus one PATCH per further annotation batch. - gates quiet, quiet-shape steps 32 -> 33, file-existence guards 9 -> 10, variable-in-path 6 -> 7, named-but-not-quiet 200 -> 204: the same job's steps. No other workflow changed since the last bless, so every moved line comes from gate-topology.yml. No other workflow changed between the last bless (290ff17df, #10172) and dc4ea956b. `tri census pin --gate` exits 0 after the re-bless. Co-Authored-By: Claude Opus 5.5 --- tools/census/quiet.txt | 8 ++++---- tools/census/shell.txt | 6 +++--- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/tools/census/quiet.txt b/tools/census/quiet.txt index c75a742499..aa3f93081b 100644 --- a/tools/census/quiet.txt +++ b/tools/census/quiet.txt @@ -1,20 +1,20 @@ GATE STEPS WHOSE PASS SURVIVES THE SUBJECT GOING MISSING workflow files read 67 - steps in a quiet shape 32 - named a path but not quiet 200 (--excluded prints them) + steps in a quiet shape 33 + named a path but not quiet 204 (--excluded prints them) by shape: failure branch passes 14 `… 2>/dev/null … || echo PASSED` a count that reads zero 9 `$(… 2>/dev/null | wc -l)` - gated on the file existing 9 often legitimate, reported apart + gated on the file existing 10 often legitimate, reported apart an if that falls through 0 an if whose then-branch exits and whose fi is followed by a pass and what can be said about the subject WITHOUT running the workflow: a tracked path, ABSENT 0 <- guarding nothing right now a tracked path, present 12 the run builds it 7 absence from a checkout says nothing - a variable in the path 6 depends on the run + a variable in the path 7 depends on the run no path ANYWHERE in the step 7 cannot be checked -- NOT the same as absent No quiet gate names a tracked path that is missing today. That is a diff --git a/tools/census/shell.txt b/tools/census/shell.txt index 5fb8b5e402..5f856d6146 100644 --- a/tools/census/shell.txt +++ b/tools/census/shell.txt @@ -1,11 +1,11 @@ WHICH INTERPRETER EACH GATE STEP IS HANDED TO, AND WHO SAYS SO workflow files read 67 - jobs 88 - run: steps 314 + jobs 89 + run: steps 316 who names the shell: - the runner does 293 no container, so bash -eo pipefail + the runner does 295 no container, so bash -eo pipefail a `shell:` key does 6 NOBODY 15 a container and no `shell:` key