claim session 0036 (placeholder) + sessions.json entry

0036/SESSION-0036.0-TRANSCRIPT-2026-05-29T00-03--INPROGRESS.md

@@ -0,0 +1,36 @@
+# Session 0036.0 — Transcript
+
+> Date: 2026-05-29
+> Start: 2026-05-29T00-03 (PST implied)
+> Status: **PLACEHOLDER — claimed at session start; finalized at session end.**
+>
+> This file reserves session ID 0036. The driver replaces this body
+> with the full transcript before publishing, and renames the file to
+> its final SESSION-0036.0-TRANSCRIPT-2026-05-29T00-03--<end>.md form.
+
+---
+
+## Launch prompt
+
+```
+OHM roadmap driver, parallel-safe. Claim your own ID first (advisory only);
+read ohm-infra/SESSION-PROTOCOL §7 + ohm-rfc/ROADMAP.md; verify live state.
+
+STATE (end of 0035): OHM live at v0.29.0 (deploys.id=40, healthy), ohm-rfc
+pin 0.29.0, flotilla now v1.3.0. Session 0035 shipped the flotilla webhook
+list/check verb (pure-flotilla, no deploy) and live-verified it — the org
+hook posture is clean.
+
+Most feature items still blocked: #21A / #20B date-gated (~06-04 — check the
+date + the DMARC rua data); #22 needs operator-drafted + counsel-reviewed
+copy; #31b needs operator screenshots; #33/#34 operator-led.
+
+If #21A (Amplitude deep audit) or #20B (email deliverability follow-up) is
+now date-unblocked, that's the cleanest feature work. Do NOT re-pick the
+email-hygiene proposal (RFC-APP-EMAIL-HYGIENE-PROPOSAL.md) — its content
+already shipped in rfc-app v0.18.0.
+
+Hard rules unchanged: never ask for secret bytes; transcript is the final
+step; deliver the next handoff in chat before publishing.
+
+```

sessions.json

@@ -91,5 +91,8 @@
   },
   "0035": {
     "title": ""
+  },
+  "0036": {
+    "title": ""
   }
 }