docs(supabase): DEV procedure with read-only checks and sandbox restore
Preflight of DEV recorded; backup adds row fingerprints and Storage bytes; restore check runs on the isolated stack; post-migration SQL, test effects, failure and restore effects; browser acceptance aligned on the owner brief.
This commit is contained in:
1 parent
9f585e9185
commit
e3b841799a
2 files changed
+299
-105
No files matched your search
@@ -1555,7 +1555,7 @@ validates after V1-1.1 and after the first UI step; nothing merges into
|
||||
| V1-1.3 | UI foundations: Playwright Chromium and axe (D14), `Dialog` containment and restore (D13). Built (§11.6), validated 2026-10-26 |
|
||||
| V1-1.4 | Animals and relations data: M3 with the species rows, RPCs, history rules, D9a proof. Written and tested on the isolated stack (§8.3), validated 2026-10-26; not applied to DEV |
|
||||
| V1-1.5 | Clients UI: routes, forms, list and search, archive, navigation entry. Built and tested on the isolated stack (§11.7), validated 2026-10-26 |
|
||||
| V1-1.6 | Animals and relations UI, navigation (D11: drawer only), documents, closure inventory (§15). Built and tested on the isolated stack (§11.8), awaiting the owner's checkpoint; D12 not in its brief; the owner's check over the LAN needs M1 to M3 on DEV |
|
||||
| V1-1.6 | Animals and relations UI, navigation (D11: drawer only), documents, closure inventory (§15). Built and tested on the isolated stack (§11.8), validated 2026-10-26; D12 not in its brief; the owner's check over the LAN needs M1 to M3 on DEV |
|
||||
|
||||
Recommended first step: V1-1.1. It is SQL only, has no visible choice, and
|
||||
every later step depends on its helpers.
|
||||
@@ -1591,7 +1591,9 @@ Owner brief §21. Status words: **done** (built, tested on the isolated stack),
|
||||
**debt** (non-blocking, documented, kept in the product follow-up),
|
||||
**deferred** (left out on purpose, with who decided), **blocking** (before a
|
||||
merge into `develop`), **DEV** (to verify once M1 to M3 are applied, SUPABASE.md
|
||||
§3.3). Nothing below is verified on DEV: no V1-1 migration is applied there.
|
||||
§3.3). Nothing below is verified on DEV: no V1-1 migration is applied there. The
|
||||
read-only preflight of DEV (2026-10-26) found M1 to M3 pending and nothing
|
||||
else, and none of their objects present (SUPABASE.md §3.3).
|
||||
|
||||
| Area | Item | Status | Proof or reason |
|
||||
|---|---|---|---|
|
||||
@@ -1617,6 +1619,6 @@ merge into `develop`), **DEV** (to verify once M1 to M3 are applied, SUPABASE.md
|
||||
| Debt | no separate message for a relation voided elsewhere (seen as `conflict`) | debt | §11.8 |
|
||||
| Debt | pre-existing axe exceptions of RR-7 (language switcher, top bar account link, dashboard `dl`) | debt | scoped to their element and route; no V1-1 page relies on them for its own elements |
|
||||
| Debt | GoTrue admin with the service key, `service_role` on the species table, no read limit of its own, partial Unicode folding | debt | release track RR-3, RR-4 (§14) |
|
||||
| DEV | M1 to M3 applied, workspaces and ten active species counted, pgTAP, types | DEV | SUPABASE.md §3.3, owner action |
|
||||
| DEV | M1 to M3 applied, workspaces and ten active species counted, pgTAP, types | DEV | SUPABASE.md §3.3, owner action; read-only preflight conform 2026-10-26, backup, restore check and migration not run |
|
||||
| DEV | browser acceptance on a phone and a computer over the LAN | DEV | SUPABASE.md §3.3 « Browser acceptance on DEV »; not done |
|
||||
| Merge | owner's go after the V1-1.6 checkpoint and the DEV acceptance | blocking | §14; nothing merges into `develop` without it |
|
||||
Reference in new issue
Block a user