Twinned from https://github.com/cfsh/ninefold/issues/606 by tools/beads/import_github.py's reconcile pass.
Suggestions from ninefold-reviewer's review of #604. All three are below the gate floor — #604 is CONVERGED — and none of them blocks anything.
empty_reason's combined sentence overclaims about pausedtools/pr/rebuild_f5.py — empty_reason, the new third branch:
``` nothing open that changes the playtest build, 1 branch held, 2 branches docs-only ```
A paused branch is held by intention; nothing has asked whether it changes the playtest build, and it very well might. The leading clause asserts a fact about it that the tool does not have. The paused-only wording is careful for exactly this reason — #512 F4 pinned the distinction, #519 F1 pinned the sentence, and #525 is still open on the same class of claim in WRAP_UP.
Cheap fix, and it keeps the two categories honest:
``` no unpaused PRs that change the playtest build, 1 branch held, 2 branches docs-only ```
The all-paused and all-docs sentences are unaffected.
DOCS_ONLY_SUFFIXES' comment points at a file that does not existtools/pr/rebuild_f5.py, above DOCS_ONLY_SUFFIXES:
> tools/PackPreset.cs says the same thing from the shipping side — it excludes *.md from every pack.
There is no tools/PackPreset.cs. The substance is right, but the shipping-side exclusion is DEV_EXTS = (".md", ".py", ".sh", ".mid") at tools/gen_packs.py:40 ("dev debris that lives inside asset trees but isn't runtime content"), asserted by tools/tests/PackPresetTests.cs:55. Worth correcting on the same argument #604's own notes/history.md entry makes about #568-vs-#549: a wrong pointer is cheap to inherit and expensive to chase.
#604 covers *.md and design_docs/** and deliberately stops there ("keep this list SHORT and provably inert"), which is the right default — a false positive costs a PR missing from a build Aedan is giving feedback against.
Recording the residual, because the live queue is the counter-example: #603 is tools/office/spawn_dev.py — a dev-session spawner that no playtest can observe — and it still merges into f5/integration and can still stop the rebuild. Same for a tools/pr/poll.py or a .claude/commands/ change. tools/ is genuinely not inert as a whole (run_tests.sh is executed by verify, probes run at merge time), so this would need a narrower predicate than a directory, not a wider one. Not obviously worth doing; filed so the half-answer is written down rather than assumed complete.
None.
No comments.