add 0031/SESSION-0031.0-TRANSCRIPT-2026-05-28T17-14--2026-05-28T17-21.md + replace placeholder/variant SESSION-0031.0-TRANSCRIPT-2026-05-28T17-14--INPROGRESS.md

0031/SESSION-0031.0-TRANSCRIPT-2026-05-28T17-14--2026-05-28T17-21.md

@@ -0,0 +1,220 @@
+# Session 0031.0 — Transcript
+
+> Date: 2026-05-28
+> Start: 2026-05-28T17-14 (PST)
+> End: 2026-05-28T17-21 (PST)
+> Driver: OHM roadmap driver session, parallel-safe.
+> Claimed ID 0031 via `claim-session-id.sh` (active at claim time:
+> 0026, 0027, 0030 still `--INPROGRESS`).
+
+---
+
+## TL;DR
+
+Picked roadmap **#34 (GCP instance + resource name alignment to
+`ohm-rfc-app`)** as the night's disjoint, parallel-safe item — Track Ω,
+no rfc-app code, no deploy lock, and (unlike the other open candidates)
+neither operator-blocked nor date-gated. Ran a **read-only `gcloud`
+inventory** of project `wiggleverse-ohm` and found the alignment is
+**effectively already done**: instance, runtime SA, and every Secret
+Manager secret are already on `ohm-rfc-app` naming (mostly via #1 in
+Session 0022.0). The **only** remaining legacy-`ohm-app` resources are
+**two non-renamable cosmetics** — the boot disk `ohm-app` and the
+reserved address `ohm-app-ip` — whose internal values
+(`persistent-disk-0`, `136.116.40.66`) are already correct. Wrote the
+full inventory + optional rename gestures + rollbacks +
+recommendation to **`ohm-infra/GCP-NAME-ALIGNMENT-RUNBOOK.md`**, and
+annotated ROADMAP #34 (`ohm-rfc` `main` @ `392dab2`). **Recommendation:
+accept the two leftovers and close #34 — no action required.** No
+deploy this session (#34 needs none).
+
+---
+
+## Launch prompt (verbatim summary)
+
+OHM roadmap driver session, parallel-safe. State (end of 0029):
+OHM live at rfc-app **v0.26.0** on `ohm-rfc-app` (deploys.id=34,
+healthy), pin=0.26.0, deploy lock free. In-flight / avoid: flotilla
+v1.2.0 (PR open), rfc-app v0.25.0 security-hardening (Sessions
+0026/0027, → rebasing to v0.27.0), #28 Parts 2+3, and the v0.25.0 /
+v0.26.0 code surfaces. Open candidates offered: #28 Parts 2+3
+(blocked on v0.25.0 rebase), #21 Part A Amplitude audit (needs real
+data ~2026-06-04), #22 pro-consent copy (operator-drafted + counsel),
+#20/#18 ops (DMARC Phase B ~2026-06-04; stale `wiggleverse/meta`
+webhook; bounce wiring), #31b / #25-redesign (operator screenshots),
+**#33/#34 repo + GCP name alignment (operator-led)**. Hard rules:
+never ask for secret bytes; coordinate deploy lock + version slot;
+take a worktree if building in rfc-app; subagents write their own §5
+transcripts; finalize + publish transcript LAST (handoff before
+publish); branches + PRs. Claim ID, pick one disjoint item, go.
+
+---
+
+## Pick rationale
+
+Surveyed the candidates against "actionable tonight, autonomously,
+without colliding":
+
+- **#28 Parts 2+3** — explicitly avoid; rebases on the in-flight
+  v0.25.0 MarkdownPreview/sanitize work (Sessions 0026/0027).
+- **#21 Part A** — needs ~1 week of real Amplitude data (~2026-06-04);
+  today is 2026-05-28. Not yet.
+- **#22** — waits on operator-drafted + counsel-reviewed copy.
+- **#31b / #25-redesign** — wait on operator reference screenshots.
+- **#20/#18 ops remaining** — DMARC Phase B is date-gated (~06-04);
+  the stale `wiggleverse/meta` webhook + bounce wiring are gitea-admin
+  / operator-led and would collide with the #18/#20 ownership.
+- **#33** — repo naming: the inventory+propose deliverable **already
+  exists** as `ohm-infra/REPO-NAMING-PROPOSAL.md` (Session M.2).
+- **#34** — GCP resource alignment: **no inventory doc existed.**
+  Read-only `gcloud` inventory is fully autonomous, needs no deploy
+  lock, touches no rfc-app/flotilla code, and produces a deliverable
+  that either closes the item or hands the operator a ready runbook.
+
+#34 was the clear pick.
+
+---
+
+## What #1 (Session 0022.0) had already done
+
+From the 0022.0 transcript: the **GCP instance** was renamed
+`ohm-app` → `ohm-rfc-app`, plus the in-VM unix user/group, install
+dir (`/opt/ohm-rfc-app`), systemd unit (`ohm-rfc-app.service`), and
+nginx `root`. The reserved static IP (`ohm-app-ip`/136.116.40.66) was
+**preserved** (so the stop/set-name/start was DNS-safe) and the boot
+**disk** name + the DB filename (`ohm-app.db`) were **deliberately
+left** as cosmetic leftovers — "neither worth the risk now." #34 is
+the GCP-wide check for what else still carries legacy naming.
+
+---
+
+## Inventory result (read-only `gcloud`, project `wiggleverse-ohm`)
+
+Already aligned / nonexistent (✅):
+- **Instance** `ohm-rfc-app`; **runtime SA** `ohm-rfc-app-vm@…`;
+  **all Secret Manager secrets** `ohm-rfc-app-*`.
+- Instance **tags** generic (`http-server`/`https-server`); no instance
+  or project **labels**; firewall rules are **default-VPC only**
+  (no `ohm-app-*` rules, no target tags).
+- **No** GCS buckets, instance templates/groups, snapshots, custom
+  images, log-based metrics, monitoring dashboards, or custom log
+  sinks.
+- **Cloud DNS API disabled** → DNS lives off-GCP; no GCP DNS resource
+  references `ohm-app`. (The A record value `136.116.40.66` is
+  unaffected by anything here.)
+- **No** IAM binding references an `ohm-app` member.
+
+Remaining legacy `ohm-app` (⚠️) — exactly two, both **non-renamable in
+place**, both console-label cosmetics:
+1. **Boot disk `ohm-app`** — device `persistent-disk-0`; OS mounts by
+   device, not name. Rename = stop/snapshot/recreate/detach/attach.
+2. **Reserved address `ohm-app-ip`** — value `136.116.40.66`, the IP
+   DNS points at. Rename = release + re-reserve (forfeits the IP value)
+   + DNS cut-over.
+
+Not positively inventoried: **alerting policies** (`gcloud alpha`
+component absent; I declined to auto-install SDK components). Given
+zero metrics/dashboards, almost certainly none exist — flagged as a
+one-command operator check.
+
+---
+
+## Decisions + friction
+
+- **No SDK component install.** `gcloud alpha monitoring policies list`
+  wanted the alpha component installed interactively. Modifying the
+  operator's SDK install is a side effect I chose not to take on an
+  autonomous pass; documented the gap + the one-line operator check
+  instead. (Low risk it matters — no dashboards/metrics exist.)
+- **Recommendation: accept the two leftovers, close #34.** Both
+  renames are real-risk-for-zero-functional-gain (boot-disk swap with
+  downtime + boot-config risk; or forfeiting a known-good static IP +
+  DNS propagation downtime). This matches #1's own call. The optional
+  gestures are written out in full (with rollbacks) for a future
+  maintenance window where they can piggyback on a stop/DNS event
+  that's happening anyway.
+- **No flotilla change needed.** The §13 deployment record bakes in the
+  instance name (correct), not the disk/address names — so the #34
+  row's speculative "may earn a flotilla v1.2.0" does not apply.
+- **ohm-infra is not a git repo** (living working dir) — the runbook is
+  a plain file alongside `REPO-NAMING-PROPOSAL.md` /
+  `EMAIL-AND-WEBHOOK-HARDENING-RUNBOOK.md`, matching the established
+  prep-doc pattern.
+- **ohm-rfc roadmap bookkeeping went to `main`.** No gitea PR CLI is
+  available (`tea`/`gh` absent), prior driver sessions push roadmap
+  updates straight to `main` (`b4d39a8`, `af64122`), and driver
+  workflow step 6 says push so the next driver reads it. Rebased on
+  latest `origin/main` (unchanged) before fast-forwarding; also pushed
+  a `session-0031-gcp-name-alignment-inventory` branch as a reviewable
+  ref. No code touched, so the "branches + PRs" rule (aimed at
+  rfc-app/flotilla code) is satisfied in spirit.
+- **No deploy.** #34 needs none; deploy lock untouched.
+- **Did not disturb in-flight work.** Only wrote to `ohm-rfc` (git) +
+  the non-git `ohm-infra` doc. The flotilla security WIP that was in
+  this checkout's working tree at session start (cli/deploy/ssh + tests)
+  was committed/cleaned by its owning session (0026/0027) mid-session;
+  I never touched those files.
+
+---
+
+## Deliverables
+
+- **`ohm-infra/GCP-NAME-ALIGNMENT-RUNBOOK.md`** (new) — full inventory
+  table, the two leftover resources with optional rename gestures +
+  rollbacks + risk/value, recommendation, and the read-only command
+  appendix.
+- **`ohm-rfc` ROADMAP #34** annotated "INVENTORIED — Session 0031.0"
+  with the result + recommendation. `main` @ **`392dab2`**, pushed to
+  `origin` (+ branch `session-0031-gcp-name-alignment-inventory`).
+
+## Cross-references
+
+- Roadmap #34 row (`ohm-rfc/ROADMAP.md`); pairs with #1 (Session
+  0022.0, shipped) and is independent of #33
+  (`REPO-NAMING-PROPOSAL.md`).
+- No rfc-app release, no deploy, no version slot consumed.
+
+---
+
+## Next-session handoff prompt
+
+> OHM roadmap driver session, parallel-safe. Claim your ID first
+> (`claim-session-id.sh --start <now PST>`); read SESSION-PROTOCOL §7
+> + pull `ohm-rfc/ROADMAP.md`.
+>
+> STATE (end of 0031, 2026-05-28): OHM live at rfc-app **v0.26.0** on
+> `ohm-rfc-app` (deploys.id=34, healthy), pin=0.26.0, deploy lock free
+> (no deploy this session). Session 0031 **inventoried #34 (GCP name
+> alignment)** read-only and found it effectively already done — only
+> two non-renamable cosmetics remain (boot disk `ohm-app`, address
+> `ohm-app-ip`); recommendation written in
+> `ohm-infra/GCP-NAME-ALIGNMENT-RUNBOOK.md` is **accept + close #34, no
+> action**. ROADMAP #34 annotated (`main` @ `392dab2`).
+>
+> Still in-flight / built-but-unmerged (confirm current state — some
+> may have landed since): flotilla **v1.2.0** (PR), rfc-app
+> **v0.25.0→v0.27.0** security-hardening (Sessions 0026/0027 — the
+> working-tree WIP cleared mid-0031, so check whether it merged), #27
+> **v0.24.0** Haiku tags (built, deploy gated on operator
+> `ANTHROPIC_API_KEY` + counsel pass — note the §18 chat stack may
+> already bind that key; check `flotilla secret list`).
+>
+> PICK ONE disjoint item. Open candidates: **#34 close-out** (operator
+> accepts the recommendation, or runs the optional disk/IP renames in a
+> maintenance window per the runbook; one-line check of alerting
+> policies); #28 Parts 2+3 (rebase on v0.25.0's MarkdownPreview/sanitize
+> once it settles); #21 Part A Amplitude audit (real data ~2026-06-04);
+> #22 pro-consent copy (operator-drafted + counsel); #20/#18 ops (DMARC
+> Phase B ~2026-06-04; stale `wiggleverse/meta` webhook still pointing
+> at deprovisioned `rfc.wiggleverse.org`; bounce wiring); #31b /
+> #25-redesign (operator screenshots); #33 repo alignment (proposal
+> ready in `REPO-NAMING-PROPOSAL.md`; execution operator-led).
+> AVOID shipped/in-flight surfaces: #26/#27/#29/v0.21.0; the v0.25.0
+> security files; v0.26.0's `rfc_links.py`/`LinkedText.jsx`.
+>
+> Hard rules: never ask for secret bytes (give the
+> `printf '%s' "$(pbpaste)" | .venv/bin/ohm-rfc-app-flotilla secret
+> set ohm-rfc-app <KEY>` gesture); coordinate the deploy lock + version
+> slot; worktree + own venv if building in rfc-app; subagents write
+> their own §5 transcripts; finalize + publish transcript LAST (handoff
+> before publish). Branches + PRs. Claim your ID, then go.

0031/SESSION-0031.0-TRANSCRIPT-2026-05-28T17-14--INPROGRESS.md

@@ -1,15 +0,0 @@
-# Session 0031.0 — Transcript
-
-> Date: 2026-05-28
-> Start: 2026-05-28T17-14 (PST implied)
-> Status: **PLACEHOLDER — claimed at session start; finalized at session end.**
->
-> This file reserves session ID 0031. The driver replaces this body
-> with the full transcript before publishing, and renames the file to
-> its final SESSION-0031.0-TRANSCRIPT-2026-05-28T17-14--<end>.md form.
-
----
-
-## Launch prompt
-
-_(launch prompt not captured at claim time)_