add 0031/SESSION-0031.0-TRANSCRIPT-2026-05-28T17-14--2026-05-28T19-42.md + replace placeholder/variant SESSION-0031.0-TRANSCRIPT-2026-05-28T17-14--2026-05-28T18-51.md

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

@@ -2,8 +2,9 @@
 
 > Date: 2026-05-28
 > Start: 2026-05-28T17-14 (PST)
-> End: 2026-05-28T18-51 (PST) — re-finalized after a second work item
->   (flotilla v1.2.0 merge) + post-merge cleanup landed post-publish.
+> End: 2026-05-28T19-42 (PST) — re-finalized after flotilla v1.2.0
+>   merge + cleanup + a refreshed next-session handoff (live state moved
+>   to v0.27.0; recommendation set to #28 Parts 2+3).
 > Driver: OHM roadmap driver session, parallel-safe.
 > Claimed ID 0031 via `claim-session-id.sh` (active at claim time:
 > 0026, 0027, 0030 still `--INPROGRESS`).
@@ -247,44 +248,61 @@ what caught the silent stomp before anything was pushed.
 
 ## 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`.
+> OHM roadmap driver session, parallel-safe. Claim your ID first:
+> `~/git/ohm-infra/scripts/claim-session-id.sh --start <now PST,
+> YYYY-MM-DDTHH-MM>`. It prints active `--INPROGRESS` sessions —
+> **coordinate**. At 0031's close, **0032** was actively running
+> (started 18-52) doing **SSH/IAP hardening** (the VM now accepts SSH
+> only via IAP — ops/infra, disjoint from rfc-app feature work, so a
+> #28 session won't collide); **0026/0027** are stale placeholders
+> (their security work already shipped as v0.27.0 — ignore). Read
+> SESSION-PROTOCOL §7 + pull `ohm-rfc/ROADMAP.md`. Next free ID ≈ 0033.
 >
-> 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`).
+> STATE (end of 0031, 2026-05-28): **OHM live at rfc-app v0.27.0**
+> (`/api/health` ok, pin=`0.27.0`, deploy lock free). Recently
+> shipped+deployed: v0.27.0 security hardening (Session 0030; the
+> v0.25.0 slot renumbered → v0.27.0), v0.26.0 #28 Part 1 (RFC
+> auto-links), v0.24.0 #27 Haiku suggest-tags. **flotilla v1.2.0**
+> merged+tagged (`ef34ffe`) and the shared flotilla checkout is synced.
+> **#34** GCP name-alignment inventoried by 0031 → recommendation:
+> *accept the 2 cosmetic leftovers (disk `ohm-app`, address
+> `ohm-app-ip`) & close* (`ohm-infra/GCP-NAME-ALIGNMENT-RUNBOOK.md`).
 >
-> Recently landed: flotilla **v1.2.0** MERGED + tagged (`ef34ffe`, PR
-> #2, Session 0031.0) — operator-tool code, no OHM deploy; rfc-app
-> **v0.27.0** security-hardening SHIPPED (Session 0030). The shared
-> flotilla checkout is synced to `ef34ffe` and the merged 0028 branch
-> is cleaned up. Still pending: #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. **Recommended: #28 Parts 2 + 3** —
+> offer-to-create-RFC for strong-candidate terms + offer-to-contribute-
+> to-a-pending-RFC (→ **v0.28.0**, possibly two minors). Fully
+> unblocked: deps #3/#7/#12(v0.16.0)/#27(v0.24.0 Haiku, live)/v0.26.0
+> scanner all shipped. You'll **extend** v0.26.0's
+> `backend/app/rfc_links.py` scanner + `frontend/src/components/
+> LinkedText.jsx` (that's the point — not an avoid), add propose-RFC
+> `?title=` pre-fill, the contribute-request form, a new §15 inbox
+> notification kind, and wire accept→#12's invite flow. Part 2's
+> candidate detection MAY use #27's live `ANTHROPIC_API_KEY` Haiku
+> pathway or a heuristic.
 >
-> 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`.
+> Other candidates (mostly blocked/date-gated): #21 Part A Amplitude
+> audit (needs ~1wk real data, ~2026-06-04); #22 pro-consent copy
+> (operator-drafted + counsel); #20/#18 ops (DMARC Phase B ~06-04;
+> stale `wiggleverse/meta` webhook still pointing at deprovisioned
+> `rfc.wiggleverse.org`; bounce wiring); #31b polish (operator
+> screenshots); #33 repo alignment (proposal ready in
+> `REPO-NAMING-PROPOSAL.md`, execution operator-led/URL-breaking);
+> #34 close-out (operator accepts the recommendation).
 >
-> 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.
+> AVOID conflicting with: whatever 0032 is doing (SSH/IAP ops);
+> v0.27.0's still-fresh security surfaces (`otc.py`, `ratelimit.py`,
+> `sanitizeHtml.js`, `MarkdownPreview/ProposalView/Editor.jsx`,
+> migration 023) — build *on* the settled sanitize, don't re-touch it.
+>
+> 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). **If you build in rfc-app, take a fresh `git
+> worktree` with its own venv** — the shared `/Users/benstull/git/
+> rfc-app` checkout may be mid-edit by another session, and a shared
+> checkout *will* get reset under you (it bit 0031 on the flotilla
+> merge; see this transcript's addendum). Coordinate the serialized
+> deploy lock + version slot; do NOT `flotilla deploy` incomplete work.
+> Branches + PRs (gitea API over the stored HTTPS cred; FF-merge).
+> Subagents write their own §5 transcripts. Finalize + publish your
+> transcript LAST — deliver the handoff prompt in chat before
+> `publish-transcript.sh`. Claim your ID, then go.