add ohm/0071/SESSION-0071.0-TRANSCRIPT-2026-06-04T05-24--2026-06-04T13-33.md + replace placeholder/variant SESSION-0071.0-TRANSCRIPT-2026-06-04T05-24--2026-06-04T08-19.md

ohm/0071/SESSION-0071.0-TRANSCRIPT-2026-06-04T05-24--2026-06-04T13-33.md

@@ -2,7 +2,7 @@
 
 > App: ohm
 > Start: 2026-06-04T05-24 (PST)
-> End: 2026-06-04T08-19 (PST)
+> End: 2026-06-04T13-33 (PST)
 > Outcome: ✅ GOAL COMPLETE — multi-project live; ecomm migrated; planner retired.
 > Type: coding
 > Mode: autonomous (yolo, default)
@@ -180,14 +180,30 @@ re-authed gcloud + ADC), and the goal was carried to done end-to-end:
   snapshotted, **`flotilla-core deploy ohm-rfc-app` → all 9 phases green
   (deploys.id=5)**. Migrations 026–028 + the startup re-stamp ran.
 - **verified live:** `GET /api/deployment` → "Wiggleverse RFC", projects
-  `[ecomm(bdd), ohm(document)]`; `/p/ohm/` 34 entries; **`/p/ecomm/` 67
+  `[ecomm(bdd), ohm(document)]`; `/p/ohm/` 34 entries; **`/p/ecomm/` 1,238
-  entries**.
+  scenario entries** (see the granularity fix below).
 - **planner retired** — `planner-vm` snapshotted (`planner-vm-pre-retirement`)
   + **stopped (TERMINATED)**; repo **archived** + deprecation banner → `/p/ecomm/`.
 
 **All three goal steps complete and in production.** Six rfc-app versions this
 session: v0.34.0 (pre-existing) → **v0.35.0–v0.39.0** shipped.
 
+### Post-cutover fix — ecomm BDD granularity (operator-flagged)
+
+Operator noted the ecomm project "doesn't seem to have many BDDs." Root cause:
+the first ingest was at *feature* granularity (67 entries, each bundling its
+scenarios in the body) — but the planner's unit (and the expectation) is the
+individual scenario. **Re-ingested at scenario granularity: 1,238 entries**, one
+per Given/When/Then scenario, keyed on its `DD.FF.NNNN` id, human title,
+`[domain, feature]` tags — parsed with the planner's own
+`tools/gherkin_corpus.py` (handles all 4 Gherkin shapes; my first hand-rolled
+regex only caught the 421 fenced ones). Replaced the 67 in `ecomm-content`,
+pushed; on the VM cleared the ecomm cache rows (no `sqlite3` CLI → used
+`python3` + stdlib `sqlite3`) and restarted so the startup sweep re-mirrored.
+Verified live: **`/p/ecomm/` = 1,238** scenarios with correct titles + bodies.
+(Brief gotcha: a `set -e` SSH script aborted after the missing-`sqlite3`
+discovery and left the service stopped for ~1 min → restored; health 200.)
+
 ## Open follow-ups (non-blocking polish for a future session)
 
 - Shared-edge `/<token>/` Cloudflare route still points at the stopped