diff --git a/SESSION-J-TRANSCRIPT-2026-05-27T23-50--2026-05-28T03-20.md b/SESSION-J-TRANSCRIPT-2026-05-27T23-50--2026-05-28T03-20.md
index e661351..3c7ce28 100644
--- a/SESSION-J-TRANSCRIPT-2026-05-27T23-50--2026-05-28T03-20.md
+++ b/SESSION-J-TRANSCRIPT-2026-05-27T23-50--2026-05-28T03-20.md
@@ -611,12 +611,34 @@ slot collision.
    Session J)` to record the slot reshuffling explicitly. v0.15.0
    remains reserved for #13 Amplitude, so #12 jumps to v0.16.0.
 
-Committed to `ohm-rfc/main` and pushed.
+Committed to `ohm-rfc/main` as `4c89179` and pushed
+(`d6af91f..4c89179 main -> main`).
 
-This transcript written. The transcript filename
+Transcript written. The filename
 `SESSION-J-TRANSCRIPT-2026-05-27T23-50--2026-05-28T03-20.md`
 matches the convention. Published via
-`~/git/ohm-infra/scripts/publish-transcript.sh`.
+`~/git/ohm-infra/scripts/publish-transcript.sh` at
+commit `44995c9` on `wiggleverse/ohm-session-history`
+(`179c1ea..44995c9 main -> main`).
+
+### Arc 20 — Operator-requested transcript update + re-publish
+
+Operator: "update the transcript." Re-read the just-published Arc
+19 against the post-write commit SHAs I'd captured but only
+described in forward-looking voice, and updated the section to
+record the actual results: `4c89179` for the ROADMAP commit,
+`44995c9` for the publish-script's commit on
+`ohm-session-history`. Also tightened the cut-state table's
+ohm-rfc + ohm-session-history rows to name those SHAs concretely.
+
+This Arc 20 itself is the second self-reference: writing it
+changes the transcript, so re-running `publish-transcript.sh`
+produces a new "update SESSION-J-…" commit on
+`wiggleverse/ohm-session-history` carrying this section.
+Session-I's Arc 16c noted the same publish-cycle
+self-referentiality is now a regular feature — every transcript
+extension after publish triggers a re-publish, and the script's
+idempotency contract handles the round-trip cleanly.
 
 ---
 
@@ -626,10 +648,10 @@ matches the convention. Published via
 | --- | --- |
 | flotilla | Unchanged. v1.0.1 installed; deployment registered; 3 new `deploys` rows added this session (`id=12 failed`, `id=13 failed`, `id=14 succeeded` — all v0.14.0). |
 | rfc-app | `de28272` tag `v0.14.0`. Pushed to `origin = git.wiggleverse.org/ben.stull/rfc-app` AND `benstull = git.benstull.org/benstull/rfc-app`. `VERSION = 0.14.0`, `frontend/package.json#version = 0.14.0`. `CHANGELOG.md` has a new top entry. CLAUDE.md Session-protocol pointer **still deferred** — Session I also deferred this. |
-| ohm-rfc | `<new commit>` (`.rfc-app-version` bumped to `0.14.0` via `d6af91f`; ROADMAP edited with row #15 + row #12 update via this session's closing commit). |
+| ohm-rfc | `4c89179` (`.rfc-app-version` bumped to `0.14.0` via `d6af91f`; ROADMAP edited via `4c89179` with new row #15 struck through and row #12's target version bumped v0.14.0 → v0.16.0). |
 | OHM live | `deploys.id=14`, v0.14.0, healthy. `/api/health` returns `{"version":"0.14.0","status":"ok"}`. `/docs` reachable anonymously and serves the new user guide. |
 | ohm-infra | New transcript: `SESSION-J-TRANSCRIPT-2026-05-27T23-50--2026-05-28T03-20.md`. No other changes to scripts or protocol. |
-| ohm-session-history | This transcript published via `publish-transcript.sh`. Adds one new file alongside Sessions A–I. |
+| ohm-session-history | This transcript first published at `44995c9` (add); Arc-20 update will re-publish as an "update SESSION-J-…" commit when the operator runs `publish-transcript.sh` again (idempotent — diff push, not a duplicate add). Adds one new file alongside Sessions A–I. |
 | Spawned task | One chip showing for the operator: "Add VM-origin preflight to flotilla deploy" — cwd-rooted in the flotilla repo. |
 
 | This session's ledger | Status |