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
@@ -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)".