Changes touching this path
- Evidence (#359): a three-lane wave lands with zero orchestrator surgery
The terminal ticket of map #354. Prove the destination live: a real wave of
lanes over one shared store reviews and reconciles with no respawn+copy, no
hand-merge, no folklore. A hermetic, re-runnable PowerShell script drives the
wave through real `loot` verbs; its captured run is committed beside it.
- docs/evidence/scripts/wave-proof-lanes-demo.ps1 + runs/wave-proof-lanes-demo.txt
(run 2026-07-21, 23 checks, all pass). Seven acts on three lanes forked from
one base: (1) three reviews open as pure projections, three review/<lane> refs,
main unmoved; (2) an interleaved out-of-wave land moves main mid-wave; (3) a
stale-anchor review refreshes byte-identically (op=up-to-date, same sha, WIP
intact) — the REFUSE_REVIEW_STALE_ANCHOR respawn family is structurally gone;
(4) the #418 seal-WIP guard: bare `loot ferry` and no-arg `loot adopt` both
refuse to seal described WIP, and --seal-wip seals on purpose + prints the
recovery round; (5) the colliding lane catches up over the moved tip, bounces
on the shared path, and reconciles IN-LANE with the resolution folded into its
subject (#337); (6) a disjoint lane catches up with no merge cost.
- The harbor land-bounce and the #349 "already-projected -> proceed" path live
inside `loot-first land` (shells to gh), so they cannot run hermetically. ACT 7
runs `cargo test -p loot-first --lib` live (69 passed) — harbor_guard_*,
already_projected_line_ahead_of_origin_reads_as_landable, the gate suite — as
the cited proof of the GitHub-facing layer. docs/evidence/wave-proof-lanes.md
is candid about what is proven live vs cited.
- docs/agents/concurrent.md gains the explicit "Running a wave" framing (#358's
"Nothing new": N lanes fire land, queue on the harbor, carry handles the moved
tip — no wave verb, no orchestrator), pointing at the evidence run.
The script gates on the release build's exit code, not just the binary's
presence, so a failed rebuild can't run a stale binary and claim the guard.
ac4b6814 · dbf3dbe6…
Renames are not followed. loot's tree maps a path to an address, so a rename is a delete and an add. This list is the history of the name, not of the bytes.