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
@
|
||
|---|---|---|
| .. | ||
| claudebox-design.md | ||
| claudebox-recipe.md | ||
| issue-12-implementation-plan.md | ||