session-history/0043/SESSION-0043.0-TRANSCRIPT-2026-05-29T07-26--INPROGRESS.md

Session 0043.0 — Transcript

Date: 2026-05-29 Start: 2026-05-29T07-26 (PST implied) Status: PLACEHOLDER — claimed at session start; finalized at session end.

This file reserves session ID 0043. The driver replaces this body with the full transcript before publishing, and renames the file to its final SESSION-0043.0-TRANSCRIPT-2026-05-29T07-26--.md form.

---

Launch prompt

OHM driver session. Reserve your own session ID first.

GOAL: ROADMAP #33 — rename the RFC content repository
wiggleverse/ohm-meta → wiggleverse/ohm-content. The meta-only topology
(#36, rfc-app v0.31.0, session 0041.0) made this repo the single
canonical home of every RFC, so "meta" is now a misnomer and "content"
tells a cleaner deployer story. This is an OPERATIONAL/config move — the
framework references the repo by the config-driven META_REPO name, so
NO rfc-app code change is needed. (SPEC §1 already carries the
"<deployment>-content" framing as of v0.31.0.)

PRE-STATE (confirm before touching anything):
- OHM live: rfc-app v0.31.0 (deploys.id=45), meta-only.
- RFC-0001 `human` is folded back: ohm-meta/rfcs/human.md has repo:null
  + the full body; wiggleverse/rfc-0001-human is archived. Catalog:
  human (active, repo None) + informed-consent (super-draft).
- Live META_REPO overlay = "ohm-meta"; gitea org = "wiggleverse".
- A parallel session (0042) was doing PHILOSOPHY work on ohm-rfc branch
  philosophy/concept-not-word — make sure it's done / not mid-flight on
  the content repo before renaming.

THE MOVE (do in order, verify each):
1. Rename gitea repo: PATCH /repos/wiggleverse/ohm-meta {"name":
   "ohm-content"} (via the #35 authoring lane `api` verb, or repo
   Settings). Gitea preserves attached webhooks across a rename and
   leaves an old-name redirect — confirm both.
2. flotilla overlay set ohm-rfc-app META_REPO=ohm-content
3. Update flotilla's webhook EXPECTATION in the §13 deployment record
   then `flotilla webhook check --org` to confirm.
4. Re-point the VM's meta-content checkout origin remote + pull.
5. flotilla deploy ohm-rfc-app, then verify health + catalog + reconciler.
6. Sweep doc references "ohm-meta" → "ohm-content".

GOTCHAS:
- Do NOT rename ben/ohm-rfc — that's the DEPLOYMENT content repo.
- Authoring-lane token is write:repository (can PATCH repo + PRs, no comment).