Skip to content

Re-bless the census this loop moved, and stop quoting a home path - #4304

Merged
gHashTag merged 1 commit into
masterfrom
fix/master-is-red
Sep 20, 2026
Merged

gHashTag merged 1 commit into
masterfrom
fix/master-is-red

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

Closes #4303

Two of the three red checks on master are this loop's own.

check why fixed here
cli-tri six workflows added since the census pin (#4277, #4279, #4281, #4283, #4291, #4300) yes -- re-blessed, with every moved number named in the commit
scan feed_defects.py quotes /Users/<name>/t27/... inside the comment warning against it yes
coverage 544 stale seals; zero successful runs in the last 60 on master, reaching back past 2026-09-18 no -- re-sealing 544 specs is a decision about the ledger, not a repair

Also: that path gate failed in every git worktree on a path no commit
contains. It excludes the .git directory; a worktree's .git is a one-line
file holding gitdir: /Users/.... The reviewer measures in a detached worktree
and every bee works in one, so this was a false failure in exactly the place
the swarm runs.

Measured after the change, locally, with a t27c and tri built from master:

$ tri census pin --gate        # rc=0, "the 3 pinned readings are unchanged"
$ python3 tools/check_devhome_paths.py
OK: 30 file(s), 38 occurrence(s), all pinned in tools/devhome_baseline.txt
$ python3 tools/check_devhome_paths.py --self-check
OK: every control behaves as stated.

🤖 Generated with Claude Code

… path

Three checks are red on master. Two are this loop's.

CENSUS. tools/census/quiet.txt pinned `workflow files read 51`; the tree holds
57. The six added since the pin are #4277, #4279, #4281, #4283, #4291 and
#4300, all merged by this loop, and cli-tri has been red since 2026-09-17.
What moved, explicitly: quiet 51 -> 57 workflow files and 123 -> 135 "named a
path but not quiet"; shell 51 -> 57 files, 72 -> 78 jobs, 249 -> 267 run-steps,
228 -> 246 steps the runner runs with `bash -eo pipefail`. The gates did not
change; the population grew.

HOME PATH. feed_defects.py carries a comment explaining that an absolute
`/Users/<name>/t27/target/release/t27c` once went into 137 open issues -- and
spells it out to say so, which is what the scan catches. It now reads
`.../t27/target/release/t27c`, same meaning, no home directory.

WORKTREES. That gate also failed in every worktree on a path no commit
contains: it excludes the `.git` DIRECTORY, and a worktree's `.git` is a FILE
holding `gitdir: /Users/...`. `--exclude=.git` joins `--exclude-dir=.git`. The
reviewer measures in a detached worktree and every bee works in one.

NOT FIXED HERE: `coverage` reports 544 stale seals and has no successful run in
its last 60 on master, reaching back past 2026-09-18. Re-sealing 544 specs
records what the compiler now produces -- a decision about the ledger, not a
repair.

Closes #4303

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

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@gHashTag
gHashTag enabled auto-merge (squash) September 20, 2026 09:52
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-09-20 09:52:31 UTC

Summary

Status Count
Total Open PRs 20
PRs with Failing Checks 17
PRs with All Checks Green 3
READY 2
FAILING 17
PENDING 0
NO CHECKS YET 0

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

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=403499176a5d != 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 ab98c2e into master Sep 20, 2026
32 of 34 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.

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

2 participants