wiggleverse/session-history
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source 
- 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>
This commit is contained in:
Ben Stull
2026-05-28 09:40:06 -07:00
parent 412b6ab5d8
commit d5125190ae
21 changed files with 281 additions and 255 deletions
Download Patch File Download Diff File Expand all files Collapse all files
0006/SESSION-0006.0-TRANSCRIPT-2026-05-27T19-00--2026-05-27T19-21.md
+8 -8
View File
@@ -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`.
---