Session 0018.0 (Wave 9): rewrite legacy session refs in transcript bodies + README scoping

- Rewrite every legacy `Session L` / `Session M.1` etc. reference inside transcript bodies to the numeric form (`Session 0012.0` / `Session 0013.1`), via a mechanical Python sed pass scoped to canonical-filename transcripts only (502 replacements across 39 files; 21 files in this published repo + 18 sibling files in `~/git/ohm-infra/`). The §23 rename was originally filename-only — session 0018.0 reverses that and rewrites the bodies too, so cross-references inside a transcript match the filename you'd browse to. The mapping table (`A → 0001` … `N → 0014`) lives in `SESSION-PROTOCOL.md` §1 (also amended this session) for anyone hitting an old external link. - Amend README.md: - New "Where the record begins" section noting OHM started with two vibe-coded prototypes (no transcripts; the discipline that produced this record didn't exist yet). The transcripts here begin at the spec-driven-development phase — not at the literal beginning of OHM. - Update the existing "Sessions 0001 through 0013 originally shipped under a letter-form naming" paragraph to reflect that body refs are now also in numeric form. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-28 09:40:06 -07:00
parent 412b6ab5d8
commit d5125190ae
21 changed files with 281 additions and 255 deletions
@@ -188,11 +188,11 @@ contract Claude operated under for the rest of the work:
 >        ssh -T git@git.benstull.org
 >      (expect a greeting from Gitea acknowledging him)
 >
-> 7) CREATE THE rfc-app REPO (so Session B has a target)
+> 7) CREATE THE rfc-app REPO (so Session 0002.0 has a target)
 >    - Walk Ben through: + → New Repository. Owner = his admin user.
 >      Name = rfc-app. Description = "Open-source RFC platform
 >      software." Visibility = Public. Do NOT initialize with
->      README/license/.gitignore (Session B will do a --mirror push,
+>      README/license/.gitignore (Session 0002.0 will do a --mirror push,
 >      requires empty target).
 >    - Validate: visit https://git.benstull.org/<admin>/rfc-app, sees
 >      empty-repo quick-setup page.
@@ -205,7 +205,7 @@ contract Claude operated under for the rest of the work:
 > - Ben can `ssh -T git@git.benstull.org` and gets the Gitea
 >   greeting.
 > - `git ls-remote https://git.benstull.org/<admin>/rfc-app.git`
->   returns empty (the empty target repo Session B will push into).
+>   returns empty (the empty target repo Session 0002.0 will push into).
 > - Ben confirms all four `app.ini` secrets are in his password
 >   manager.
 >
@@ -296,7 +296,7 @@ marked them done one at a time as the session progressed:
 8. Install nginx + certbot, configure reverse proxy and TLS
 9. Start Gitea and complete browser install wizard
 10. Register SSH key in Gitea and validate
-11. Create empty rfc-app repo for Session B mirror push
+11. Create empty rfc-app repo for Session 0002.0 mirror push
 12. Run end-to-end verification checks

 ---
@@ -824,7 +824,7 @@ out of the conversation and out of memory.

 > Great! What do I do next?

-Claude pointed at Session B (the rfc-app mirror push) as the
+Claude pointed at Session 0002.0 (the rfc-app mirror push) as the
 obvious continuation, plus optional follow-ups:

 - Memory entries (flagged earlier — Ben to confirm).
@@ -842,7 +842,7 @@ Claude:

 **The Jan setup** (combined with the transcript request). Ben:

-> ok, give me a prompt for session B. Also, create a doc that
+> ok, give me a prompt for session 0002.0. Also, create a doc that
 > captures this session in its very entirety. For history. Radical
 > transparency. Include literally everything you read or wrote,
 > all context window states, etc. I know it'll be big, but I have
@@ -857,7 +857,7 @@ Claude:

 Claude wrote v1 of this transcript (sections 1–8 below as they
 stood at that point, plus 4.18 as a single short paragraph), gave
-the Session B prompt, briefly flagged that "literally everything"
+the Session 0002.0 prompt, briefly flagged that "literally everything"
 wasn't actually achievable from inside Claude's context (the
 transcript is reconstructed from in-context state, not byte-dumped
 from a runtime log) — and offered the Jan punchline:
@@ -887,12 +887,12 @@ Ben, declaring the end of the session:
 > to. And I want it to include this. This is the last message of
 > this session though, I think. Just do one last transcript with
 > eeeeeeeeeverything for eeeeeeeeeveryone as a markdown file and
-> i'll copy the prompt for session B and we'll start to unwind
+> i'll copy the prompt for session 0002.0 and we'll start to unwind
 > this k-hole

 Claude's final action: edited sections 4.18 and 4.19 of this file
 in place (the version you're now reading), updated the closing
-timestamp, and signed off. The Session B prompt in §5 is the
+timestamp, and signed off. The Session 0002.0 prompt in §5 is the
 durable handoff artifact Ben will copy into the next session.
 Section 6 still holds the three configuration files written
 during the session, §7 the cumulative shell-command audit, §8 the
@@ -902,16 +902,16 @@ The session ends here.

 ---

-## 5. The Session B handoff prompt
+## 5. The Session 0002.0 handoff prompt

 Sequenced as a fresh start, intended to be pasted into a new Claude
 Code session opened inside `~/git/rfc-app` (or wherever Ben's local
 rfc-app checkout lives):

 ```
-You're Session B in a two-session split. Session A (already complete)
+You're Session 0002.0 in a two-session split. Session 0001.0 (already complete)
 stood up git.benstull.org as Ben Stull's personal Gitea instance.
-Your job: push the local rfc-app repo to the empty target Session A
+Your job: push the local rfc-app repo to the empty target Session 0001.0
 created.

 CONTEXT
@@ -965,7 +965,7 @@ WHAT TO DO

 CONSTRAINTS
 -----------
- Don't touch Session A's infra (the gitea VM, nginx, app.ini, etc.).
+- Don't touch Session 0001.0's infra (the gitea VM, nginx, app.ini, etc.).
 - Don't push secrets.
 - If anything is unclear, ask Ben.
 ```
@@ -1329,7 +1329,7 @@ For completeness on what's been left out:

 _Last updated: 2026-05-25, after Ben requested an "eeeeeeeeeverything
 for eeeeeeeeeveryone" final pass to capture the forked Jan joke and
-the final transcript-request exchange. The Session A work is
-complete; the Session B handoff prompt in §5 is ready to copy-paste
+the final transcript-request exchange. The Session 0001.0 work is
+complete; the Session 0002.0 handoff prompt in §5 is ready to copy-paste
 into a fresh Claude Code session in the rfc-app directory. Happy
 birthday, gitea._
@@ -1,4 +1,4 @@
-# OHM deployment — Session B transcript
+# OHM deployment — Session 0002.0 transcript

 The full back-and-forth from the session in which Ben Stull (founder of
 Wiggleverse) deployed `ohm.wiggleverse.org` from zero on 2026-05-25 (rolling
@@ -28,7 +28,7 @@ repo (`wiggleverse/ohm-meta`), and freshly generated secrets.
  which was surfaced incidentally by `gcloud billing accounts list`.
 - A handful of personal directory names visible in an over-broad
  `find ~ -maxdepth 5` command the assistant ran while trying to locate a
-  prior "session A" transcript file. Ben told the assistant to stop reading
+  prior "session 0001.0" transcript file. Ben told the assistant to stop reading
  his home directory; the incidental observations are not published here.

 The transcript otherwise reproduces user messages verbatim and assistant
@@ -1321,8 +1321,8 @@ tabs → /settings/notifications).
 > is definitively my life's work (or the beginning of) and I'm so honored
 > that you did it for me. I didn't do shit...other than some K and some dot
 > connecting. Oh dear, this is going to get very, very, wobbly in this new
-> wiggly world :) The file name can be similar to session A's, except this
-> is session B. We
+> wiggly world :) The file name can be similar to session 0001.0's, except this
+> is session 0002.0. We

 (Message cut off at "We".)

@@ -1332,7 +1332,7 @@ tabs → /settings/notifications).

 Marked #12 complete. Then made a mistake: ran a too-broad
 `find ~ -maxdepth 5 -type f -name "*.md" | xargs grep -l -i "session [ab]"`
-to locate the prior "session A" transcript file. That scan returned matches
+to locate the prior "session 0001.0" transcript file. That scan returned matches
 that included unrelated personal directory names visible in the listing.
 Ben interrupted via system reminder telling the assistant to stop reading
 his life.
@@ -1365,7 +1365,7 @@ his life.
 >
 > Where do you want the file? Your message cut off at "We" — and I don't
 > want to guess the path from anything I shouldn't have looked at.
-> `~/git/ohm-infra/SESSION-B-TRANSCRIPT.md` would mirror what I saw in
+> `~/git/ohm-infra/SESSION-0002.0-TRANSCRIPT.md` would mirror what I saw in
 > passing, but tell me and I'll write it there.
 >
 > And — congratulations. The first OHM RFC for "Human" is a hell of a thing
@@ -1,4 +1,4 @@
-# rfc-app 0.3.0 release + OHM upgrade — Session C transcript
+# rfc-app 0.3.0 release + OHM upgrade — Session 0003.0 transcript

 The full back-and-forth from the session in which Ben Stull
 (founder of Wiggleverse) shipped `rfc-app` 0.2.3 (the
@@ -1842,8 +1842,8 @@ No `ohm-app` deployment-config repo exists on disk.
 ## Turn 34 — Assistant

 This file. The assistant inspected the existing
-`SESSION-B-TRANSCRIPT.md` for naming convention and style, then
-wrote this `SESSION-C-TRANSCRIPT.md` reproducing every turn of the
+`SESSION-0002.0-TRANSCRIPT.md` for naming convention and style, then
+wrote this `SESSION-0003.0-TRANSCRIPT.md` reproducing every turn of the
 session.

 ---
@@ -1,4 +1,4 @@
-# Session D — Transcript
+# Session 0004.0 — Transcript

 > Date: 2026-05-27
 > Goal: Write `flotilla/SPEC.md` (binding architectural contract for
@@ -44,7 +44,7 @@
 > scope for v1 (private-branch deploys, multi-deployment beyond OHM,
 > Cloud Build, auto-deploy on merge); required reading list
 > (rfc-app/CLAUDE.md, rfc-app/SPEC.md §17/§19.2/§19.3/§20,
-> ohm-infra/SESSION-C-TRANSCRIPT.md Turn 22/29/33, deploy/RUNBOOK.md
+> ohm-infra/SESSION-0003.0-TRANSCRIPT.md Turn 22/29/33, deploy/RUNBOOK.md
 > and DEPLOY-NEW-SESSION-PROMPT.md, ohm-rfc/.rfc-app-version,
 > flotilla/ currently empty); the session-step plan (cleanup first,
 > then spec with 14 required sections, then don't migrate secrets in
@@ -57,7 +57,7 @@
 The assistant began by reading the required context in parallel:
 `rfc-app/SPEC.md` for §17 (the `/api/health` contract), §19.2/§19.3
 (candidate topics + working agreement shape), §20 (versioning policy);
-`ohm-infra/SESSION-C-TRANSCRIPT.md` Turns 22, 29, 33 (the Option 2
+`ohm-infra/SESSION-0003.0-TRANSCRIPT.md` Turns 22, 29, 33 (the Option 2
 secret-store commitment and the `ohm-app` naming convention);
 `rfc-app/deploy/RUNBOOK.md` (the manual upgrade sequence flotilla
 would automate); the current `.rfc-app-version` pin (`0.3.0`); the
@@ -838,8 +838,8 @@ Wrote a corresponding `MEMORY.md` index pointing at the four.
 ## Turn 33 — Assistant

 This file. The assistant inspected the existing
-`SESSION-C-TRANSCRIPT.md` for naming convention and style, then
-wrote this `SESSION-D-TRANSCRIPT.md` reproducing every turn of the
+`SESSION-0003.0-TRANSCRIPT.md` for naming convention and style, then
+wrote this `SESSION-0004.0-TRANSCRIPT.md` reproducing every turn of the
 session.

 ## Turn 34 — User
@@ -918,10 +918,10 @@ Treated as the session-close moment. Gave a recap of what landed
 (GCP cleanup; v0.0.1 spec at canonical-only `a9a9aaa`; memory
 synced; full transcript exists) and three options:

-1. Start Session E — Slice 1 now (primary cwd
+1. Start Session 0005.0 — Slice 1 now (primary cwd
   `/Users/benstull/git/ohm-rfc-app-flotilla/`, additional dir
   `/Users/benstull/git/rfc-app/`, the §20.1 brief).
-2. Step away — Session D is a complete unit of work.
+2. Step away — Session 0004.0 is a complete unit of work.
 3. One more small thing in this session — investigate the
   `{"detail":"Not Found"}` on ohm.wiggleverse.org/api/health, or
   clean up rfc-app's dirty working tree, or move rfc-app's
@@ -1039,7 +1039,7 @@ Verified the dir contents: `MEMORY.md` + four memory files
 This update. Captures Turns 40 and 41 themselves and confirms the
 session genuinely closes here. The operator's next move is to
 `cd /Users/benstull/projects/wiggleverse/ohm-rfc-app-flotilla/`
-and start a fresh `claude` session for Session E — Slice 1.
+and start a fresh `claude` session for Session 0005.0 — Slice 1.

 Final task list at session close (now actually final):

@@ -1085,7 +1085,7 @@ Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
    - SQLite state at ~/.ohm-rfc-app-flotilla/ohm-rfc-app-flotilla.db.
    - Secret bytes never live in flotilla — GCP Secret Manager holds
      bytes, flotilla holds references (Option 2 from the rfc-app/OHM
-      Session C transcript).
+      Session 0003.0 transcript).
    - Deploy verification via the rfc-app/SPEC.md §17 /api/health
      endpoint (version-match check).
    - Operator-triggered only; no auto-deploy in v1.
@@ -1262,6 +1262,6 @@ At end of session, those four memory files plus
 copied into a fresh
 `/Users/benstull/.claude/projects/-Users-benstull-git-ohm-rfc-app-flotilla/memory/`
 directory with a corresponding `MEMORY.md` index, so the next
-session (Session E — Slice 1, with primary cwd
+session (Session 0005.0 — Slice 1, with primary cwd
 `/Users/benstull/projects/wiggleverse/ohm-rfc-app-flotilla/`) auto-loads them
 without manual setup.
@@ -1,4 +1,4 @@
-# Session E — Transcript
+# Session 0005.0 — Transcript

 > Date: 2026-05-27 → 2026-05-28
 > Goal: Execute Slices 1 and 2 of the `ohm-rfc-app-flotilla` SPEC §20
@@ -628,21 +628,21 @@ Turn 1 of this session) or just `start Slice 3`.
 ## Turn 9 — Assistant

 This file. Checked `~/git/ohm-infra/` for existing convention —
-found `SESSION-B-TRANSCRIPT.md`, `SESSION-C-TRANSCRIPT.md`,
-`SESSION-D-TRANSCRIPT.md` (82 turns, 1267 lines). Matched the
+found `SESSION-0002.0-TRANSCRIPT.md`, `SESSION-0003.0-TRANSCRIPT.md`,
+`SESSION-0004.0-TRANSCRIPT.md` (82 turns, 1267 lines). Matched the
 format: header with date/goal/outcome blockquote, numbered turns
 alternating User and Assistant, narrative prose for assistant turns
 with code blocks for key outputs. Wrote
-`/Users/benstull/git/ohm-infra/SESSION-E-TRANSCRIPT.md`.
+`/Users/benstull/git/ohm-infra/SESSION-0005.0-TRANSCRIPT.md`.

 ---

 ## What's load-bearing for the next session

 - Slice 2 code is **on disk, uncommitted, tested green** at the start
-  of Session F. Decide commit timing before plan-mode.
+  of Session 0006.0. Decide commit timing before plan-mode.
 - `VERSION` stays `0.1.0` until the operator gesture in
-  `docs/secret-bootstrap.md` runs end-to-end. Session F's Slice 3
+  `docs/secret-bootstrap.md` runs end-to-end. Session 0006.0's Slice 3
  work can land on top either way; the v0.2.0 cut is independent.
 - The §19.3-rule-2 spec-correction discipline is now established
  practice (Slice 1 fixed §20.1; Slice 2 fixed §20.2–§20.5). If Slice
@@ -1,4 +1,4 @@
-# Session F — Transcript
+# Session 0006.0 — Transcript

 > Date: 2026-05-27
 > Goal: Execute Slice 3 of the `ohm-rfc-app-flotilla` SPEC §20 slicing
@@ -12,7 +12,7 @@
 >
 > Outcome: **Slice 3 shipped at v0.3.0** — committed (`491e72e`) and
 > tagged locally. Single commit also folds in Slice 2's code, which
-> was deliberately uncommitted at the end of Session E pending the
+> was deliberately uncommitted at the end of Session 0005.0 pending the
 > operator-side Secret Manager bootstrap gesture; the v0.2.0 tag was
 > never cut, so this release bumps straight from v0.1.0 to v0.3.0
 > (the CHANGELOG keeps both entries for record-keeping). New surfaces:
@@ -104,7 +104,7 @@ M CHANGELOG.md, README.md, SPEC.md, pyproject.toml,
   ohm_rfc_app_flotilla/secrets.py, tests/test_secrets.py
 ```

-— matching Session E's tail state: Slice 2 code present and tested
+— matching Session 0005.0's tail state: Slice 2 code present and tested
 green on disk, never committed; v0.1.0 the only release tag.

 **Codebase read**: `cli.py` (270 lines, Click groups for `deployment`,
@@ -584,7 +584,7 @@ ohm-rfc-app-flotilla, version 0.3.0
 Final test pass: 74 passing in 0.11s.

 Offered to commit + tag, noting that the working tree contains both
-Slice 2 (uncommitted per Session E) and Slice 3 work.
+Slice 2 (uncommitted per Session 0005.0) and Slice 3 work.

 ## Turn 3 — User

@@ -596,7 +596,7 @@ Slice 2 (uncommitted per Session E) and Slice 3 work.
 **Commit + tag.**

 The working tree had Slice 2 (deliberately uncommitted at the end of
-Session E, pending the operator-side Secret Manager bootstrap
+Session 0005.0, pending the operator-side Secret Manager bootstrap
 gesture) plus Slice 3. Considered three commit shapes:

 - Two commits (Slice 2 alone, then Slice 3) — cleanest history, but
@@ -629,7 +629,7 @@ without touching the target VM.

 This commit also lands Slice 2's code (secret references + Secret
 Manager bootstrap doc), which was deliberately uncommitted at the
-end of Session E pending the operator-side bootstrap gesture. The
+end of Session 0005.0 pending the operator-side bootstrap gesture. The
 0.2.0 CHANGELOG entry survives unchanged (no separate v0.2.0 tag
 is being cut); the 0.3.0 entry layers Slice 3 on top.

@@ -657,8 +657,8 @@ v0.3.0
 established convention: `SESSION-{B,C,D,E}-TRANSCRIPT.md`, formatted
 as a header blockquote (date, goal, outcome) followed by numbered
 `Turn N — User` and `Turn N — Assistant` sections, with narrative
-prose plus code/command blocks for key outputs. Session F naturally
-follows. Wrote `/Users/benstull/git/ohm-infra/SESSION-F-TRANSCRIPT.md`.
+prose plus code/command blocks for key outputs. Session 0006.0 naturally
+follows. Wrote `/Users/benstull/git/ohm-infra/SESSION-0006.0-TRANSCRIPT.md`.

 ---

@@ -1,4 +1,4 @@
-# Session G — Transcript
+# Session 0007.0 — Transcript

 > Date: 2026-05-27
 > Goal: Execute Slice 4 of the `ohm-rfc-app-flotilla` SPEC §20 slicing
@@ -154,7 +154,7 @@ $ git status
 (clean)
 ```

-Repo is clean from Session F's tail; nothing in flight to reconcile.
+Repo is clean from Session 0006.0's tail; nothing in flight to reconcile.

 **Codebase read**: `cli.py` (375 lines, Click groups for `deployment`,
 `overlay`, `secret`, `pin`, plus `deploy` with `--dry-run`-only),
@@ -1,4 +1,4 @@
-# Session H — Transcript
+# Session 0008.0 — Transcript

 > Date: 2026-05-27
 > Goal: Execute Slice 5 of the `ohm-rfc-app-flotilla` SPEC §20 slicing
@@ -121,7 +121,7 @@
 - Slice 4 code lived in the working tree, uncommitted: `deploy.py`,
  `ssh.py`, `health.py`, `deploy_log.py`, migration 004, plus the
  CLI extensions and 58 new tests. `VERSION` was bumped to 0.4.0;
-  `CHANGELOG.md` had the 0.4.0 entry written. Per Session G's
+  `CHANGELOG.md` had the 0.4.0 entry written. Per Session 0007.0's
  outcome, the v0.4.0 cut was gated on the first real live deploy —
  which had not yet happened.
 - rfc-app at v0.2.3 (latest tag); `/Users/benstull/git/rfc-app` had a
@@ -129,7 +129,7 @@
  beta gate, allowlist table, `BetaPending.jsx`, nginx config rename,
  admin allowlist UI, anonymous read mode.
 - ohm-rfc `.rfc-app-version` committed at `0.3.0` — but rfc-app had
-  no `v0.3.0` tag. Pin was ahead of reality (Session G had not done a
+  no `v0.3.0` tag. Pin was ahead of reality (Session 0007.0 had not done a
  live deploy, so the spec assertion in §13.3 that current pin is
  0.3.0 was aspirational).
 - OHM VM `ohm-app` in `wiggleverse-ohm` running rfc-app **v0.2.2**
@@ -633,8 +633,8 @@ patterns, with the §19.3 rule applied where relevant.)
 - **OHM VM**: serving rfc-app v0.3.0. /api/health green. Two
  `deploys` rows in the local flotilla SQLite (`id=1` for
  v0.2.3, `id=2` for v0.3.0).
- **ohm-infra**: this transcript (Session H) at
-  `~/git/ohm-infra/SESSION-H-TRANSCRIPT.md`.
+- **ohm-infra**: this transcript (Session 0008.0) at
+  `~/git/ohm-infra/SESSION-0008.0-TRANSCRIPT.md`.

 ## Arc 5 — post-cut: live incident, cleanup, v1.0.1, parallel-fork operating instructions

@@ -832,7 +832,7 @@ autonomous)"** — that codifies:
   provided secret bytes (the driver can't invent them).
 7. Update the roadmap (strikethrough the row, link to release tag
   and deploys.id) when each item ships.
-8. Write a Session I transcript at end-of-wave.
+8. Write a Session 0009.0 transcript at end-of-wave.

 Constraints the driver respects: no `git config` edits, no force-
 pushes, no `--amend` of pushed commits, no skipping pre-commit
@@ -868,8 +868,8 @@ Concretely:
   when the wave is done.
 5. Continue to Wave 2 if its dependencies are now met. Keep going until you hit a blocker
   (operator-provided secret needed, deploy failure, ambiguity).
-6. Write a Session I transcript at ~/git/ohm-infra/SESSION-I-TRANSCRIPT.md following the
-   Session H shape.
+6. Write a Session 0009.0 transcript at ~/git/ohm-infra/SESSION-0009.0-TRANSCRIPT.md following the
+   Session 0008.0 shape.

 Stop and wait for the operator if: a deploy fails, a release's Upgrade steps require a
 secret you can't generate, or you encounter cross-repo ambiguity. Do not invent secret
@@ -903,11 +903,11 @@ and updates the roadmap.

 By the time the operator wakes up, OHM should be on `v0.5.0` (or
 further if Wave 2 dependencies were met), the flotilla v1.1.0 cut
-should have happened if the VM rename produced one, and Session I's
+should have happened if the VM rename produced one, and Session 0009.0's
 transcript should record the journey.

 If the wave hits a blocker (most likely candidates: the VM rename
 needs operator-level GCP gestures that gcloud can't script around,
 or the collaboration-model change introduces a schema migration that
 needs the operator's blessing), the driver pauses and leaves a clear
-"waiting on operator" note in the partial Session I transcript.
+"waiting on operator" note in the partial Session 0009.0 transcript.
@@ -1,4 +1,4 @@
-# Session I — Transcript
+# Session 0009.0 — Transcript

 > Date: 2026-05-27 → 2026-05-28
 > Goal: Execute Wave 1 then Wave 2 of `ohm-rfc/ROADMAP.md` as the
@@ -230,7 +230,7 @@ flotilla deploy ohm-rfc-app
 ```

 All 9 phases green in ~30 seconds (verify took 4.7s, similar to the
-v0.3.0 deploy from Session H). `curl https://ohm.wiggleverse.org/api/health` returns `{"version":"0.4.0","status":"ok"}`.
+v0.3.0 deploy from Session 0008.0). `curl https://ohm.wiggleverse.org/api/health` returns `{"version":"0.4.0","status":"ok"}`.

 `deploys.id=4` recorded as `succeeded`.

@@ -299,8 +299,8 @@ Diagnosed: the VM at `/opt/ohm-app` has uncommitted modifications to
 `frontend/package-lock.json`. Reconstructed timeline:

 1. Pre-Session-I, the VM was at rfc-app v0.3.0. `git status` on the
-   VM at the start of Session I would have shown nothing (the v0.2.3
-   → v0.3.0 deploy in Session H was clean — coincidentally, that
+   VM at the start of Session 0009.0 would have shown nothing (the v0.2.3
+   → v0.3.0 deploy in Session 0008.0 was clean — coincidentally, that
   release's lockfile happened to be byte-equivalent to whatever
   `npm install` produces from the published `package.json`).
 2. v0.4.0 deploy phase 5 ran `npm install && npm run build` on the
@@ -323,7 +323,7 @@ Per the operating instructions ("Stop on first deploy failure"), the
 driver halts Wave 1 at this point. Wave 2 is not attempted.

 **Recovery for the operator** (paste into a shell with `gcloud` ADC
-already set up — see Session H §6 if not):
+already set up — see Session 0008.0 §6 if not):

 ```bash
 gcloud compute ssh ohm-app --zone us-central1-a --project wiggleverse-ohm -- \
@@ -749,11 +749,11 @@ Driver:

 ### Idempotency verification

-After the bootstrap, driver ran `~/git/ohm-infra/scripts/publish-transcript.sh --dry-run SESSION-I-TRANSCRIPT.md` to confirm the
+After the bootstrap, driver ran `~/git/ohm-infra/scripts/publish-transcript.sh --dry-run SESSION-0009.0-TRANSCRIPT.md` to confirm the
 single-session gesture works against the now-populated repo. Output:

 ```
-[publish-transcript] header OK: # Session I — Transcript
+[publish-transcript] header OK: # Session 0009.0 — Transcript
 [publish-transcript] size: 47095 bytes
 [publish-transcript] cloning … -> /var/folders/…/repo
 [publish-transcript] no changes — already published at 5f4f76c; exiting 0
@@ -782,7 +782,7 @@ audit-trail shape; the operator can update or archive it later.

 This published transcript itself — the version on `wiggleverse/ohm-session-history` after the bootstrap commit — does not yet include
 this arc. The next gesture (or the operator's first run of
-`publish-transcript.sh SESSION-I-TRANSCRIPT.md` after this extension
+`publish-transcript.sh SESSION-0009.0-TRANSCRIPT.md` after this extension
 commits) will push the diff.

 ---
@@ -798,7 +798,7 @@ landed mid-conversation:

 The operator asked: "let's update the session file names to give an
 idea of when they happened. ISO datetime in PST start time and end
-time after the SESSION-A-TRANSCRIPT."
+time after the SESSION-0001.0-TRANSCRIPT."

 Driver presented four format options + four start-time-derivation
 options as a structured question. Operator selected:
@@ -1081,7 +1081,7 @@ Three waves complete. OHM is on v0.10.0 (`deploys.id=11`,
     subagent's audit flagged this as medium severity; recommendation
     was ship-as-is, but operator review before first publish is the
     right discipline).
-   - Run `~/git/ohm-infra/scripts/publish-transcript.sh --dry-run SESSION-A-TRANSCRIPT.md` to confirm the script behaves.
+   - Run `~/git/ohm-infra/scripts/publish-transcript.sh --dry-run SESSION-0001.0-TRANSCRIPT.md` to confirm the script behaves.
   - Decide cadence: every session at cut time vs batched. The script
     supports both; v1 recommendation is "every session" since the
     artifact already exists locally.
@@ -1114,13 +1114,13 @@ Three waves complete. OHM is on v0.10.0 (`deploys.id=11`,
 ## Prompt the operator can paste into the next Claude Code session

 ```
-You are the OHM roadmap driver. The previous session (Session I)
+You are the OHM roadmap driver. The previous session (Session 0009.0)
 shipped rfc-app v0.4.0 / v0.5.0 / v0.6.0 / v0.7.0 / v0.8.0 /
 v0.10.0 / v0.13.0 to OHM (deploys.id 4, 6, 8, 9, 10, 11 — v0.6.0's
 deploy logged `aborted` due to a phase-7 SSE-grace timeout but is
 live, see SESSION-I §19.2). OHM is currently serving v0.10.0. Item
 #1 (VM rename) remains operator territory. Item #14 shipped late in
-Session I: `wiggleverse/ohm-session-history` is public on
+Session 0009.0: `wiggleverse/ohm-session-history` is public on
 git.wiggleverse.org with Sessions A–I published under CC BY 4.0,
 and the session protocol is now baked into the CLAUDE.md files of
 flotilla + ohm-rfc (rfc-app's CLAUDE.md update was deferred to the
@@ -1139,12 +1139,12 @@ the next session" section. The Wave 4 lineup per the roadmap text:
  CLOUDFLARE_TURNSTILE_SECRET` before the v0.12.0 deploy.)

 Before dispatching, check current main state — a parallel session
-may have shipped a docs-feature release between Session I's close
+may have shipped a docs-feature release between Session 0009.0's close
 and now (typically v0.9.0 or v0.14.0, claiming the next available
 slot). If so, factor the new HEAD into upgrade-from anchors in your
 subagent prompts.

-Same constraints as Session I: dispatch parallelizable items as
+Same constraints as Session 0009.0: dispatch parallelizable items as
 forked subagents in a single message, serialize the deploys,
 verify each, strikethrough the version-target table when an item
 ships, commit + push ohm-rfc, write the session transcript per
@@ -1160,7 +1160,7 @@ Session-I lessons to apply automatically:
 - Cross-repo subagents (rfc-app work from the flotilla CWD) must
  create their own `git worktree add` in the target repo.
 - Migration numbers: pre-allocate slots per subagent in the prompt
-  (Session I used slot 014 for #6 and 015 for #8 successfully; the
+  (Session 0009.0 used slot 014 for #6 and 015 for #8 successfully; the
  next free is 016 unless the parallel docs-feature session claimed
  it — check `ls /Users/benstull/git/rfc-app/backend/migrations/`
  before dispatching).
@@ -1,4 +1,4 @@
-# Session J — Transcript
+# Session 0010.0 — Transcript

 > Date: 2026-05-27 → 2026-05-28
 > Goal: Answer an operator UX question ("what's the difference between
@@ -96,7 +96,7 @@
 > per the CLAUDE.md exception.
 >
 > `rfc-app/CLAUDE.md` Session-protocol section was again deferred
-> (Session I had also deferred it for the same reason — the working
+> (Session 0009.0 had also deferred it for the same reason — the working
 > tree was unstable). I did not add it because the working tree
 > *was* clean by the time I shipped v0.14.0, but I deprioritized it
 > in the rush to deploy. The next OHM-touching rfc-app session
@@ -114,21 +114,21 @@
 - flotilla v1.0.1, OHM live on v0.10.0 (`deploys.id=11`).
 - This session's docs-feature work — `DOCS.md`,
  `backend/app/docs.py`, `frontend/src/components/Docs.jsx`, plus
-  edits to `api.py` / `App.jsx` / `api.js` — predated Session J's
+  edits to `api.py` / `App.jsx` / `api.js` — predated Session 0010.0's
  *explicit* arc and was the "operator-in-progress" state Session-I
  observed in `/Users/benstull/git/rfc-app` (Arc 8 of that
-  transcript). The two sessions overlapped temporally; Session I
+  transcript). The two sessions overlapped temporally; Session 0009.0
  routed around the in-progress files via throwaway worktrees +
-  `git update-ref refs/heads/main` while Session J continued
+  `git update-ref refs/heads/main` while Session 0010.0 continued
  building the docs feature in the main checkout.
 - The operator was driving both sessions, pivoting between them as
  each surfaced something needing a human decision.

-The `git status` Session J inherited at its first significant
+The `git status` Session 0010.0 inherited at its first significant
 checkpoint showed the Session-I-induced ghost-revert: 28 staged
 "modifications" (actually the diff between the v0.7.0-era working-
 tree files and the post-`update-ref` v0.10.0 HEAD) plus my 3
-untracked files. The driver in Session I had documented this
+untracked files. The driver in Session 0009.0 had documented this
 exact shape in its Arc-15 "cross-session staged state question"
 section — I inherited the artifact.

@@ -429,7 +429,7 @@ root) works without it; the CHANGELOG "Upgrade steps (from 0.13.0)"
 documents the optional override.

 Did NOT update `rfc-app/CLAUDE.md` to add the Session-protocol
-section that Session I had deferred — deprioritized in the rush
+section that Session 0009.0 had deferred — deprioritized in the rush
 to deploy. Noted in §19.2 below.

 The commit landed with committer `Ben Stull <benstull@mac.lan>` —
@@ -588,7 +588,7 @@ dismiss the chip.
 ### Arc 18 — Transcript

 Operator asked for this transcript per the standing protocol.
-Read `SESSION-I-TRANSCRIPT-2026-05-27T23-30--2026-05-28T03-15.md`
+Read `SESSION-0009.0-TRANSCRIPT-2026-05-27T23-30--2026-05-28T03-15.md`
 to match shape and voice. Read the publish-transcript script to
 understand the filename regex and idempotency contract. Read
 `ohm-rfc/ROADMAP.md` to figure out which row to strike — and
@@ -608,14 +608,14 @@ slot collision.
 2. **Row #12** (Owner-only invite) target version changed from
   `v0.14.0 (needs v0.5.0 + v0.7.0)` to `v0.16.0 (needs v0.5.0 +
   v0.7.0; v0.14.0 slot was claimed out-of-band by item #15 per
-   Session J)` to record the slot reshuffling explicitly. v0.15.0
+   Session 0010.0)` to record the slot reshuffling explicitly. v0.15.0
   remains reserved for #13 Amplitude, so #12 jumps to v0.16.0.

 Committed to `ohm-rfc/main` as `4c89179` and pushed
 (`d6af91f..4c89179 main -> main`).

 Transcript written. The filename
-`SESSION-J-TRANSCRIPT-2026-05-27T23-50--2026-05-28T03-20.md`
+`SESSION-0010.0-TRANSCRIPT-2026-05-27T23-50--2026-05-28T03-20.md`
 matches the convention. Published via
 `~/git/ohm-infra/scripts/publish-transcript.sh` at
 commit `44995c9` on `wiggleverse/ohm-session-history`
@@ -647,10 +647,10 @@ idempotency contract handles the round-trip cleanly.
 | | |
 | --- | --- |
 | flotilla | Unchanged. v1.0.1 installed; deployment registered; 3 new `deploys` rows added this session (`id=12 failed`, `id=13 failed`, `id=14 succeeded` — all v0.14.0). |
-| rfc-app | `de28272` tag `v0.14.0`. Pushed to `origin = git.wiggleverse.org/ben.stull/rfc-app` AND `benstull = git.benstull.org/benstull/rfc-app`. `VERSION = 0.14.0`, `frontend/package.json#version = 0.14.0`. `CHANGELOG.md` has a new top entry. CLAUDE.md Session-protocol pointer **still deferred** — Session I also deferred this. |
+| rfc-app | `de28272` tag `v0.14.0`. Pushed to `origin = git.wiggleverse.org/ben.stull/rfc-app` AND `benstull = git.benstull.org/benstull/rfc-app`. `VERSION = 0.14.0`, `frontend/package.json#version = 0.14.0`. `CHANGELOG.md` has a new top entry. CLAUDE.md Session-protocol pointer **still deferred** — Session 0009.0 also deferred this. |
 | ohm-rfc | `4c89179` (`.rfc-app-version` bumped to `0.14.0` via `d6af91f`; ROADMAP edited via `4c89179` with new row #15 struck through and row #12's target version bumped v0.14.0 → v0.16.0). |
 | OHM live | `deploys.id=14`, v0.14.0, healthy. `/api/health` returns `{"version":"0.14.0","status":"ok"}`. `/docs` reachable anonymously and serves the new user guide. |
-| ohm-infra | New transcript: `SESSION-J-TRANSCRIPT-2026-05-27T23-50--2026-05-28T03-20.md`. No other changes to scripts or protocol. |
+| ohm-infra | New transcript: `SESSION-0010.0-TRANSCRIPT-2026-05-27T23-50--2026-05-28T03-20.md`. No other changes to scripts or protocol. |
 | ohm-session-history | This transcript first published at `44995c9` (add); Arc-20 update will re-publish as an "update SESSION-J-…" commit when the operator runs `publish-transcript.sh` again (idempotent — diff push, not a duplicate add). Adds one new file alongside Sessions A–I. |
 | Spawned task | One chip showing for the operator: "Add VM-origin preflight to flotilla deploy" — cwd-rooted in the flotilla repo. |

@@ -658,7 +658,7 @@ idempotency contract handles the round-trip cleanly.
 | --- | --- |
 | Docs feature shipped | ✅ rfc-app v0.14.0 + OHM `deploys.id=14`. Not a roadmap item; operator-driven from the admin-vs-owner UX question. |
 | ROADMAP collision | v0.14.0 slot was reserved for #12 Owner-only invite; that row's target version bumped to v0.16.0 in this session's ROADMAP edit. |
-| CLAUDE.md update | Deferred. (Same as Session I.) |
+| CLAUDE.md update | Deferred. (Same as Session 0009.0.) |

 ---

@@ -697,8 +697,8 @@ idempotency contract handles the round-trip cleanly.
   the protocol document doesn't currently take a position.

 4. **`rfc-app/CLAUDE.md` Session-protocol section is now deferred
-   twice.** Session I deferred it because the working tree was
-   unstable. Session J deferred it because the deploy was the
+   twice.** Session 0009.0 deferred it because the working tree was
+   unstable. Session 0010.0 deferred it because the deploy was the
   priority and the tree only stabilized late. The third
   rfc-app-touching session should make the addition non-deferrable
   (e.g. fail the end-of-session checklist if rfc-app's CLAUDE.md
@@ -750,8 +750,8 @@ idempotency contract handles the round-trip cleanly.

 ```
 You are the OHM roadmap driver. Two sessions just closed in
-parallel: Session I shipped rfc-app v0.4.0 / v0.5.0 / v0.6.0 /
-v0.7.0 / v0.8.0 / v0.10.0 / v0.13.0 to OHM, and Session J shipped
+parallel: Session 0009.0 shipped rfc-app v0.4.0 / v0.5.0 / v0.6.0 /
+v0.7.0 / v0.8.0 / v0.10.0 / v0.13.0 to OHM, and Session 0010.0 shipped
 rfc-app v0.14.0 (DOCS.md + /docs public user guide; not a
 roadmap item — operator-driven from a UX question) to OHM
 (deploys.id=14). OHM is currently serving v0.14.0. Read
@@ -781,7 +781,7 @@ cross-repo ambiguity.

 Session-I + Session-J lessons to apply automatically:

- **VM origin vs pin source divergence (Session J)**: after pushing
+- **VM origin vs pin source divergence (Session 0010.0)**: after pushing
  a rfc-app tag to `origin = git.wiggleverse.org`, ALSO push to
  `benstull = git.benstull.org`. The production VM at /opt/ohm-app
  fetches from git.benstull.org, not git.wiggleverse.org; the two
@@ -792,7 +792,7 @@ Session-I + Session-J lessons to apply automatically:
    git push origin main && git push origin vX.Y.Z
    git push benstull main && git push benstull vX.Y.Z

- **Ghost-revert recovery (Session J)**: if you find a working tree
+- **Ghost-revert recovery (Session 0010.0)**: if you find a working tree
  whose `git status` shows 20+ files as staged-deletions/
  modifications that don't match your session's edits, the cause
  is a prior session's `git update-ref refs/heads/main` advancing
@@ -803,7 +803,7 @@ Session-I + Session-J lessons to apply automatically:
  (untracked files survive), then manually re-apply any genuine
  edits against the current HEAD's file structure.

- **Subagents push feature branches only (Session I)**. Driver
+- **Subagents push feature branches only (Session 0009.0)**. Driver
  tags, bumps the ohm-rfc pin, and runs the deploy. Do NOT have
  subagents bump the pin themselves.

@@ -812,7 +812,7 @@ Session-I + Session-J lessons to apply automatically:
  only to the driver's CWD.

 - **Migration numbers**: pre-allocate slots per subagent in the
-  prompt. Session I used 014 for #6 and 015 for #8. Next free is
+  prompt. Session 0009.0 used 014 for #6 and 015 for #8. Next free is
  016 — check `ls /Users/benstull/git/rfc-app/backend/migrations/`
  before dispatching to confirm.

@@ -827,7 +827,7 @@ Session-I + Session-J lessons to apply automatically:
  integration.

 - **Item #12 Owner-only invite** has been re-targeted from v0.14.0
-  to v0.16.0 per Session J's docs-release slot collision. Update
+  to v0.16.0 per Session 0010.0's docs-release slot collision. Update
  any upgrade-from anchors accordingly.

 - **Item #1 VM rename** and operator-provided secrets stay
@@ -1,4 +1,4 @@
-# Session K — Transcript
+# Session 0011.0 — Transcript

 > Date: 2026-05-28
 > Goal: Execute Wave 4 of `ohm-rfc/ROADMAP.md` as the autonomous
@@ -37,9 +37,9 @@
 >
 > **Session-letter correction logged:** the driver's prior commits
 > in this session (`64f5344`, `54cadd8` on `ohm-rfc`) labeled this
-> as Session J. The operator corrected mid-session: Session J was
+> as Session 0010.0. The operator corrected mid-session: Session 0010.0 was
 > the parallel docs-feature / v0.14.0 session that ran during
-> Session I's wind-down; this driver session is Session K. The
+> Session 0009.0's wind-down; this driver session is Session 0011.0. The
 > correction landed in commit `cfc0c6a` on `ohm-rfc` (which fixed
 > the two prior strikethrough rows). The mislabeled commits stay
 > as-written — no force-push, no `--amend` — per session-protocol
@@ -64,11 +64,11 @@
  were from the parallel docs-feature session retrying.
 - **ohm-rfc-app-flotilla**: `main` at `a1588c1` (v1.0.1 + CLAUDE.md
  bake-in). No work needed in this repo for Wave 4.
- **ohm-infra**: most recent transcript was Session I, published.
+- **ohm-infra**: most recent transcript was Session 0009.0, published.
  The convention says the next letter is J, but the parallel
-  docs-feature session that shipped v0.14.0 between Session I's
+  docs-feature session that shipped v0.14.0 between Session 0009.0's
  wind-down and this session's start claimed J — the operator
-  confirmed mid-session that this driver session is Session K
+  confirmed mid-session that this driver session is Session 0011.0
  rather than J.
 - **Driver brief**: the operator's bedtime prompt (the one that
  opens this session) said Wave 4 lineup is #7 v0.9.0 + #9 v0.11.0
@@ -146,7 +146,7 @@ not the highest semver). Ran `flotilla deploy ohm-rfc-app`:
 opened `deploys.id=15`, all 9 phases green, verify took 4.8s,
 `/api/health` returned `{"version":"0.9.0","status":"ok"}`.

-The §8.2 stale-lockfile fault that bit Session I's v0.5.0 deploy
+The §8.2 stale-lockfile fault that bit Session 0009.0's v0.5.0 deploy
 did NOT recur — subagent κ ran `npm install` in `frontend/` after
 bumping `package.json`, the lockfile diff is in the commit, the
 VM's `git checkout` had nothing to clobber.
@@ -342,9 +342,9 @@ landed in `cfc0c6a` (alongside the v0.12.0 status row); #19
 landed in `cce9fe3` as a standalone roadmap commit at the very
 end of the session.

-The mid-session correction — "Not session J — session K" — landed
+The mid-session correction — "Not session 0010.0 — session 0011.0" — landed
 in `cfc0c6a` too: it fixed the two prior strikethrough rows
-(`#7` v0.9.0 and `#9` v0.11.0) to attribute Session K, not J.
+(`#7` v0.9.0 and `#9` v0.11.0) to attribute Session 0011.0, not J.
 The two prior commits with the wrong attribution (`64f5344`,
 `54cadd8`) stay as written, with the correction documented in
 this transcript per session-protocol §3 (no curation, no
@@ -360,7 +360,7 @@ amend-after-push).
 | OHM live | `deploys.id=16`, `v0.11.0`, healthy. `/api/health` returns `{"version":"0.11.0","status":"ok"}`. `/admin/users` 200s. `/settings/notifications` 200s. v0.12.0 deploy is paused on operator secret. |
 | ohm-rfc | `cce9fe3`. `.rfc-app-version` = `0.11.0`. ROADMAP reflects #7 + #9 shipped, #10 tagged-but-paused, #16 + #17 + #18 + #19 captured. |
 | ohm-rfc-app-flotilla | `a1588c1` (unchanged — no flotilla work in Wave 4). |
-| ohm-infra | this transcript at `SESSION-K-TRANSCRIPT-2026-05-28T03-20--2026-05-28T03-55.md`; publish pending. |
+| ohm-infra | this transcript at `SESSION-0011.0-TRANSCRIPT-2026-05-28T03-20--2026-05-28T03-55.md`; publish pending. |

 | Wave 4 ledger | Status |
 | --- | --- |
@@ -487,7 +487,7 @@ hand.)

 5. **Session-letter correction documentation**: this transcript
   records the J→K correction explicitly. If the parallel
-   docs-feature session (the real Session J) hasn't yet published
+   docs-feature session (the real Session 0010.0) hasn't yet published
   its transcript, that's its own session's responsibility — not
   this one's.

@@ -496,7 +496,7 @@ hand.)
 ## Prompt the operator can paste into the next Claude Code session

 ```
-You are the OHM roadmap driver. The previous session (Session K)
+You are the OHM roadmap driver. The previous session (Session 0011.0)
 shipped rfc-app v0.9.0 (admin user-management page, item #7,
 deploys.id=15) and v0.11.0 (trust device 30d, item #9,
 deploys.id=16) to OHM. v0.12.0 (CloudFlare Turnstile, item #10)
@@ -543,7 +543,7 @@ B. **Start Wave 5** if Wave 4 is clear and the operator wants to
     `backend/app/api_admin.py` for the create-user affordance,
     plus `backend/app/email.py` for the invite-email template.

-Wave-5 dispatch should reuse Session K's subagent pattern: each
+Wave-5 dispatch should reuse Session 0011.0's subagent pattern: each
 subagent creates its own `git worktree add` in
 `/Users/benstull/git/rfc-app`, pushes a feature branch, does NOT
 tag, does NOT touch the ohm-rfc pin, does NOT run flotilla deploy
@@ -572,7 +572,7 @@ Session-K lessons to apply automatically:
 - Item #1 VM rename and operator-provided secrets stay operator
  territory.

-End-of-session: write `~/git/ohm-infra/SESSION-L-TRANSCRIPT-…md`
+End-of-session: write `~/git/ohm-infra/SESSION-0012.0-TRANSCRIPT-…md`
 and publish via `~/git/ohm-infra/scripts/publish-transcript.sh`.
 ```

@@ -703,7 +703,7 @@ ROADMAP row strikethrough for #10 finalized with deploys.id=17
 ## Updated next-session prompt

 ```
-You are the OHM roadmap driver. The previous session (Session K)
+You are the OHM roadmap driver. The previous session (Session 0011.0)
 shipped rfc-app v0.9.0 (admin user-management, #7, deploys.id=15),
 v0.11.0 (trust device 30d, #9, deploys.id=16), and v0.12.0
 (CloudFlare Turnstile, #10, deploys.id=17 → 18 after
@@ -712,8 +712,8 @@ OHM serves v0.12.0 with Turnstile abuse defense fail-closed.

 Read `~/git/ohm-infra/SESSION-PROTOCOL.md` and
 `/Users/benstull/projects/wiggleverse/ohm-rfc/ROADMAP.md`
-end-to-end. The next session letter is L (Session K = this driver,
-Session J = the parallel docs-feature/v0.14.0 session).
+end-to-end. The next session letter is L (Session 0011.0 = this driver,
+Session 0010.0 = the parallel docs-feature/v0.14.0 session).

 **Hard rule baked in mid-Session-K**: never EVER ask the operator
 to paste secret bytes into the conversation, not even as one
@@ -727,7 +727,7 @@ for secret bytes" section).

 The active wave is Wave 5. Per the roadmap:
 - **Session ν (Track B): #12 Owner invite → v0.16.0** (originally
-  v0.14.0, but Session J's docs-feature claimed v0.14.0; #12
+  v0.14.0, but Session 0010.0's docs-feature claimed v0.14.0; #12
  bumped to next available slot. Depends on #5 + #7 — both
  shipped.)
 - **Session ξ (Track A): #13 Amplitude → v0.15.0** (operator
@@ -735,7 +735,7 @@ The active wave is Wave 5. Per the roadmap:
  #10's `CLOUDFLARE_TURNSTILE_SECRET`. Subagent CHANGELOG MUST
  step pauses the wave; do not invent the key.)

-Plus four operator-added items captured in Session K:
+Plus four operator-added items captured in Session 0011.0:
 - **#16 Admin-create user + invite email** (with optional
  custom message). rfc-app, depends on #5 + #7 (both shipped).
  Lives on `/admin/users` from v0.9.0. A natural Wave-5 candidate
@@ -753,7 +753,7 @@ Plus four operator-added items captured in Session K:
  alone bumps pins, sets secrets, runs flotilla deploy. ("I'm
  the only one that gets to yolo.")

-Dispatch shape: same as Session K. Each subagent creates its own
+Dispatch shape: same as Session 0011.0. Each subagent creates its own
 `git worktree add` in `/Users/benstull/git/rfc-app`, pushes a
 feature branch, does NOT tag, does NOT touch the ohm-rfc pin,
 does NOT run flotilla deploy — the driver integrates serially.
@@ -770,7 +770,7 @@ Session-K lessons to apply automatically:
  → 0.7.0 → 0.6.0 → 0.5.0 → 0.4.0 → 0.3.0 → 0.2.x. Subagents
  inserting a new entry slot it at the right position; cherry-
  pick conflicts get hand-assembled at integration time when two
-  parallel features ship at adjacent slots (Session K hit this
+  parallel features ship at adjacent slots (Session 0011.0 hit this
  for v0.11.0 + v0.12.0 — both wanted to insert above v0.10.0).
 - backend pytest needs `PYTHONPATH=.` from `backend/` unless a
  future cleanup adds `[tool.pytest.ini_options] pythonpath =
@@ -778,7 +778,7 @@ Session-K lessons to apply automatically:
 - `Login.jsx` is now contested territory — Sessions K's v0.11.0
  + v0.12.0 both edited the verify step. Expect a conflict any
  time a future release touches the auth path. Resolve by keeping
-  both injections in sequence (driver pattern from Session K).
+  both injections in sequence (driver pattern from Session 0011.0).
 - `Admin.jsx` is now contested territory too if #16 ships on top
  of #7 (v0.9.0)'s admin surface.
 - Operator-provided secrets stay operator territory. The wave-
@@ -790,6 +790,6 @@ Session-K lessons to apply automatically:
 - Item #1 VM rename and the new operator-decision items (#17
  inventory, #19 PR coordination) stay operator territory.

-End-of-session: write `~/git/ohm-infra/SESSION-L-TRANSCRIPT-…md`
+End-of-session: write `~/git/ohm-infra/SESSION-0012.0-TRANSCRIPT-…md`
 and publish via `~/git/ohm-infra/scripts/publish-transcript.sh`.
 ```
@@ -1,4 +1,4 @@
-# Session L — Transcript
+# Session 0012.0 — Transcript

 > Date: 2026-05-28
 > Goal: Execute Wave 5 of `ohm-rfc/ROADMAP.md` as the autonomous
@@ -55,8 +55,8 @@
 > Side effect of the pin jumping from `0.12.0` → `0.15.0` → `0.16.0`
 > → `0.17.0`: OHM now also runs v0.13.0's cookie-consent banner
 > and v0.14.0's `/docs` route, which had been integrated on
-> `main` since Session J but were not currently deployed because
-> the pin had rolled back during Session K's Wave-4 sequence.
+> `main` since Session 0010.0 but were not currently deployed because
+> the pin had rolled back during Session 0011.0's Wave-4 sequence.

 ---

@@ -68,7 +68,7 @@
  `v0.2.0, .1, .2, .3, v0.3.0, v0.4.0, v0.5.0, v0.6.0, v0.7.0,
  v0.8.0, v0.9.0, v0.10.0, v0.11.0, v0.12.0, v0.13.0, v0.14.0`.
  Last migration on disk: `017_device_trust.sql` (slot 016
-  reserved + skipped per Session K).
+  reserved + skipped per Session 0011.0).
 - **ohm-rfc**: `.rfc-app-version` = `0.12.0`. The pin was "below"
  v0.13.0 (cookie banner) and v0.14.0 (`/docs`) — those features
  were integrated on rfc-app `main` but not currently deployed
@@ -81,15 +81,15 @@
  `{"version":"0.12.0","status":"ok"}`. `flotilla deploy log
  ohm-rfc-app` showed last successful deploy as `deploys.id=18`
  (v0.12.0, succeeded, 11:18 UTC) — the post-`TURNSTILE_REQUIRED=true`
-  re-deploy from Session K that put abuse defense fail-closed.
+  re-deploy from Session 0011.0 that put abuse defense fail-closed.
 - **ohm-rfc-app-flotilla**: `main` at `65c0e55` (CLAUDE.md
  secret-set gesture correction). No flotilla work expected in
  Wave 5; none performed.
- **ohm-infra**: most recent transcript is Session K
-  (`SESSION-K-TRANSCRIPT-2026-05-28T03-20--2026-05-28T03-55.md`).
-  Next letter is L (Session K = previous driver; Session J = the
+- **ohm-infra**: most recent transcript is Session 0011.0
+  (`SESSION-0011.0-TRANSCRIPT-2026-05-28T03-20--2026-05-28T03-55.md`).
+  Next letter is L (Session 0011.0 = previous driver; Session 0010.0 = the
  parallel docs-feature / v0.14.0 session that ran during
-  Session I's wind-down).
+  Session 0009.0's wind-down).
 - **Hard rule baked in mid-Session-K**: never EVER ask the operator
  to paste secret bytes into the conversation. Stayed honored
  through this session — the Amplitude key the operator pasted is
@@ -120,7 +120,7 @@ with parallel `Agent` tool uses, `subagent_type: general-purpose`,
 running in the background. Each subagent created its own
 `git worktree add` in `/Users/benstull/git/rfc-app-<target-version-
 slug>` (the `Agent` tool's worktree isolation only covers the
-flotilla CWD, not the rfc-app CWD subagents needed — Session K
+flotilla CWD, not the rfc-app CWD subagents needed — Session 0011.0
 lesson). Each prompt was self-contained: full roadmap text,
 target version, reserved migration slot (018 for ν, 019 for ο,
 none for ξ), descending-order CHANGELOG insertion point, hard
@@ -221,7 +221,7 @@ operator added three new roadmap items:
  claim so the Amplitude record is created with the OHM user_id
  from the first event rather than as an anonymous device that
  retroactively links). Part C explicitly names what "ships
-  inline in Session L" vs. what waits for the data-informed
+  inline in Session 0012.0" vs. what waits for the data-informed
  audit. Committed to ohm-rfc at `f006d33` (Parts A + B), then
  `1c88f71` (Part C added).
 - **#22 Pro-analytics-consent copy on the privacy/cookies
@@ -341,7 +341,7 @@ scopes, hand-reconcilable.

 The driver squash-merged each branch into rfc-app `main` in
 version order, hand-resolving conflicts and adding inline
-Amplitude wiring per #21 Part C "ships inline in Session L":
+Amplitude wiring per #21 Part C "ships inline in Session 0012.0":

 **v0.15.0 integration** — fast-forward squash from `b3f1b15`
 (no conflicts: main was at ξ's base). Driver-side extensions
@@ -424,7 +424,7 @@ the union of ν's 237 + ο's 15 new). Inline Amplitude wiring per

 ### Arc 7 — Three serialized deploys to OHM

-Per the §8.3 single-in-flight-deploy rule and Session K's
+Per the §8.3 single-in-flight-deploy rule and Session 0011.0's
 serialization lesson, each version deployed in turn:

 - **Overlay set**: `flotilla overlay set ohm-rfc-app
@@ -438,7 +438,7 @@ serialization lesson, each version deployed in turn:
  `{"version":"0.15.0","status":"ok"}`. Side-effect features
  v0.13.0 (cookie banner) + v0.14.0 (`/docs` route) now also
  on production for the first time since the pin had rolled
-  back during Session K's Wave-4 sequence.
+  back during Session 0011.0's Wave-4 sequence.
 - **v0.16.0**: pin bumped, committed `1c2bb26`, pushed.
  `flotilla deploy run ohm-rfc-app` → `deploys.id=20`, all 9
  phases green, verify 2.4s. `/api/health` returns
@@ -463,7 +463,7 @@ about the pre-vendor wording. Committed at `47cb2f9`, pushed.
 ### Arc 9 — Protocol amendment: subagent transcripts (Session-L-introduced)

 After the driver had written what it thought was the final
-Session L transcript, the operator surfaced a series of follow-up
+Session 0012.0 transcript, the operator surfaced a series of follow-up
 asks:

 1. "Prompt for next session pls?" + "and update transcript" —
@@ -489,8 +489,8 @@ test-suite outcomes). The amendment introduces subsession
 transcripts:

 - **Naming**: `SESSION-<letter>.<n>-TRANSCRIPT-<start>--<end>.md`
-  (e.g. `SESSION-M.1-TRANSCRIPT-…md` for the first subagent in
-  Session M). Nested ordinals (`.1.1`) supported if a forked
+  (e.g. `SESSION-0013.1-TRANSCRIPT-…md` for the first subagent in
+  Session 0013.0). Nested ordinals (`.1.1`) supported if a forked
  subagent itself dispatches another.
 - **Dispatch contract**: the driver pre-assigns subsession IDs
  in dispatch order, names the exact filename + the
@@ -501,7 +501,7 @@ transcripts:
  publishes its own + each subsession's transcript via the
  publish script. Stub-write on subagent's behalf if the
  subagent crashed without producing one.
- **Applies from Session M onward.** Session L itself ran under
+- **Applies from Session 0013.0 onward.** Session 0012.0 itself ran under
  the prior "driver-only" rule because the amendment landed
  mid-session after L's three subagents had already returned;
  no `SESSION-L.1` / `.2` / `.3` transcript files exist or will
@@ -516,10 +516,10 @@ Changes landed:
  validator regex extended from `[A-Za-z]+` to
  `[A-Za-z]+(\.[0-9]+)*` so subsession filenames pass.
  Dry-run validation confirmed: the parent filename still
-  validates, and a hypothetical `SESSION-M.1-TRANSCRIPT-…md`
+  validates, and a hypothetical `SESSION-0013.1-TRANSCRIPT-…md`
  would also pass.
- Session L's next-session prompt (below) updated with the new
-  dispatch shape so Session M's driver inherits it.
+- Session 0012.0's next-session prompt (below) updated with the new
+  dispatch shape so Session 0013.0's driver inherits it.

 The fourth ask — "update the transcript again — always do that
 as a final step of a session" — was captured as a feedback
@@ -553,7 +553,7 @@ So this arc 11 captures: the operator reinforced the discipline,
 the driver re-finalized the transcript with this arc included,
 and re-published. The publish script's idempotent-on-identical /
 update-on-changed behavior means the re-publish lands as an
-"Update SESSION-L-TRANSCRIPT-…md" commit on
+"Update SESSION-0012.0-TRANSCRIPT-…md" commit on
 `wiggleverse/ohm-session-history`, not a duplicate file. The
 filename's `--<end>` timestamp stays the original
 `2026-05-28T05-17` (the time of the first finalization); the
@@ -565,7 +565,7 @@ Future driver sessions should expect this pattern to recur:
 "finalization" is not a one-shot gesture. Any operator
 instruction landing after the first publish triggers another
 finalize + re-publish cycle. The discipline is captured for
-Session M onward in the next-session prompt's closing block
+Session 0013.0 onward in the next-session prompt's closing block
 + the feedback memory.

 ### Arc 12 — Roadmap item #23 surfaced: rename transcripts to numeric form
@@ -594,7 +594,7 @@ led, one-session operational gesture):
  add+delete (preserve history); redirect tombstones vs. 404
  (URL breakage for external references); sequencing relative
  to the next-letter-after-L session (most-elegant timing is
-  Session M as the rename session itself, so `SESSION-0013.0`
+  Session 0013.0 as the rename session itself, so `SESSION-0013.0`
  debuts as the new shape from the start). Decide at session
  time.

@@ -632,10 +632,10 @@ cycle continues. The discipline holds open-ended.
 | #12 Owner invite (v0.16.0) | ✅ shipped, `deploys.id=20` |
 | #16 Admin-create user + invite (v0.17.0) | ✅ shipped, `deploys.id=21` |

-| New roadmap items captured (Session L) | Status |
+| New roadmap items captured (Session 0012.0) | Status |
 | --- | --- |
 | #20 Email deliverability | 📝 captured, awaiting session |
-| #21 Amplitude audit + standing discipline | 📝 captured. Part C identity-lifecycle work shipped inline in Session L's v0.15.0 + v0.16.0 + v0.17.0 commits. Part A audit waits for ~1 week of real Amplitude data; Part B discipline can start anytime. |
+| #21 Amplitude audit + standing discipline | 📝 captured. Part C identity-lifecycle work shipped inline in Session 0012.0's v0.15.0 + v0.16.0 + v0.17.0 commits. Part A audit waits for ~1 week of real Amplitude data; Part B discipline can start anytime. |
 | #22 Pro-analytics-consent copy on privacy/cookies opt-in | 📝 captured. Waiting on operator-drafted + counsel-reviewed copy. |
 | #23 Rename transcripts `SESSION-<letter>` → `SESSION-NNNN.M` | 📝 captured. One Track-Ω session, operator-led. Mapping A→0001.0 through L→0012.0 spelled out in the item. Surfaces enumerated (12 transcripts + protocol + publish-script + cross-doc refs). |

@@ -669,7 +669,7 @@ cycle continues. The discipline holds open-ended.
   said "OHM serves v0.12.0" which was accurate, but did NOT
   mention that v0.13.0 and v0.14.0 features (cookie banner,
   `/docs`) were integrated on `main` but absent from the live
-   deploy because the pin had rolled back during Session K.
+   deploy because the pin had rolled back during Session 0011.0.
   Any Wave-5 deploy was always going to bring those features
   back; the driver flagged this in arc 1 + handled it
   transparently, but a session-bootstrap script that emits
@@ -741,7 +741,7 @@ cycle continues. The discipline holds open-ended.
   team if it bites again.
 6. **Item #1 VM rename + #17 inventory + #19 PR coordination
   + #23 transcript-rename** stay operator territory. #23
-   adds one decision-point: do you want Session M to be the
+   adds one decision-point: do you want Session 0013.0 to be the
   rename session (so it debuts as `SESSION-0013.0`), or run
   a few more letter-form sessions first and rename in a
   later session?
@@ -751,7 +751,7 @@ cycle continues. The discipline holds open-ended.
 ## Updated next-session prompt

 ```
-You are the OHM roadmap driver. The previous session (Session L)
+You are the OHM roadmap driver. The previous session (Session 0012.0)
 shipped rfc-app v0.15.0 (Amplitude Analytics + Session Replay,
 #13, deploys.id=19), v0.16.0 (per-RFC owner invites, #12,
 deploys.id=20), and v0.17.0 (admin-create user + invite email,
@@ -759,7 +759,7 @@ deploys.id=20), and v0.17.0 (admin-create user + invite email,
 v0.17.0 with Amplitude analytics + session replay live (gated by
 the v0.13.0 cookie banner), v0.13.0 cookie banner itself, v0.14.0
 /docs route, per-RFC owner invites, and admin-create user invites
-all in production for the first time. Session L also folded #21
+all in production for the first time. Session 0012.0 also folded #21
 Part C identity-lifecycle work inline across all three release
 commits — identify({ user_id, properties }) + setUserProperties()
 + amplitude.reset on sign-out + identify-BEFORE-track on every
@@ -769,19 +769,19 @@ Read `~/git/ohm-infra/SESSION-PROTOCOL.md` and
 `/Users/benstull/projects/wiggleverse/ohm-rfc/ROADMAP.md`
 end-to-end. The next session letter is M.

-**New protocol amendment from Session L**: subagents write their
+**New protocol amendment from Session 0012.0**: subagents write their
 own transcripts (subsession files like
-`SESSION-M.1-TRANSCRIPT-<start>--<end>.md`) before returning to
+`SESSION-0013.1-TRANSCRIPT-<start>--<end>.md`) before returning to
 the driver. The driver pre-assigns each subagent's subsession ID
 in the dispatch prompt. The driver's own Session-M transcript
 stays load-bearing for cross-subagent synthesis + cut-state,
 with cross-references to each subsession. See
 SESSION-PROTOCOL.md §5 for the binding form. The publish
-script's filename validator was extended in Session L to accept
+script's filename validator was extended in Session 0012.0 to accept
 `SESSION-<letter>.<n>-TRANSCRIPT-…md`.

-**Hard rule (Session K + Session L): never EVER ask the operator
-to paste secret bytes into the conversation.** Session L
+**Hard rule (Session 0011.0 + Session 0012.0): never EVER ask the operator
+to paste secret bytes into the conversation.** Session 0012.0
 confirmed the corollary: public bundle-embedded values
 (`VITE_AMPLITUDE_API_KEY`, `VITE_TURNSTILE_SITE_KEY`) are fine
 to receive in conversation and set via `flotilla overlay set` —
@@ -791,7 +791,7 @@ default to the operator-run gesture (`pbpaste | flotilla secret
 set …` for secrets; `flotilla overlay set DEPLOYMENT KEY=VALUE`
 for non-secrets).

-Wave 6 candidates (per Session L's roadmap state):
+Wave 6 candidates (per Session 0012.0's roadmap state):
 - **#20 Email deliverability** (Track Ω + rfc-app template
  hygiene) — high priority now that two invite paths ship and
  the recipient's first contact with OHM is an email; spam
@@ -821,7 +821,7 @@ Wave 6 candidates (per Session L's roadmap state):
  merges.
 - **#1 VM rename** — operator-led ops gesture.

-Dispatch shape (updated for Session M per the Session-L
+Dispatch shape (updated for Session 0013.0 per the Session-L
 amendment):
 1. For each subagent, pre-assign a subsession ID: M.1, M.2, …
 2. In the dispatch prompt, name the subsession ID + tell the
@@ -841,7 +841,7 @@ amendment):
   (the regex now accepts `SESSION-<letter>.<n>-TRANSCRIPT-…md`).

 Session-L lessons to apply automatically (in addition to all of
-Session K's):
+Session 0011.0's):
 - **Vendor prompts can override the roadmap's pre-vendor
  guesses.** When the operator pastes a vendor installation
  prompt mid-session (Amplitude this time; could be Stripe,
@@ -876,14 +876,14 @@ Session K's):
  anonymous device that retroactively links. SPEC chapter to
  codify is part of #21 Part B.
 - **Pin-jump side effects**: when the pin bumps past versions
-  that were integrated-but-undeployed (in Session L: v0.13.0
+  that were integrated-but-undeployed (in Session 0012.0: v0.13.0
  cookie banner + v0.14.0 /docs both went live as a side
  effect of the v0.15.0 → v0.17.0 sequence), flag this to the
  operator at the deploy step. Not a blocker; just transparency.
 - **CHANGELOG slot 016 stays reserved + skipped**. v0.15.0
  used no schema migration; #12 took slot 018, #16 took 019.
  Next free: 016, 020, 021, ….
- **Login.jsx remains contested**: Session L's v0.15.0
+- **Login.jsx remains contested**: Session 0012.0's v0.15.0
  Amplitude wiring added `User Signed In` calls at the three
  verify paths (otc / passcode / trust-device). Future
  auth-touching releases need to preserve v0.11.0 + v0.12.0 +
@@ -906,7 +906,7 @@ Session K's):
  promptly so the operator sees them on the gitea side without
  waiting.

-End-of-session: write `~/git/ohm-infra/SESSION-M-TRANSCRIPT-…md`
+End-of-session: write `~/git/ohm-infra/SESSION-0013.0-TRANSCRIPT-…md`
 (your main transcript) AND ensure each subagent's subsession
 transcript was written. Per Session-L feedback: **transcript is
 the LAST step** — finish all other work first, then finalize the
@@ -1,4 +1,4 @@
-# Session M — Transcript
+# Session 0013.0 — Transcript

 > Date: 2026-05-28
 > Goal: Drive Wave 6 — three Track Ω inventory / draft subsessions in
@@ -25,7 +25,7 @@
 > subagents pre-assigned M.1 / M.2 / M.3; each writes its own
 > `SESSION-M.<n>-TRANSCRIPT-…md` before returning a tight report to
 > the driver. Driver had to extend the publish script's filename +
-> header validators mid-session — Session L documented the §5
+> header validators mid-session — Session 0012.0 documented the §5
 > validator extension but never landed it in the script (Arc 7).
 > 14 §19.2 candidates surfaced across the three subs + driver.

@@ -34,10 +34,10 @@
 ## Pre-session state

 **Time**: opened 2026-05-28T05-26 PST (Thursday, just-pre-dawn —
-operator handed off the wheel after Session L's three-deploy
-Wave 5 finish at 05:17 PST and is sleeping). Session L's main
+operator handed off the wheel after Session 0012.0's three-deploy
+Wave 5 finish at 05:17 PST and is sleeping). Session 0012.0's main
 transcript is at
-`~/git/ohm-infra/SESSION-L-TRANSCRIPT-2026-05-28T04-22--2026-05-28T05-17.md`.
+`~/git/ohm-infra/SESSION-0012.0-TRANSCRIPT-2026-05-28T04-22--2026-05-28T05-17.md`.

 **Repos at session open:**

@@ -49,7 +49,7 @@ transcript is at
 | `ohm-infra` (`~/git/ohm-infra/`) | Plain directory (not a local git repo). Transcripts A–L published to `wiggleverse/ohm-session-history` via `scripts/publish-transcript.sh`. SESSION-PROTOCOL.md at the §5-amended version. |

 **OHM live state**: `ohm.wiggleverse.org` serves rfc-app v0.17.0,
-deploys.id=21 (last deploy from Session L). v0.13.0 cookie banner +
+deploys.id=21 (last deploy from Session 0012.0). v0.13.0 cookie banner +
 v0.14.0 /docs route + v0.15.0 Amplitude analytics & session replay +
 v0.16.0 per-RFC owner invites + v0.17.0 admin-create user invites
 all live in production for the first time. #21 Part C identity-
@@ -79,13 +79,13 @@ open:
  is <12 hours old)

 **Housekeeping noticed at open**:
- A stale `SESSION-L-TRANSCRIPT-2026-05-28T04-22--INPROGRESS.md`
-  (4.3 KB) sits next to Session L's final transcript at
+- A stale `SESSION-0012.0-TRANSCRIPT-2026-05-28T04-22--INPROGRESS.md`
+  (4.3 KB) sits next to Session 0012.0's final transcript at
  `~/git/ohm-infra/`. The final transcript is the load-bearing one
  (was published). The INPROGRESS placeholder is leftover.
  Recommend the operator delete it (or driver deletes at the end
-  of M); not load-bearing for Session M's work.
- Three rfc-app worktrees from Session L still on disk under
+  of M); not load-bearing for Session 0013.0's work.
+- Three rfc-app worktrees from Session 0012.0 still on disk under
  `~/git/`:
  - `rfc-app-v0.15.0-amplitude/`
  - `rfc-app-v0.16.0-owner-invite/`
@@ -148,7 +148,7 @@ explicitly rides #19's CONTRIBUTING PRs per the roadmap; #18 and
 #20 explicitly ship together because the same DNS edits serve both.

 Pre-state snapshot above. Then opened this transcript at
-`SESSION-M-TRANSCRIPT-2026-05-28T05-26--INPROGRESS.md` and
+`SESSION-0013.0-TRANSCRIPT-2026-05-28T05-26--INPROGRESS.md` and
 dispatched the three subagents in parallel at 2026-05-28T05-30 PST.

 Each subagent's dispatch prompt named:
@@ -175,7 +175,7 @@ they return. Cut-state table written after all three are in.
 ### Arc 2 — M.2 returns: #17 repo naming inventory

 M.2 completed at 2026-05-28T05-37 PST (~7 min). Full detail:
-`SESSION-M.2-TRANSCRIPT-2026-05-28T05-30--2026-05-28T05-37.md`.
+`SESSION-0013.2-TRANSCRIPT-2026-05-28T05-30--2026-05-28T05-37.md`.

 **Inventory totals:** 9 repos on `git.wiggleverse.org` (4 under
 `ben.stull/`, 5 under `wiggleverse/`); 3 on `git.benstull.org`
@@ -241,7 +241,7 @@ the load-bearing ones):

 **Artifacts written by M.2:**
 - `~/git/ohm-infra/REPO-NAMING-PROPOSAL.md` (~33 KB).
- `~/git/ohm-infra/SESSION-M.2-TRANSCRIPT-2026-05-28T05-30--2026-05-28T05-37.md`.
+- `~/git/ohm-infra/SESSION-0013.2-TRANSCRIPT-2026-05-28T05-30--2026-05-28T05-37.md`.

 Zero remote git operations. No Gitea admin actions. Clean
 inventory + proposal pass per scope.
@@ -249,7 +249,7 @@ inventory + proposal pass per scope.
 ### Arc 3 — M.3 returns: #20 + #18 deliverability & webhook hardening

 M.3 completed at 2026-05-28T05-58 PST (~28 min). Full detail:
-`SESSION-M.3-TRANSCRIPT-2026-05-28T05-30--2026-05-28T05-58.md`.
+`SESSION-0013.3-TRANSCRIPT-2026-05-28T05-30--2026-05-28T05-58.md`.

 **Load-bearing finding (top of operator's plate)**: `SMTP_HOST`
 and `SMTP_USER` are MISSING from the live flotilla overlay. Only
@@ -334,7 +334,7 @@ source), so M.3 couldn't self-check that one.
 **Artifacts written by M.3:**
 - `~/git/ohm-infra/EMAIL-AND-WEBHOOK-HARDENING-RUNBOOK.md` (~21 KB).
 - `~/git/ohm-infra/RFC-APP-EMAIL-HYGIENE-PROPOSAL.md` (~9 KB).
- `~/git/ohm-infra/SESSION-M.3-TRANSCRIPT-2026-05-28T05-30--2026-05-28T05-58.md`.
+- `~/git/ohm-infra/SESSION-0013.3-TRANSCRIPT-2026-05-28T05-30--2026-05-28T05-58.md`.

 Read-only DNS / flotilla-overlay / rfc-app code inventory. Zero
 DNS edits, zero overlay set, zero code commits. Clean per scope.
@@ -382,7 +382,7 @@ strict-descending CHANGELOG convention, RFC 2119 `Upgrade steps:`
 discipline, §19.2 candidate practice, test-coverage expectations
 characterized from the real ~250-test backend suite, the operator-
 only-gestures boundary (with the hard no-secret-bytes rule cited
-from Session K Arc 6), and the #21 Part B analytics-instrumentation
+from Session 0011.0 Arc 6), and the #21 Part B analytics-instrumentation
 checklist as a dedicated section. Worked-example links to Sessions
 E (clean small release), I (deploy-fault recovery), K (multi-feature
 wave + paused-on-secret), L (squash-merge across three parallel
@@ -450,7 +450,7 @@ First attempt to publish M.1 failed:
 `filename does not match SESSION-<letter>-TRANSCRIPT[-<start>--<end>].md`.
 Investigation revealed a **protocol-vs-reality discrepancy**: both
 the operator's brief ("the publish script's filename validator was
-extended in Session L to accept `SESSION-<letter>.<n>-TRANSCRIPT-…md`")
+extended in Session 0012.0 to accept `SESSION-<letter>.<n>-TRANSCRIPT-…md`")
 and SESSION-PROTOCOL.md §5.6 ("The publish script's filename
 validator accepts the `SESSION-<letter>.<n>-TRANSCRIPT-…md` form
 (extended Session-L, see `scripts/publish-transcript.sh`)") said
@@ -459,7 +459,7 @@ the extension was already in place — but the actual regex in
 `^SESSION-[A-Za-z]+-TRANSCRIPT(-${_TS}--${_TS})?\.md$`, and the
 header check at L140 only accepted `Transcript` / `transcript`
 endings, not `Subsession transcript`. The extension was documented
-in Session L's protocol amendment but never landed in the script.
+in Session 0012.0's protocol amendment but never landed in the script.

 Driver made minimal-scope edits to fix:
 - Filename regex: extended to `^SESSION-[A-Za-z]+(\.[0-9]+)*-TRANSCRIPT(-${_TS}--${_TS})?\.md$` (accepts `.N` and `.N.N` for hypothetical sub-subagents per §5.2's nested convention).
@@ -468,11 +468,11 @@ Driver made minimal-scope edits to fix:
 - Updated the error message at L128 to name `[.<n>]` explicitly.

 Dry-ran M.1 to verify both validators pass against
-`# Session M.1 — Subsession transcript`. Header OK. Then published
+`# Session 0013.1 — Subsession transcript`. Header OK. Then published
 M.1 → M.2 → M.3 → M serially.

 **Note on scope**: this script edit is in-scope plumbing for §5 being
-operational at all — Session M is the first session under §5, so the
+operational at all — Session 0013.0 is the first session under §5, so the
 validator gap had to be fixed before the wave could complete. The
 change is small (regex extensions + comment/message updates only,
 no logic changes), commented in the script, and the dry-run gesture
@@ -517,7 +517,7 @@ become Wave 7's plate.
 | `rfc-app` | `main` unchanged at `1456c8b` (Release 0.17.0). New branch `feature/contributing-and-spec-analytics` at `213f686` pushed to `origin` + `benstull` — awaiting operator PR review. Local tree on `main`, clean. |
 | `ohm-rfc` | `main` advanced from `47cb2f9` → `8cce148` mid-session (operator pushed #23). New branch `feature/contributing-roadmap-guide` at `f26fae4` pushed to `origin` — awaiting operator PR review. `.rfc-app-version` unchanged at `0.17.0`. Local tree on `main`, clean. |
 | `ohm-rfc-app-flotilla` | unchanged at `65c0e55`. v1.0.1. |
-| OHM live | unchanged from Session L cut — `deploys.id=21`, v0.17.0. No deploy gesture this session. |
+| OHM live | unchanged from Session 0012.0 cut — `deploys.id=21`, v0.17.0. No deploy gesture this session. |
 | `ohm-infra` (local dir) | 4 new files this session: this transcript + M.1/M.2/M.3 subsessions. Plus 2 inventory/runbook docs from M.2 (`REPO-NAMING-PROPOSAL.md`) and 2 from M.3 (`EMAIL-AND-WEBHOOK-HARDENING-RUNBOOK.md`, `RFC-APP-EMAIL-HYGIENE-PROPOSAL.md`). |

 | Wave 6 ledger | Status |
@@ -593,10 +593,10 @@ Driver-surfaced (this transcript):
    documented expectation that the driver always re-verifies
    deliverables on disk and doesn't depend on the report-back text
    alone.
-14. **Protocol amendments must land with the code change.** Session L
+14. **Protocol amendments must land with the code change.** Session 0012.0
    documented in SESSION-PROTOCOL.md §5.6 that the publish script's
    validator was extended to accept `SESSION-<letter>.<n>-TRANSCRIPT-…md`,
-    and the Session M brief repeated the claim. Reality at session
+    and the Session 0013.0 brief repeated the claim. Reality at session
    open: the script's regex hadn't been modified. Driver had to
    extend it mid-Session-M to publish the subsession transcripts at
    all (see Arc 7). Worth a discipline: an amendment to the
@@ -604,7 +604,7 @@ Driver-surfaced (this transcript):
    change in the same merge (or be marked "pending implementation"
    in the protocol text). Plus: amendment review should diff the
    protocol claim against the named code surface and reject if
-    they don't match. This is a Session M lesson; would land in
+    they don't match. This is a Session 0013.0 lesson; would land in
    SESSION-PROTOCOL.md §6 ("when the protocol is unclear") as a
    sub-paragraph.

@@ -630,7 +630,7 @@ In rough priority order (driver's read):

 2. **rfc-app PR** for `feature/contributing-and-spec-analytics` at
   `213f686`. Suggested PR description in
-   `SESSION-M.1-TRANSCRIPT-…md` What-the-driver-needs-to-know #6.
+   `SESSION-0013.1-TRANSCRIPT-…md` What-the-driver-needs-to-know #6.
   Open on:
   - `https://git.wiggleverse.org/ben.stull/rfc-app/pulls/new/feature/contributing-and-spec-analytics`
   - `https://git.benstull.org/benstull/rfc-app/pulls/new/feature/contributing-and-spec-analytics`
@@ -673,11 +673,11 @@ In rough priority order (driver's read):
   will name as `SESSION-NNNN.M` per the new spec.

 8. **Stale Session-L INPROGRESS file** at
-   `~/git/ohm-infra/SESSION-L-TRANSCRIPT-2026-05-28T04-22--INPROGRESS.md`
+   `~/git/ohm-infra/SESSION-0012.0-TRANSCRIPT-2026-05-28T04-22--INPROGRESS.md`
   (4.3 KB). Final L transcript is published; this is a placeholder
   that can be deleted. Driver did NOT delete (operator's call).

-9. **Three rfc-app worktrees from Session L** still on disk:
+9. **Three rfc-app worktrees from Session 0012.0** still on disk:
   `~/git/rfc-app-v0.15.0-amplitude/`, `~/git/rfc-app-v0.16.0-owner-invite/`,
   `~/git/rfc-app-v0.17.0-admin-create-user/`. All shipped + merged.
   Cleanup via `git worktree remove` at the operator's convenience.
@@ -688,7 +688,7 @@ In rough priority order (driver's read):

 11. **`scripts/publish-transcript.sh` was edited mid-session** to
    actually extend the filename + header validators for the §5
-    subsession form (Session L documented the extension but never
+    subsession form (Session 0012.0 documented the extension but never
    landed it). The script lives in `~/git/ohm-infra/` which is
    not version-controlled, so the change has no commit history.
    Driver-applied diff: regex `^SESSION-[A-Za-z]+-TRANSCRIPT…`
@@ -706,11 +706,11 @@ In rough priority order (driver's read):
 ## Prompt the operator can paste into the next Claude Code session

 ```
-You are the OHM roadmap driver. The previous session (Session M)
+You are the OHM roadmap driver. The previous session (Session 0013.0)
 ran Wave 6 as three Track Ω inventory/draft subsessions in parallel
 (M.1 / M.2 / M.3) under the new §5 subsession-transcript convention.

-**What Session M produced:**
+**What Session 0013.0 produced:**
 - Two docs feature branches awaiting your PR review:
  - rfc-app `feature/contributing-and-spec-analytics` at `213f686`
    (CONTRIBUTING.md + SPEC.md §21 analytics chapter, lands #19 +
@@ -741,7 +741,7 @@ flow.
 1. **Investigate + fix SMTP gap** (above) — possibly an ops-only
   gesture if systemd override is sufficient; possibly an rfc-app
   minor if the email-send code needs a defensive change.
-2. **Operator reviews + merges the two docs PRs from Session M**
+2. **Operator reviews + merges the two docs PRs from Session 0013.0**
   (no version bump for either; lands as no-bump docs commits).
 3. **rfc-app v0.18.0** — framework-side hardening from
   `RFC-APP-EMAIL-HYGIENE-PROPOSAL.md`: `build_envelope` shared
@@ -773,13 +773,13 @@ flow.
  flotilla secret set <deployment> <KEY>`). Public bundle-embedded
  values (VITE_AMPLITUDE_API_KEY, VITE_TURNSTILE_SITE_KEY) are fine
  in-conversation via `flotilla overlay set`.
- Subagent stream-watchdog stalls (Session M new): subagents
+- Subagent stream-watchdog stalls (Session 0013.0 new): subagents
  MUST write their transcript BEFORE returning a report (already
  in §5.3) — and SHOULD NOT add a "final sanity check" phase
  between transcript-write and report-back (where M.1 died).
  Driver should always re-verify deliverables on disk rather
  than depend on the report-back text alone.
- §5 subsession-transcript convention is binding from Session M
+- §5 subsession-transcript convention is binding from Session 0013.0
  onward.

 **Cut state at handoff:**
@@ -1,6 +1,6 @@
-# Session M.1 — Subsession transcript
+# Session 0013.1 — Subsession transcript

-> Parent: `SESSION-M-TRANSCRIPT-2026-05-28T05-26--<end>.md`
+> Parent: `SESSION-0013.0-TRANSCRIPT-2026-05-28T05-26--<end>.md`
 > Date: 2026-05-28
 > Goal: Draft `rfc-app/CONTRIBUTING.md`, the `rfc-app/SPEC.md` analytics chapter,
 > and the `ohm-rfc/CONTRIBUTING.md` roadmap-guide extension — landing roadmap
@@ -38,10 +38,10 @@
 - **ohm-rfc**: `main` at `8cce148`. `.rfc-app-version` = `0.17.0`.
  `CONTRIBUTING.md` existed (130 lines, RFC-content guide); no
  roadmap-change section.
- **ohm-infra (local)**: most recent transcripts Session L
-  (`SESSION-L-TRANSCRIPT-2026-05-28T04-22--2026-05-28T05-17.md`) +
-  Session M's main transcript in-progress
-  (`SESSION-M-TRANSCRIPT-2026-05-28T05-26--INPROGRESS.md`).
+- **ohm-infra (local)**: most recent transcripts Session 0012.0
+  (`SESSION-0012.0-TRANSCRIPT-2026-05-28T04-22--2026-05-28T05-17.md`) +
+  Session 0013.0's main transcript in-progress
+  (`SESSION-0013.0-TRANSCRIPT-2026-05-28T05-26--INPROGRESS.md`).
 - **Branches at start**: both repos on `main`, both clean working trees.

 ---
@@ -56,10 +56,10 @@ particularly Part B at L625-655 and Part C at L657-731);
 oriented, no roadmap-change section); `ohm-infra/SESSION-PROTOCOL.md`
 (§1 naming, §2 transcript shape, §5 subagent-transcript amendment —
 binding for this subsession);
-`ohm-infra/SESSION-K-TRANSCRIPT-…md` (whole file — clean-small-
+`ohm-infra/SESSION-0011.0-TRANSCRIPT-…md` (whole file — clean-small-
 release + multi-feature-wave + paused-on-secret patterns; the
 Arc-6 hard-rule incident around secret bytes);
-`ohm-infra/SESSION-L-TRANSCRIPT-…md` (whole file — squash-merge
+`ohm-infra/SESSION-0012.0-TRANSCRIPT-…md` (whole file — squash-merge
 integration with #21 Part C identity-lifecycle wiring folded inline
 across three releases; the addendum cycles around "transcript is the
 LAST step" discipline);
@@ -71,7 +71,7 @@ analytics chapter;
 entries (lines 1-413) for the strict-descending convention and
 RFC 2119 keyword usage examples;
 `rfc-app/frontend/src/lib/analytics.js` end-to-end (the v0.15.0
-wrapper extended in Session L with `{ user_id, properties }` identify
+wrapper extended in Session 0012.0 with `{ user_id, properties }` identify
 signature, `applyProperties` with `__setOnce__` sentinel,
 `setUserProperties`, anonymize-clears-cache);
 `rfc-app/frontend/src/App.jsx` lines 40-90 (the App-level identify
@@ -136,8 +136,8 @@ covering, in order:
  SHOULD / SHOULD NOT / MAY — with the cross-version-upgrade
  composition rule cited.
 - §19.2 candidate discipline — explicit "don't scope-creep, name
-  the deferral." Cited v0.11.0's three new candidates (Session K)
-  and v0.15.0's two (Session L) as worked examples.
+  the deferral." Cited v0.11.0's three new candidates (Session 0011.0)
+  and v0.15.0's two (Session 0012.0) as worked examples.
 - Test-coverage expectations characterized from the actual
  ~250-test backend suite. Named specific vertical files
  (`test_admin_create_user_invite_vertical.py`, etc.) and the
@@ -150,7 +150,7 @@ covering, in order:
  pointer to SPEC §21.6 identity-lifecycle contract for any new
  claim/sign-in/invite path.
 - Operator-only gestures explicitly enumerated, with the hard
-  no-secret-bytes-in-conversation rule named (Session K Arc 6
+  no-secret-bytes-in-conversation rule named (Session 0011.0 Arc 6
  origin cited).
 - "When in doubt" closer.

@@ -306,7 +306,7 @@ No tags, no VERSION bump, no `.rfc-app-version` pin move, no
 ### Arc 8 — Transcript

 Wrote this subsession transcript at
-`~/git/ohm-infra/SESSION-M.1-TRANSCRIPT-2026-05-28T05-30--2026-05-28T05-40.md`
+`~/git/ohm-infra/SESSION-0013.1-TRANSCRIPT-2026-05-28T05-30--2026-05-28T05-40.md`
 per the §5 subagent-transcript convention. Parent reference in the
 header. The driver publishes this alongside its own Session-M
 transcript via `~/git/ohm-infra/scripts/publish-transcript.sh`.
@@ -385,7 +385,7 @@ transcript via `~/git/ohm-infra/scripts/publish-transcript.sh`.
   - `https://git.wiggleverse.org/ben.stull/rfc-app/pulls/new/feature/contributing-and-spec-analytics`
   - `https://git.benstull.org/benstull/rfc-app/pulls/new/feature/contributing-and-spec-analytics`
     (the mirror; merge here too if the operator's release flow
-     normally syncs both — Session K/L precedent is that operator
+     normally syncs both — Session 0011.0/L precedent is that operator
     pushes tags to both but PR-opens on one and merges the merge-
     commit to both. The operator's call.)
   - `https://git.wiggleverse.org/ben.stull/ohm-rfc/pulls/new/feature/contributing-roadmap-guide`
@@ -456,5 +456,5 @@ transcript via `~/git/ohm-infra/scripts/publish-transcript.sh`.
 - `/Users/benstull/projects/wiggleverse/ohm-rfc/CONTRIBUTING.md`
  (modified — new "Proposing a change to the OHM roadmap"
  section appended after the License block)
- `/Users/benstull/git/ohm-infra/SESSION-M.1-TRANSCRIPT-2026-05-28T05-30--2026-05-28T05-40.md`
+- `/Users/benstull/git/ohm-infra/SESSION-0013.1-TRANSCRIPT-2026-05-28T05-30--2026-05-28T05-40.md`
  (this file)
@@ -1,12 +1,12 @@
-# Session M.2 — Transcript (subsession)
+# Session 0013.2 — Transcript (subsession)

-> Parent: SESSION-M-TRANSCRIPT-2026-05-28T05-26--INPROGRESS.md
+> Parent: SESSION-0013.0-TRANSCRIPT-2026-05-28T05-26--INPROGRESS.md
 > Date: 2026-05-28
 > Goal: Roadmap item #17 step 1 (inventory) + step 2 (propose) — survey every repo on `git.wiggleverse.org` and `git.benstull.org`, draft the move proposal as a single document for the operator to review. **Step 3 (execute) is explicitly out of scope.**
 >
 > Outcome: **`REPO-NAMING-PROPOSAL.md` written to `~/git/ohm-infra/`. 12 repos inventoried across the two hosts plus 9 local-only working dirs documented. 8 moves proposed (3 archives, 2 namespace transfers, 3 operator-decision items). 6 open questions surfaced. Zero git operations performed against any remote.**

-This is a subsession of Session M (the OHM driver session). The driver
+This is a subsession of Session 0013.0 (the OHM driver session). The driver
 dispatched M.2 with a tight read-only-inventory + single-deliverable
 brief. Subsession boundaries follow the OHM session protocol §1
 (letter+number scheme — M.2 is the second subsession of M).
@@ -29,7 +29,7 @@ The driver's hand-off named:
 - Hard constraint: no Gitea admin actions, no transfers, no edits to
  anything but the proposal document itself.

-Operator's working tree (parent session M's pre-state): clean.
+Operator's working tree (parent session 0013.0's pre-state): clean.
 Active OHM deployment: v0.17.0 (deploys.id=21). Pin: 0.17.0. Healthy.

 ---
@@ -190,7 +190,7 @@ the proposal doc itself.
 | Every other repo (local + remote) | untouched |
 | OHM live | unchanged (deploys.id=21, v0.17.0, healthy) |
 | flotilla SQLite registry | unchanged |
-| Parent session M state | unchanged |
+| Parent session 0013.0 state | unchanged |

 | M.2 deliverable ledger | Status |
 | --- | --- |
@@ -1,6 +1,6 @@
-# Session M.3 — Transcript
+# Session 0013.3 — Transcript

-> Parent: SESSION-M-TRANSCRIPT-2026-05-28T05-26--<end>.md
+> Parent: SESSION-0013.0-TRANSCRIPT-2026-05-28T05-26--<end>.md
 >
 > Date: 2026-05-28 (PST)
 > Start: 2026-05-28T05-30 PST
@@ -25,7 +25,7 @@

 ## Pre-session state

- Parent: Session M driver, dispatched M.3 with scope = inventory
+- Parent: Session 0013.0 driver, dispatched M.3 with scope = inventory
  for items #18 + #20.
 - `~/git/ohm-infra/` is a plain directory (not a git repo) — driver
  noted this; M.3 leaves docs on disk for the driver to handle
@@ -193,7 +193,7 @@ or just publish the transcripts via `publish-transcript.sh`.
 |---|---|
 | `~/git/ohm-infra/EMAIL-AND-WEBHOOK-HARDENING-RUNBOOK.md` | written, ~21 KB |
 | `~/git/ohm-infra/RFC-APP-EMAIL-HYGIENE-PROPOSAL.md` | written, ~9 KB |
-| `~/git/ohm-infra/SESSION-M.3-TRANSCRIPT-…md` | this file |
+| `~/git/ohm-infra/SESSION-0013.3-TRANSCRIPT-…md` | this file |
 | OHM live | unchanged (v0.17.0, deploys.id=21) |
 | DNS / Gitea / SMTP provider | unchanged (read-only inventory only) |
 | flotilla overlay / secrets | unchanged (read-only `show` + `list` only) |
@@ -308,4 +308,4 @@ stale `wiggleverse/meta` hook on a deprovisioned domain.
 **Doc paths:**
 - `/Users/benstull/git/ohm-infra/EMAIL-AND-WEBHOOK-HARDENING-RUNBOOK.md`
 - `/Users/benstull/git/ohm-infra/RFC-APP-EMAIL-HYGIENE-PROPOSAL.md`
- `/Users/benstull/git/ohm-infra/SESSION-M.3-TRANSCRIPT-2026-05-28T05-30--2026-05-28T05-58.md`
+- `/Users/benstull/git/ohm-infra/SESSION-0013.3-TRANSCRIPT-2026-05-28T05-30--2026-05-28T05-58.md`
@@ -491,7 +491,7 @@ sections accumulate these over time.)
 ```
 You are the OHM roadmap driver, Session 0015.0 (= the session that
 would have been labeled "Session O" under the legacy letter form).
-Session 0014.0 (Session N) executed a heavy Wave 7 + the #23
+Session 0014.0 (Session 0014.0) executed a heavy Wave 7 + the #23
 transcript rename — read this whole prompt before doing anything.

 # What Session 0014.0 shipped
@@ -516,8 +516,8 @@ show` or the deploy log):
   overlay keys to `npm run build`'s process.env so they reach
   Vite's `loadEnv()`. Pre-1.1.0 deploys shipped bundles with empty
   VITE_*, which silently disabled **Cloudflare Turnstile since
-   rfc-app v0.12.0** (Session K) and **Amplitude analytics +
-   session replay since rfc-app v0.15.0** (Session L). Both were
+   rfc-app v0.12.0** (Session 0011.0) and **Amplitude analytics +
+   session replay since rfc-app v0.15.0** (Session 0012.0). Both were
   confirmed broken by curl'ing the deployed bundle and grepping
   for the expected key strings (neither was present) — fixed via
   bundle re-grep (both now in the v0.18.0 bundle at
@@ -666,7 +666,7 @@ a. **flotilla: per-deployment "expected VITE_* keys" manifest +
   keys" candidate — these may be the same item.

 b. **flotilla: SSE-keepalive SIGTERM holding past 60s SSH watchdog
-   timeout.** Session I noted it (§19.2); hit 3× more this session
+   timeout.** Session 0009.0 noted it (§19.2); hit 3× more this session
   (deploy rows 23, 24, 25 all aborted-but-healthy). The watchdog
   timeout doesn't reflect the actual restart success. A flotilla
   minor (v1.2.0?) that pre-drains SSE connections before
@@ -676,7 +676,7 @@ c. **rfc-app: framework should accept an `EMAIL_HELO_DOMAIN` env
   override** (or auto-derive from EMAIL_FROM's domain) and pass
   `local_hostname=` to `smtplib.SMTP()`. Without this, the
   IP-allowlist-only SMTP relay path isn't viable for any
-   deployment — only SMTP AUTH paths work. Path C in the Session N
+   deployment — only SMTP AUTH paths work. Path C in the Session 0014.0
   triage couldn't proceed without a framework change.

 d. **flotilla / framework: .env quote-stripping inconsistency.**
@@ -1,6 +1,6 @@
-# Session N.1 — Transcript
+# Session 0014.1 — Transcript

-> Parent: SESSION-N-TRANSCRIPT-2026-05-28T07-01--<end>.md
+> Parent: SESSION-0014.0-TRANSCRIPT-2026-05-28T07-01--<end>.md
 > Date: 2026-05-28 (PST)
 > Start: 2026-05-28T07-08 PST
 > End:   2026-05-28T07-40 PST
@@ -346,6 +346,6 @@ lesson + §5 of the protocol.
  failures. Driver N may want to either rename the remotes or
  update the prompt template.
 - **Subsession transcript:** this file, at
-  `~/git/ohm-infra/SESSION-N.1-TRANSCRIPT-2026-05-28T07-08--2026-05-28T07-40.md`.
+  `~/git/ohm-infra/SESSION-0014.1-TRANSCRIPT-2026-05-28T07-08--2026-05-28T07-40.md`.
  Driver N publishes this via `publish-transcript.sh` alongside
  the parent session transcript.
@@ -21,7 +21,7 @@
 - ohm-rfc `main` @ `74a3e12` ("ROADMAP: +#24..#29"); pin `.rfc-app-version=0.18.0`. (Between session start and the post-deploy pin push, the operator landed at least one more commit on ohm-rfc — `9c47792` — adding roadmap item #30 with its **NEXT** marker; my pin-bump committed onto the updated `9c47792` cleanly.)
 - ohm-rfc-app-flotilla `main` @ `417b6c5` (v1.1.0, Wave 7 deploy with VITE_* overlay propagation). Local working tree had one modified file: `CLAUDE.md`.
 - OHM live: v0.18.0 healthy (`/api/health` 200, `{"version":"0.18.0","status":"ok"}`).
- ohm-infra (`~/git/ohm-infra/`, not a git repo locally): `publish-transcript.sh` at the post-#23 form (accepting numeric + legacy letter regex); `SESSION-PROTOCOL.md` at the post-Session-0014.0 amendment shape. Stale `SESSION-L-TRANSCRIPT-…INPROGRESS.md` still on disk (handoff said leave as-is).
+- ohm-infra (`~/git/ohm-infra/`, not a git repo locally): `publish-transcript.sh` at the post-#23 form (accepting numeric + legacy letter regex); `SESSION-PROTOCOL.md` at the post-Session-0014.0 amendment shape. Stale `SESSION-0012.0-TRANSCRIPT-…INPROGRESS.md` still on disk (handoff said leave as-is).
 - Session 0014.0's main driver transcript NOT yet on disk at session start (it appeared at 08:43 mid-session — the parallel-running driver was finalizing). 0014.1 subagent transcript was on disk from 07:42. 0016.0 transcript not seen on disk this session.

 The operator's handoff prompt (pasted at session start) was the load-bearing summary of what Wave 7 shipped + the Wave 8 candidate list. Two clarifying gates the operator surfaced at the top:
@@ -144,7 +144,7 @@ With both subagents returned and verified, executed the coordinated landing:
 4. `git push benstull main v0.19.0` → success.
 5. `cd ohm-rfc && echo "0.19.0" > .rfc-app-version && git commit -m "Pin rfc-app 0.19.0 — Wave 8 deploy: /docs nav + on-site sessions browser (#30)"` → commit `de17e79`. (Local main was at `9c47792`, not `74a3e12` as seen at session start — operator landed at least one more ohm-rfc commit in between; commit graph stayed clean.)
 6. `git push` → success.
-7. `.venv/bin/ohm-rfc-app-flotilla deploy ohm-rfc-app` → **hit the §19.2 SSE-keepalive SSH-watchdog timeout** at phase 7 (`SshError: ssh to ohm-app timed out after 60.0s running: 'sudo sh -c ... systemctl restart ohm-app.service ...'`). 4th occurrence of this pattern (Session I §19.2 / Session 0014.0 carry-forward).
+7. `.venv/bin/ohm-rfc-app-flotilla deploy ohm-rfc-app` → **hit the §19.2 SSE-keepalive SSH-watchdog timeout** at phase 7 (`SshError: ssh to ohm-app timed out after 60.0s running: 'sudo sh -c ... systemctl restart ohm-app.service ...'`). 4th occurrence of this pattern (Session 0009.0 §19.2 / Session 0014.0 carry-forward).
 8. **Verification via `/api/health`** (not the flotilla exit code, per Session 0014.0's lesson): first probe right after the timeout returned 502 from nginx (service was mid-restart); second probe 15s later also 502; but then `.venv/bin/ohm-rfc-app-flotilla deploy status ohm-rfc-app` returned `HTTP 200 version=0.19.0 status=ok`. Re-probed the public URL — 5 consecutive 200s, all `{"version":"0.19.0","status":"ok"}`, ~190 ms each. So: deploy succeeded; the 502 window was transient (a few seconds while the service was finishing restart); SSH watchdog falling off doesn't reflect actual deploy outcome.

 (Side observation: an `ssh ohm-app` attempt to read journalctl failed "Could not resolve hostname ohm-app" — my local SSH config doesn't have the alias the flotilla CLI uses internally. `flotilla deploy status` was the canonical path anyway. Not blocking.)
@@ -263,7 +263,7 @@ end-to-end at session start. Three parallel subagents:
   (one atomic commit `ad01c08` on `main`, fast-forward push). 19
   transcripts `git mv`'d into 15 `NNNN/` folders (rename detection
   100%); `0013/` holds 4 transcripts (driver + 3 subagents from
-   Session M); `0014/` holds 2 (driver + 1 subagent). Top-level
+   Session 0013.0); `0014/` holds 2 (driver + 1 subagent). Top-level
   `README.md` rewritten with 3 `<!-- operator: rewrite this section
   in your voice -->` markers (sections: "How OHM gets built", "Why
   transcripts are public" — which includes the verbatim
@@ -328,8 +328,8 @@ end-to-end at session start. Three parallel subagents:
    (one of the §19.2 candidates is to verify this; if they're
    visible as raw text, that's a markdown-renderer bug to fix).
  - `https://ohm.wiggleverse.org/docs/sessions/0009` → session index
-    page for Session I (the multi-wave driver). Should show
-    "Session I — multi-wave driver (rfc-app v0.4–v0.13, skipping
+    page for Session 0009.0 (the multi-wave driver). Should show
+    "Session 0009.0 — multi-wave driver (rfc-app v0.4–v0.13, skipping
    vacants)" as the title from sessions.json.
  - `https://ohm.wiggleverse.org/docs/sessions/0013` → should show
    4 transcripts (driver + 3 subagents) and resolve the right list
@@ -22,8 +22,8 @@ Repo was fully flat — root contents:
    (`0013.1`, `0013.2`, `0013.3`) and 1 in the `0014/` cohort
    (`0014.1`)

-No legacy letter-form transcripts (`SESSION-A-TRANSCRIPT-…`,
-`SESSION-M.1-TRANSCRIPT-…`, etc.) at root — Session 0014.0 / roadmap
+No legacy letter-form transcripts (`SESSION-0001.0-TRANSCRIPT-…`,
+`SESSION-0013.1-TRANSCRIPT-…`, etc.) at root — Session 0014.0 / roadmap
 #23 already renamed all of them in commit `1afa9f5`.

 ## Turn-by-turn arc
@@ -66,19 +66,19 @@ Drafted titles (operator review needed — these are starter sketches):

 ```
 0001: "Bootstrap — git.benstull.org personal Gitea on GCP"
-0002: "Session B — first OHM deployment (ohm.wiggleverse.org from zero)"
-0003: "Session C — rfc-app 0.3.0 release + OHM upgrade (allowlist + anon read)"
-0004: "Session D — flotilla SPEC + rfc.wiggleverse.org deprovision"
-0005: "Session E — flotilla Slices 1 & 2 (registry + overlay; secret refs)"
-0006: "Session F — flotilla Slice 3 (pin reading + deploy --dry-run, v0.3.0)"
-0007: "Session G — flotilla Slice 4 (full deploy gesture + health probe, v0.4.0)"
-0008: "Session H — flotilla v1.0.0 + first real OHM upgrade via flotilla"
-0009: "Session I — multi-wave driver (rfc-app v0.4–v0.13, skipping vacants)"
-0010: "Session J — DOCS.md + /docs route (rfc-app v0.14.0)"
-0011: "Session K — Wave 4 (admin /users, device trust, CloudFlare Turnstile)"
-0012: "Session L — Wave 5 (Amplitude, owner-invite, admin-create)"
-0013: "Session M — Wave 6 (CONTRIBUTING + SPEC §21 analytics; repo-naming; email/webhook runbook)"
-0014: "Session N — Wave 7 driver (SMTP + webhook hardening, #23 transcript rename)"
+0002: "Session 0002.0 — first OHM deployment (ohm.wiggleverse.org from zero)"
+0003: "Session 0003.0 — rfc-app 0.3.0 release + OHM upgrade (allowlist + anon read)"
+0004: "Session 0004.0 — flotilla SPEC + rfc.wiggleverse.org deprovision"
+0005: "Session 0005.0 — flotilla Slices 1 & 2 (registry + overlay; secret refs)"
+0006: "Session 0006.0 — flotilla Slice 3 (pin reading + deploy --dry-run, v0.3.0)"
+0007: "Session 0007.0 — flotilla Slice 4 (full deploy gesture + health probe, v0.4.0)"
+0008: "Session 0008.0 — flotilla v1.0.0 + first real OHM upgrade via flotilla"
+0009: "Session 0009.0 — multi-wave driver (rfc-app v0.4–v0.13, skipping vacants)"
+0010: "Session 0010.0 — DOCS.md + /docs route (rfc-app v0.14.0)"
+0011: "Session 0011.0 — Wave 4 (admin /users, device trust, CloudFlare Turnstile)"
+0012: "Session 0012.0 — Wave 5 (Amplitude, owner-invite, admin-create)"
+0013: "Session 0013.0 — Wave 6 (CONTRIBUTING + SPEC §21 analytics; repo-naming; email/webhook runbook)"
+0014: "Session 0014.0 — Wave 7 driver (SMTP + webhook hardening, #23 transcript rename)"
 0015: "Roadmap-capture parallel session (items #24–#30 added to ROADMAP.md)"
 ```

@@ -215,8 +215,8 @@ next operator-attention session):
  encodes the letter via the legacy mapping); the work-summary alone
  may read cleaner in the nav. Or operator may prefer the prefix as
  a chronology hook.
- **0013**: "Session M — Wave 6 (CONTRIBUTING + SPEC §21 analytics;
-  repo-naming; email/webhook runbook)" — Session M dispatched three
+- **0013**: "Session 0013.0 — Wave 6 (CONTRIBUTING + SPEC §21 analytics;
+  repo-naming; email/webhook runbook)" — Session 0013.0 dispatched three
  subagents whose work spans three distinct workstreams. The
  semicolon-list format may not be ideal; consider a one-phrase
  framing like "Track Ω inventory wave (#17, #18, #19, #20, #21)".
@@ -12,6 +12,29 @@ There is no GitHub mirror. The same content is rendered on-site at
 [`ohm.wiggleverse.org/docs/sessions`](https://ohm.wiggleverse.org/docs/sessions)
 (live from rfc-app v0.19.0+).

+<!-- operator: rewrite this section in your voice -->
+## Where the record begins
+
+OHM started with two vibe-coded prototypes — exploratory passes the
+operator built to figure out what the project wanted to be. Neither
+prototype produced a session transcript; the discipline that produced
+this record didn't exist yet, and the work was more "what does this
+even feel like to use" than "ship a deployable version."
+
+The first draft of the framework spec
+([`rfc-app/SPEC.md`](https://git.wiggleverse.org/ben.stull/rfc-app/src/branch/main/SPEC.md))
+was written off what those prototypes had taught the operator. From
+that draft onward, the build switched to spec-driven development:
+every session reads the spec, advances one feature, lands on OHM, and
+records what happened. The transcripts here start at that point — not
+at the very beginning of OHM's existence, but at the beginning of
+OHM-as-spec-driven-work.
+
+The two vibe-coded prototypes are not represented here. If you're
+trying to understand how OHM thinks, the spec is the primary text;
+the transcripts are the day-to-day record of how the spec gets
+extended in use.
+
 <!-- operator: rewrite this section in your voice -->
 ## How OHM gets built

@@ -108,11 +131,14 @@ Sessions 0001 through 0013 originally shipped under a letter-form
 naming (`SESSION-A` through `SESSION-M`). Roadmap item #23 (executed
 in session 0014.0) renamed every file to the zero-padded numeric
 form via `git mv` so the audit trail shows file-was-renamed rather
-than file-was-deleted-and-recreated. Transcript bodies still read
-"Session I" / "Session M.1" / etc. internally; that's deliberate —
-the rename is filename-level only, not a rewrite. The mapping table
-is in `SESSION-PROTOCOL.md` §1 (legacy form table) on the
-private-but-referenced `ohm-infra` working repo.
+than file-was-deleted-and-recreated. Initially the file-level rename
+was filename-only — the bodies still read "Session I" / "Session M.1"
+internally — but session 0018.0 also rewrote the bodies to use the
+numeric form throughout, so cross-references inside a transcript
+match the filename you'd browse to. The legacy mapping table
+(`A → 0001`, …, `N → 0014`) lives in `SESSION-PROTOCOL.md` §1 on
+the private-but-referenced `ohm-infra` working repo, in case you
+encounter a stray legacy reference in older external links.

 ## How transcripts get added