docs(app): R3 sheet list documents as built, M9 applied

V1-2-6_U1_CORRECTIONS §R3 as built (A7 split superseded by D2, exact
results, deviations), the SQL checkpoint applied with corrections F2 to
F4, the owner's answers and the date limits F7, M9 in §12.3, db:sandbox
migrate, the sheet list spec and its named failures, class C rows, the
design deviations, CLAUDE.md and CHANGELOG. Gates pending.
This commit is contained in:
bchanot committed 2026-11-16 17:47:49 +01:00
1 parent 73ed37546f
commit a86020d6e3
9 files changed
+235 -12

No files matched your search

+1 -1
View File
@@ -806,7 +806,7 @@ Docker.
| `pnpm db:sandbox verify-e2e` | V1-2.3: a gateway (`nginx:1.31-alpine`, sandbox network only, no host port) and the real verification worker `faunosteo_worker:dev run --jobs sheet-verify` against the sandbox, then `packages/supabase/tests/sandbox/sheet-verification.sandbox.ts`; both containers removed at the end, the service key passed through a 600 file deleted at start |
| `pnpm db:sandbox avatar-e2e` | V1-2.3: the same gateway, published on `127.0.0.1:57800` only and routing `/auth/v1/` too, the real worker `faunosteo_worker:dev run` (default mode: avatars and sweep, 5 s sweep, no quarantine grace, 512 MiB as the compose `worker`) against the sandbox, then `packages/supabase/tests/e2e/avatar-flow.e2e.ts` through that port; the suite's psql calls go to the sandbox database container, which it requires by name; its two accounts are made per run with random passwords and deleted after; both containers removed at the end |
| `pnpm db:sandbox trial` / `trial-account <email>` / `trial-grant <email> <kind>` | V1-2.6 owner trial (`docs/development/V1-2-6_OWNER_TRIAL.md`): the app on `http://$FAUNOSTEO_TRIAL_HOST:5193` (default the LAN address of this machine, `127.0.0.1` = host-only; loopback or private IPv4 of an interface only, Host header allowlisted) behind a trial gateway on `127.0.0.1:57801` (refuses to start when `faunosteo_dbsandbox_trial_gateway` exists), a confirmed account (hidden password prompt), a catalogue right (email and kind checked, passed as psql variables; editor and publisher also get the admin role) |
| `pnpm db:sandbox migrate` | forward only on the running sandbox: `supabase migration up --db-url` applies the branch's pending migrations, nothing else (no reset, no seed, no container recreated, data kept); prints the last applied version before and after, a second run applies nothing |
| `pnpm db:sandbox migrate` | forward only on the running sandbox: `supabase migration up --db-url` applies the branch's pending migrations, nothing else (no reset, no seed, no container recreated, data kept); prints the last applied version before and after, a second run applies nothing. Takes no argument and refuses when the sandbox is not up. The CLI refuses a pending file older than the last applied one; a migration edited after it was applied is neither detected nor applied again, so a migration is frozen from its first application to any stack and a change ships as a new file. Added in V1-2.6 R3 (owner decision D3, 2026-11-16) as additions only to `scripts/db-sandbox.sh` (`scripts/db-trial-check.sh` checks that), so it is documented here and in the script's comment, not in the help header the script prints; first run 2026-11-16, M9, `20261103100000` → `20261116100000` |
| `pnpm db:sandbox sql` / `down` | psql as postgres on stdin / remove the stack |
Every CLI call passes `--db-url` with `sslmode=disable` (the sandbox has no