Rendered from docs/process/obligations/0240-five-run-tooling-gaps-from-run-20261012-2342-filed-together.md in the Headwater
corpus. Every document on this half of the site is typed by the taxonomy
the descriptor names: corpus.json.
Project process. These notes record how Headwater itself is built and run. You do not need them to use Headwater. Back to the specification
Five run-tooling gaps from run 20261012-2342, filed together
Context
hw-run-policy sends a finding about the build order, its tooling or the CI of this repository to this shelf. Run 20261012-2342 wrote these as intake lines from the work on #1490, #1315, #1433 and #1561. The product owner ruled each one RECORD, four at the fifth-merge pass and one at the final pass, both on 2026-10-13. Each item was checked on 56febd34. The product owner read the anchors.code_path.scope list in .headwater/overlay.yml, the schedule and the readme-apt job of .github/workflows/install-routes.yml, the judge function of tools/repo/release-guide-fixtures.sh, the advisory text of .claude/hooks/write.sh, and the mergeable wait in .claude/agents/hw-verify.md.
Obligation
.github/workflows/install-routes.yml(#1490) is a second workflow outsideanchors.code_path.scope, which namestools/**andsite/**and no path under.github/. HW-OBL-0227 records the gap withreadme-apt.ymlas its example. This is one more instance, and the remedy there covers it.tools/repo/readme-install-block.shandtools/repo/install-route-issue.shsit insidetools/**, and no document underdocs/or.headwater/names either. The maintainer of #1490 asks whether a process decision is owed for the rule that one scheduled workflow runs every README route and opens one bug issue.- The
judgefunction oftools/repo/release-guide-fixtures.shlets mutants J1, J6 and J7 survive, and it acceptssha256:zzas a digest (the #1315 verifier, report 3). At9arm withsha256:zzthat expects "carries no verified_revision" holds J7. - For an edit through a symbolic link inside the root, the
advisorytext of.claude/hooks/write.shsays a document "declares that it governs" the link path, though the edge names the file that the link reaches.headwater routenames the real path. #1648 replaces the shell hooks, so it is the natural change to carry the fix. - The mergeable wait in
.claude/agents/hw-verify.mdrunsgh pr view <N>with no--repo. From an agent worktree the call fails with "Could not resolve to a PullRequest", and the!= UNKNOWNtest then passes on the error text (round 2 of the verify of PR #1741).hw-run-policylistsgh issue viewandgh pr editas calls that fail this way and does not listgh pr view.
Discharge
Each item discharges alone. The first does when HW-OBL-0227 discharges. The second does when a document governs the two scripts, or a process decision states the rule they implement. The third does when a case kills J1, J6 and J7. The fourth does when the hook, or what replaces it, names the real path. The fifth does when the wait names --repo headwater-ai/headwater and refuses a wait on an error. The record discharges when every item has.