docs(docs): V1-1.2 clients as built, budget windows and lock order
Contract §8.2 (as built, divergent replay, fold, measured search, residual hint), §9 helpers and lock order, §9.4 request_conflict, §10 UTC budget windows. SUPABASE.md §3.4 and the DEV procedure for M1 and M2 pending together (rehearsed). TEST_STRATEGY counts.
This commit is contained in:
1 parent
4adbfcb608
commit
f8bd1b6861
3 files changed
+102
-27
No files matched your search
@@ -16,6 +16,11 @@ V1-1.1 (2026-10-25): supabase vitest 44 (config test added), 12 pgTAP files
|
||||
(`012_workspaces.sql`, 85 checks; 531 checks in all), also run on an isolated
|
||||
real stack because the DEV stack stays untouched until the owner applies M1
|
||||
(`V1-1_OWNERS_ANIMALS.md` §8.1).
|
||||
V1-1.2 (2026-10-25): supabase vitest 53 (field-limits parity test added), 13
|
||||
pgTAP files (`013_clients.sql`, 130 checks; 661 in all); the isolated stack is
|
||||
a project tool (`pnpm db:sandbox`, SUPABASE.md §5.1) with its own suite under
|
||||
`packages/supabase/tests/sandbox` (28 real-stack checks: HTTP per role,
|
||||
concurrency, budget races, 20 000-client search timing).
|
||||
|
||||
## 1. Layers
|
||||
|
||||
|
||||
Reference in new issue
Block a user