🜄Headwater

How it works Compare Proof Tutorial

Process obligation records

The CI job named \"(advisory)\" carries every blocking shell suite in the repository
The skills fixture suite passes on an empty input set, and always fails in a clone that has not built the engine
Four inline gates in the workflow decide an exit status and no suite provokes one
The value rule writes adopter on every self-audit record and most of them wait on a build
A bare none footprint is claimed as a literal path, so two disjoint issues collide
Three small run-tooling gaps from run 20260922-1121, filed together
hw-run-policy names a worktree-add workaround that Write/Edit refuses under this harness
The plan usage of one issue is known only as the average of its run
A build-order dispatch passes no isolation, so a stage can inherit the parent worktree as its working directory
No fixture holds the symlink case of new-worktree.sh, and a bare name of two dots leaves a branch behind
Two hand-remedy lines for hw-cargo in hw-run-policy may not earn their cost on every dispatch
ci-done.sh reads a cancelled run of another branch as a red result on a main merge commit
CI builds no MkDocs site, so a generated page under docs/ is never checked against a strict build before merge
Two merge hooks of this repository print a resolve flag that the verb refuses
The site-review marker lives in the common directory of a clone, so one worktree's unreviewed merge blocks the push of every worktree
No disk floor is stated for a build-order run, and nothing prunes the cargo pool
Subagents read skills from the shared checkout, and a worktree-isolated integrator cannot fast-forward it after a merge
Thirteen run-tooling gaps from run 20260928-1109, filed together
Eight run-tooling gaps from run 20260929-1205, filed together
Seven run-tooling gaps from run 20260929-2201, filed together
Five run-tooling gaps from run 20261001-1107, filed together

Rendered from docs/process/obligations/0210-no-fixture-holds-the-symlink-case-of-new-worktree-sh-and-a-bare-name-of-two-dots-leaves-a-branch-behind.md in the Headwater corpus. Every document on this half of the site is typed by the taxonomy the descriptor names: corpus.json.

No fixture holds the symlink case of new-worktree.sh, and a bare name of two dots leaves a branch behind

Context

The verifier of PR #1061 (#848) in run 20260924-0411 found two gaps in contributor tooling. The product owner ruled both Record.

Obligation

The symlink case has no fixture. The script resolves the main checkout with pwd -P. If that call drops to a plain pwd, the suite stays green.

A name of two dots leaves a branch. --name .. passes the bare-name check. Git then fails to add the worktree, and the branch the call created stays behind.

Discharge

The first gap discharges when a fixture runs the script through a symlinked path and fails with plain pwd. The second discharges when --name .. is refused before any branch exists, and a case holds that.

Keys	Action
`?`	Open this help
`n`	Next page
`p`	Previous page
`s`	Search