Master is red on three checks, two of them from this loop's own merges #4303

What is wrong

Three checks are red on master, and two of them are red because of changes
this loop merged.

1. cli-tri / "No census moved without saying so". The pinned census reads
workflow files read 51; the tree holds 57. Six workflows were added since the
pin -- spec-parse-ratchet (#4277), auto-merge-ready-prs (#4279),
queen-feed-empty-bodies (#4281), pusher (#4283), dupe-ratchet (#4291),
queen-doctor (#4300) -- and none re-blessed. The gate exists to make exactly
this visible, and it has been red since 2026-09-17.

2. scan / "Block hardcoded developer home paths". tools/queen/feed_defects.py
and its coordination entry both quote an absolute /Users/<name>/t27/... path.
They quote it inside the comment warning against it -- the comment explaining
that this mistake put an unrunnable path into 137 open issues.

The same gate also fails in every git WORKTREE for a path no commit contains:
it excludes the .git DIRECTORY, and a worktree's .git is a one-line FILE
holding gitdir: /Users/.... A worktree is where the swarm's reviewer measures
and where every bee works.

3. coverage / "Every seal still describes its spec" reports 544 stale
seals. NOT from this loop: the last 60 runs of that workflow on master hold
zero successes, the failures reaching back past 2026-09-18. It is named here so
the next reader does not attribute it to the two above, and it is not fixed
here -- re-sealing 544 specs records what the compiler now produces, which is a
decision about the seal ledger and not a repair.

Acceptance criteria

• 1. grep -c 'workflow files read 57' tools/census/quiet.txt prints 1 (today: 0)
• 2. grep -c 'Users/playom' tools/queen/feed_defects.py prints 0 (today: 1)
• 3. grep -c 'exclude=.git' tools/check_devhome_paths.py prints at least 2 (today: 0)

Boundary

tools/check_devhome_paths.py