update SESSION-I-TRANSCRIPT-2026-05-27T23-30--2026-05-28T03-15.md

SESSION-I-TRANSCRIPT-2026-05-27T23-30--2026-05-28T03-15.md

@@ -1138,13 +1138,20 @@ the next session" section. The Wave 4 lineup per the roadmap text:
   secret. Operator must `flotilla secret set ohm-rfc-app
   CLOUDFLARE_TURNSTILE_SECRET` before the v0.12.0 deploy.)
 
+Before dispatching, check current main state — a parallel session
+may have shipped a docs-feature release between Session I's close
+and now (typically v0.9.0 or v0.14.0, claiming the next available
+slot). If so, factor the new HEAD into upgrade-from anchors in your
+subagent prompts.
+
 Same constraints as Session I: dispatch parallelizable items as
 forked subagents in a single message, serialize the deploys,
 verify each, strikethrough the version-target table when an item
-ships, commit + push ohm-rfc, write SESSION-J-TRANSCRIPT.md at
+ships, commit + push ohm-rfc, write the session transcript per
-end-of-session. Stop and wait for the operator if a deploy fails,
+~/git/ohm-infra/SESSION-PROTOCOL.md at end-of-session. Stop and
-a release's Upgrade steps require an operator-provided secret,
+wait for the operator if a deploy fails, a release's Upgrade steps
-or you encounter cross-repo ambiguity.
+require an operator-provided secret, or you encounter cross-repo
+ambiguity.
 
 Session-I lessons to apply automatically:
 - Subagents push feature branches only. Driver tags, bumps the
@@ -1154,21 +1161,22 @@ Session-I lessons to apply automatically:
   create their own `git worktree add` in the target repo.
 - Migration numbers: pre-allocate slots per subagent in the prompt
   (Session I used slot 014 for #6 and 015 for #8 successfully; the
-  next free is 016).
+  next free is 016 unless the parallel docs-feature session claimed
+  it — check `ls /Users/benstull/git/rfc-app/backend/migrations/`
+  before dispatching).
 - Phase-7 SSH timeout (60s) can fire while uvicorn is still in
   SIGTERM-grace waiting for SSE clients; if the deploy logs
   `failed` or `in_progress` at phase 7, check `/api/health` —
   the service likely restarted fine. If so, `flotilla deploy
   abort` to clear the in-flight row.
-- Operator-in-progress work in `/Users/benstull/git/rfc-app` main
+- Operator-in-progress work in /Users/benstull/git/rfc-app's main
-  checkout (`DOCS.md` + `docs.py` + `Docs.jsx` + edits to
+  checkout — if the parallel session finished, the working tree
-  `api.py` / `App.jsx` / `api.js`) — do NOT touch. Route all
+  should be clean now. If you see staged "revert" state, route
   integrations through `/tmp/rfc-app-integrate-vX.Y.Z` throwaway
-  worktrees. Use `git update-ref refs/heads/main refs/remotes/origin/main`
+  worktrees and use `git update-ref refs/heads/main refs/remotes/origin/main`
   to advance local main without disturbing the working tree.
-- CHANGELOG.md should be strictly version-descending. If a subagent
+- CHANGELOG.md must be strictly version-descending. If a subagent
-  inserts at the top out of order, fix it during integration (a
+  inserts at the top out of order, fix it during integration.
-  small Python re-sort script works fine).
 - Item #1 VM rename and operator-provided secrets stay operator
   territory unless the operator explicitly clears them.
 ```