add ohm/0071/SESSION-0071.0-TRANSCRIPT-2026-06-04T05-24--2026-06-04T06-31.md + replace placeholder/variant SESSION-0071.0-TRANSCRIPT-2026-06-04T05-24--2026-06-04T06-15.md

ohm/0071/SESSION-0071.0-TRANSCRIPT-2026-06-04T05-24--2026-06-04T06-31.md

@@ -2,7 +2,7 @@
 
 > App: ohm
 > Start: 2026-06-04T05-24 (PST)
-> End: 2026-06-04T06-15 (PST)
+> End: 2026-06-04T06-31 (PST)
 > Type: coding
 > Mode: autonomous (yolo, default)
 
@@ -78,15 +78,29 @@ now-unblocked frontier).
    OHM cutover milestone) + CLAUDE.md stub committed/pushed.
 6. **Designed the next slice:** authored + merged (PR #13) the **M3-backend
    Plan B** design spec (`docs/superpowers/specs/2026-06-04-m3-backend-planb-design.md`).
-7. **Stopped before** hand-rolling the 12-table PK-rebuild migration —
-   delicate (migration runner can't toggle `PRAGMA foreign_keys` mid-txn; needs
-   an isolated migration test), best executed fresh from its design doc.
+7. **Then (after the Stop hook + "keep going") shipped rfc-app v0.36.0 — §22
+   M3-backend Plan B (1/2):** the slug-keyed **PK/UNIQUE rebuilds** that
+   activate project #2 (migration `028`, 13 tables incl. composite FKs to
+   `cached_rfcs(project_id, slug)`), a migration-runner `-- migrate:no-foreign-keys`
+   capability (the runner couldn't toggle `PRAGMA foreign_keys` mid-txn — added
+   it, with `foreign_key_check` after), and `ON CONFLICT` target updates so the
+   app's upserts match the new composite indexes. `foreign_key_check` caught a
+   3rd FK-referencing table I'd missed (`rfc_invitations`); the full suite
+   caught the `ON CONFLICT` coupling (81→0 failures after the fixes). **442
+   backend tests green; two-project same-slug coexistence proven.** No behavior
+   change. PR #14 merged, tagged, mirrored. Design §2 marked shipped. Split off
+   per-project *serving* (Plan B 2/2) for migration hygiene.
 
 ## Cut state
 
-- **rfc-app `main` = v0.35.0** (origin + benstull), tag pushed. M3-frontend
-  shipped + tested (438 backend, 11 Vitest, clean build). PR #12 merged.
-- **rfc-app M3-backend Plan B design** merged (PR #13).
+- **rfc-app `main` = v0.36.0** (origin + benstull), tags v0.35.0 + v0.36.0
+  pushed. **Two releases shipped this session:**
+  - v0.35.0 — M3-frontend (routing/branding/directory/308s). PR #12. 438
+    backend + 11 Vitest, clean build.
+  - v0.36.0 — M3-backend Plan B (1/2): slug-keyed PK rebuilds (migration 028)
+    + runner FK-off capability + ON CONFLICT updates. PR #14. 442 backend
+    (incl. 4 new migration tests). No behavior change.
+- **rfc-app M3-backend Plan B design** merged (PR #13), §2 marked shipped.
 - **ohm-rfc `main`**: ROADMAP Phase G + CLAUDE.md stub pushed. Pin **unchanged
   at 0.31.5** (OHM not deployed on the multi-project stack — see below).
 - No open PRs; both repos in sync with origin.
@@ -116,7 +130,7 @@ now-unblocked frontier).
 ## Next-session prompt
 
 ```
-/executing-plans Execute M3-backend Plan B per rfc-app/docs/superpowers/specs/2026-06-04-m3-backend-planb-design.md — make a 2nd project's corpus serve+render. First task: seed a Tier-1 registry repo + projects.yaml and set REGISTRY_REPO in testing/.env.tier1 (unblocks M3-frontend + Plan B e2e). Then: default-project-id re-stamp (§22.13 step 1) + the 12-table slug-keyed PK-rebuild migration (migration 026 header — isolated migration test, two-project same-slug coexistence; note the runner can't toggle PRAGMA foreign_keys mid-txn) + per-project RFC serving (path-scoped endpoints, per-project cache/bot/webhook dispatch, scoped frontend calls, guard removal). Ship rfc-app v0.36.0. Read memory multi-project-program.md + ohm-rfc ROADMAP Phase G first. Do NOT do the OHM live cutover without operator go-ahead.
+/executing-plans Execute M3-backend Plan B (2/2) per rfc-app/docs/superpowers/specs/2026-06-04-m3-backend-planb-design.md §1 + §3–§5 (§2 PK rebuilds already shipped v0.36.0). Make a 2nd project's corpus actually serve+render. First task: seed a Tier-1 registry repo + projects.yaml and set REGISTRY_REPO in testing/.env.tier1 (unblocks M3-frontend + Plan B Playwright e2e). Then: default-project-id re-stamp (§22.13 step 1, via the reconciler) + per-project RFC serving (path-scoped /api/projects/{pid}/rfcs… endpoints, per-project cache/bot/webhook dispatch over each content_repo, scoped frontend api calls, REMOVE the M3-frontend NotServedPlaceholder guard). Ship rfc-app v0.37.0. Read memory multi-project-program.md + ohm-rfc ROADMAP Phase G first. Do NOT do the OHM live cutover without operator go-ahead.
 ```
 
 ## Operator plate (needs you)