| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
TML-2503: close out the Supabase integration — promote the decision log, delete the project workspaces (#990) ## What this is The Supabase integration umbrella close-out (TML-2503): the durable knowledge the project produced moves to its permanent home, and the transient project workspaces — `projects/supabase-integration/` and `projects/extension-supabase/` — are deleted. This is the deletion both dirs deferred to (extension-supabase Slice E deferred its own dir here; the umbrella README's §Close-out prescribed constituent dirs delete alongside the umbrella). ## Project DoD — verified Every constituent shipped and merged; the launch acceptance executed: | Item | Evidence | |---|---| | Slices B/C (RLS via authoring, roles first-class) | #956, #957, #950 | | Slice D (`db.supabase` secondary root) | #845 | | Slice F (complete introspected contract) | #960 | | Slice G (extension-aware `contract infer`) | #919 | | Slice E (docs, acceptance harness, close-out) | #985 | | User-facing skill (`prisma-next-supabase`) | #987 | | Launch-blocking acceptance run | executed 2026-07-15 against a real Supabase project (session pooler), 3/3 green: anon read, authenticated update-own + withCheck, service-role read, expired-JWT rejection | | Deferred items | all recorded with durable homes (package README "Known gaps"; the promoted doc's Deferred directions / Follow-on work sections) | | Final retro | lessons landed continuously in durable memory + ADRs during delivery; no unlanded lesson at close | ## Migration (1 long-lived file, rewritten at migration) `projects/supabase-integration/decisions.md` → **`docs/architecture docs/Supabase Integration.md`** (git mv, history preserved), per the umbrella README's own close-out instruction. The rewrite: a design-history header pointing at the living surfaces (package README, `examples/supabase`, the user skill, ADRs 224/226/230/234); links into the deleted workspaces stripped to plain text; the content-addressed-names draft link re-pointed at ADR 234; "Decisions still open" closed out as the design-hole resolution record; and two appended sections fold in the workspace's still-relevant remainder — **Deferred directions** (from `deferred.md` + the DX roadmap) and **Follow-on work** (FK1 discrete FK/index entities superseding ADR 161, FK2 auth/storage split, the `auth.uid()` default stretch, TML-2492, the post-launch perf/bundle deferrals). Everything else classified transient per the close-out defaults: the umbrella README (tracker), `overview.md` (its user-facing narrative is superseded by the skill + READMEs; its composition story by the ADRs and subsystem docs), the `example/` design artefact (deletion explicitly prescribed), and the extension-supabase spec/plan/slices/trace. ## Reference strip (4 files re-pointed) - `packages/3-extensions/supabase/README.md` — 4 links → the promoted doc. - `examples/supabase/README.md` — 1 link → the promoted doc. - `projects/native-postgres-enums/.../infer-native-enum-adoption/spec.md` — plan link → merged #960. - `projects/psl-ambient-declarations/spec.md` — OC1/OC4/deferred links → the promoted doc (that project actively consumes the decision log; the promoted doc keeps it grounded). Post-strip scan is clean — the only residual mentions are the scope notes in the new upgrade-instruction files, which describe the deletion itself. The README touches trip the upgrade-coverage gate, so this PR also opens the `0.15-to-0.16` transition dirs in both upgrade skills with `changes: []` + incidental scope notes. ## Verified `lint:docs`, `lint:skills`, `check:upgrade-coverage --mode pr`, `check:release-notes --mode pr` all green; markdown-only diff otherwise. With this merged, the Supabase integration is fully closed: shipped, verified against real Supabase, documented for users, and its process scaffolding retired. 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Added ADR 237 detailing how Supabase-internal data is accessed via a `service_role`-only secondary query surface. * Updated Supabase extension documentation references to reflect the new secondary-root architecture guidance. * Clarified documentation scope for the 0.15 → 0.16 upgrade (no application-facing changes), including upgrade metadata and related READMEs. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> | 2 个月前 |