Merge chore/sandbox-rule-line into develop

This commit is contained in:
bchanot committed 2026-11-14 19:20:54 +01:00
commit 06ee6eb797
3 files changed
+27

No files matched your search

+3
View File
@@ -459,3 +459,6 @@ R5.4: `draft/{labels,changelog,review_report,drawing,overlay,app_review,svg_comp
## 2026-11-02
- bugfix/avatar-e2e-sandbox-only: develop e2e:avatar → sandbox only (3a4614b, e8da0d9, d3dfd03). Proofs a-j strace with forged JWTs, 2 × 5/5, DEV untouched. Verifier CONFORME 10/10, security PASS ×2. BLK-013, LRN-095, TODO RR-11. Owner authorised merge into develop; worktree kept.
## 2026-11-14
- chore/sandbox-rule-line: LRN-080 promotion made true, .claude/rules/database.md gains the db:sandbox line (block F claimed it 2026-11-13 without the line). Security PASS.
+2
View File
@@ -15,6 +15,8 @@ paths: ["supabase/migrations/**", "supabase/tests/**", "packages/supabase/**", "
from public and granted only to the roles that evaluate them.
- A migration is never edited once applied. Each migration ships its pgTAP file with
allowed AND denied cases, and a regenerated `database.types.ts`.
- Every migration step runs first on the throwaway sandbox (`pnpm db:sandbox`,
`scripts/db-sandbox.sh`), never against DEV; changes to DEV stay owner actions (LRN-080).
- The browser holds the anon key only. The `service_role` key value never appears in env.js, .env.example or code;
operator scripts under `packages/*/scripts/` read it from the environment and are never bundled.
- pgTAP files run on PGlite and on the real image: scope counts to fixture ids, pin `collate "C"` on text ordering.
@@ -0,0 +1,22 @@
# CONTRACT — sandbox-rule-line (LRN-080 promotion made true)
- date: 2026-11-14 | flow: hotfix | branch: chore/sandbox-rule-line (off develop)
- status: active
## REQUEST (verbatim — IMMUTABLE)
faunosteo: LRN-080 status (2026-11-13, block F) says "implemented, promoted to rule line .claude/rules/database.md" but that rule file has no sandbox line: the promotion claim is false. Add one bullet to .claude/rules/database.md from LRN-080's own Apply text: every migration step is tried first on the throwaway sandbox (`pnpm db:sandbox`, scripts/db-sandbox.sh), never on DEV; DEV changes stay owner actions. 1 file.
## CLARIFICATIONS
- [gated 2026-11-14] wording = LRN-080 Apply line; no challenge (doc line, no behaviour); placed right after the "A migration is never edited once applied" bullet.
## ACCEPTANCE CRITERIA
1. The rule file carries the sandbox line.
CHECK: grep -c 'db:sandbox' .claude/rules/database.md
EXPECT: 1
EVIDENCE: PENDING
2. Frontmatter unchanged, project rules check green.
CHECK: git diff -U0 .claude/rules/database.md | grep -c '^[-+]paths:'
EXPECT: 0
EVIDENCE: PENDING
## FILE SCOPE
.claude/rules/database.md