define canonical migration deployment paths

This commit is contained in:
makearmy 2026-07-10 20:21:27 -04:00
parent ed1c84eb76
commit 27fd4f4ae3
4 changed files with 238 additions and 21 deletions

View file

@ -239,6 +239,8 @@ Build verification inspects image histories and filesystems for forbidden names
The current `app`, `bgbye`, and `dashboard` directories will be moved only in a dedicated mechanical commit after build-context and path references are covered by tests. Milestone 0 may initially implement the target logical boundaries without a risky all-at-once directory move.
The repository tree above exists at exactly one persistent nonproduction checkout, `/srv/le-payload-dev/lasereverything.net.db`, and at the canonical production root, `/var/www/lasereverything.net.db`. Runtime data is never placed inside either Git checkout unless it is a deliberately versioned non-secret fixture. The complete canonical host directory policy and transitional consolidation are defined in `host-runtime-plan.md`.
## End-to-end test matrix
| Area | Fixture mode | Snapshot/rehearsal mode | Core assertions |