Three ordered stages, one per issue: a live audit of the boundary and the
four load-bearing Incus behaviors the analysis could only assert from a
code reading, the isolation hardening on the current tool (whose test
then guards the rename), and the box/templates rework. Re-pinned to main
@ 0982a2d after PR #13 merged — resolve_box() is now the single seam for
stage 2's dual-tag matching.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
