docs(app): R3 gate results, fix wave run, deploy order, trial steps

- CHANGELOG: the six shell failures split into the four Target crashed
  of BLK-015 and the two A0 lookup timeouts (counted as BLK-015, not A/B
  proven); pgTAP 014 / 021 not proven by a run without M9; the intro
  names the R3 entry's branch
- owner trial 4.15: steps strictly in order (step 5 shows what two
  sheets prove, the move back to the top is step 9's last action), how
  to open the working copy, the trimmed text, no Claude sentence, the
  re-save sentence removed
- deploy order (database first, then the application) and its
  fail-closed consequence in the SQL checkpoint and SUPABASE.md
- design review, code review and security gate results, the fix wave
  run, the owner decisions left open; verifier, check:all and the owner
  trial still pending
- TODO: fix wave line, three follow-ups
This commit is contained in:
bchanot committed 2026-11-16 18:11:12 +01:00
1 parent ea5512af02
commit bcdacbbb9a
8 files changed
+125 -34

No files matched your search

+8
View File
@@ -752,6 +752,14 @@ checked. Two anomalies:
`pnpm db:reset && pnpm db:test` on the real stack.
5. `pnpm db:types` and commit `packages/supabase/src/database.types.ts`.
6. Never edit an applied migration. Corrections are new migrations.
7. Deploy order: the database first, then the application, whenever the typed
client starts requiring what a migration adds. M9
(`20261116100000_sheet_admin_last_modified.sql`, V1-2.6 R3) is such a case:
an application at the R3 head against a database without M9 answers
« indisponible » on the admin sheet screens and on the editor's admin reads
(fail closed, by the client's check of `last_modified_at`); an older
application against a migrated database is unaffected (it ignores the key).
Details: `V1-2-6_R3_SQL_CHECKPOINT.md` §8.
Rules enforced by the schema-types test for every future `public` table:
RLS enabled, no `using (true)` / `with check (true)` policy for `anon` or