update ecomm/0024/SESSION-0024.0-TRANSCRIPT-2026-06-10T22-20--INPROGRESS.md

ecomm/0024/SESSION-0024.0-TRANSCRIPT-2026-06-10T22-20--INPROGRESS.md

@@ -17,8 +17,40 @@
 
 ```
 
+## Plan
+
+> Anchor: design /Users/benstull/git/wiggleverse.org/wiggleverse/wiggleverse-ecomm-content/specs/SD-0001-mvp-sign-up-and-single-storefront.md (R2a — ELIGIBLE)
+
+Implement SLICE-3 (storefront) per SD-0001 v0.3.0 §7.2:
+
+1. `storefronts` domain — `create_storefront` + membership, INV-4 guard,
+   concurrent-create refusal.
+2. Wire into the BFF `_storefront_for` seam (replace the `null` stub).
+3. Create-storefront + Admin-shell screens (PUC-4/5/6/7/8) per the Claude
+   Design export at `wiggleverse-ecomm-content/ui/designs/ecomm-login-and-create-storefront-designs/`.
+4. Complete entry routing (signed-in users route by storefront presence).
+5. Whole-flow INV-1 bootstrap test.
+6. Update SLICE-1/2 UI (Landing, Sign-in) to match the design export.
+
+> Implementation plan: `docs/superpowers/plans/2026-06-10-slice-3-storefront.md`
+> (branch `slice-3-storefront`; inline execution via superpowers:executing-plans).
+
 ## Deferred decisions
 
 _Autonomous-mode low-confidence calls the driver made and would have
 liked operator input on. Appended as the session runs; surfaced at
 finalize. Empty if none._
+
+- **E2E browser tests deferred** per SD-0001 §6.8 ("component/E2E browser tests
+  deferred until there is UI beyond forms") — SLICE-3's UI is still forms + text;
+  same stance as SLICE-1/2. The §9 pipeline policy is noted, not yet automated.
+- **Design-fidelity divergence (honest-UI):** the design export's dead `#` links
+  ("How it works", "Open Core", footer Privacy/Terms) are not shipped — INV-9's
+  spirit (nothing links nowhere). Footer keeps the identity line only.
+- **Welcome-banner placement:** the hf-signin design shows the PUC-3 honest-copy
+  banner on the code step; the SPA routes immediately after verify, so the banner
+  renders on the destination screen (create-storefront/admin) instead.
+- **INV-4 concurrency mechanism:** per-account `pg_advisory_xact_lock(account_id)`
+  serializes guard+insert (spec asks only that "two concurrent creates cannot both
+  pass the guard"; the advisory lock is the lightest way without a schema UNIQUE,
+  which INV-4 forbids).