diff --git a/SESSION-L-TRANSCRIPT-2026-05-28T04-22--2026-05-28T05-17.md b/SESSION-L-TRANSCRIPT-2026-05-28T04-22--2026-05-28T05-17.md
index 3f26766..76b6b8e 100644
--- a/SESSION-L-TRANSCRIPT-2026-05-28T04-22--2026-05-28T05-17.md
+++ b/SESSION-L-TRANSCRIPT-2026-05-28T04-22--2026-05-28T05-17.md
@@ -528,13 +528,45 @@ memory at
 so future driver sessions honor the "transcript is the LAST
 thing before publish" discipline. Memory index updated.
 
-### Arc 10 — Final transcript pass + publish
+### Arc 10 — First transcript pass + publish
 
-This file. Final pass folds in arcs 1–9 + this arc; cut-state
-reflects the protocol amendment + the publish-script edit + the
-memory captured. Published via
+This file's first "final" pass folded in arcs 1–9 + arc 10;
+cut-state reflected the protocol amendment + the publish-script
+edit + the memory captured. Published via
 `~/git/ohm-infra/scripts/publish-transcript.sh` to
-`wiggleverse/ohm-session-history`.
+`wiggleverse/ohm-session-history` at commit `b983b7d`.
+
+### Arc 11 — Operator reinforced the final-step discipline; re-finalize + re-publish
+
+Immediately after the first publish, the operator repeated the
+instruction: "and then update the transcript again — always do
+that as a final step of a session." This is precisely the
+pattern the new feedback memory
+(`feedback_transcript_is_final_step.md`) anticipates: a "finalized"
+transcript that gets new material added after it (in this case,
+the arc-9 protocol-amendment exchange itself + the driver's
+closing summary that surfaced the next-session prompt) is not
+yet final — the discipline is to apply the new material AND
+finalize AGAIN AND re-publish.
+
+So this arc 11 captures: the operator reinforced the discipline,
+the driver re-finalized the transcript with this arc included,
+and re-published. The publish script's idempotent-on-identical /
+update-on-changed behavior means the re-publish lands as an
+"Update SESSION-L-TRANSCRIPT-…md" commit on
+`wiggleverse/ohm-session-history`, not a duplicate file. The
+filename's `--<end>` timestamp stays the original
+`2026-05-28T05-17` (the time of the first finalization); the
+re-finalized content acknowledges that the actual session end
+crept a few minutes later (~05-25 PST) as the discipline-
+reinforcement exchange happened.
+
+Future driver sessions should expect this pattern to recur:
+"finalization" is not a one-shot gesture. Any operator
+instruction landing after the first publish triggers another
+finalize + re-publish cycle. The discipline is captured for
+Session M onward in the next-session prompt's closing block
++ the feedback memory.
 
 ---