Record the first successful phase rotation

Handoff produced, validated, anchored, committed, predecessor slot freed,
successor leased and started with pickup validated. Autonomous.

F33 and F34 proved themselves incidentally in the same event.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011xsXyr5J1RACo71YeKG3Pu

BURNIN.md

@@ -1561,3 +1561,49 @@ Fixed in `cb7782d`. `lastObservedCommand` skips commands the validator would
 call circular. The rule is asked for through `continuity.IsCircularCommand`
 rather than restated, because restating a rule in two places is exactly what
 produced F36.
+
+## Run 5: the continuity chain, live and autonomous, 2026-08-28 01:47
+
+The first successful phase rotation in this project's burn-in history.
+
+```text
+handoff_ref           abe51f5c663f4d59bba2c98c0418554278ec2a9b75bfc504bd36757666e3948a
+transaction_id        06G4A9VSBE5N5BF8BE3J0PSAER    the one that had stuck at "prepared"
+anchor_sha            c643aaab87b4b1f79b9f1d909bf8788a0e25fe61
+pickup_acknowledged   true
+new epoch             06G4AC5KX225JGXAEWH52NNPB0
+new pane              created 01:47:09
+session phase         research
+task                  leased v9, work_phase research, lifecycle started
+```
+
+| Step | Evidence |
+|---|---|
+| Handoff answer parses | F31, no `invalid handoff answer` |
+| Handoff validates | F36 and F37, `handoff_ref` exists |
+| Anchor pushed | `anchor_sha c643aaab` |
+| Release commits | transaction gone from `releases` |
+| Predecessor slot frees | old session dropped |
+| Successor leases and starts | new epoch, new pane, phase `research` |
+| Pickup validates | `pickup_acknowledged: true` |
+
+No lifecycle shepherding. The only operator action in this run was one Enter
+into a pane holding unsent input, which F35 turns into an action.
+
+Two fixes proved themselves incidentally in the same event. The relaunch logged
+`submit_attempts=2`, so F33's resend path does real recovery rather than
+existing only in tests. The new lease carries `progress_sha` at once, so F34's
+launch baseline survives into the real worker path.
+
+### Remaining gates
+
+```text
+research  -> research.json sealed -> request -> rotation -> plan launch carries accepted research
+plan live -> correction comment -> HumanDecisionRecorded -> RemoteTurn -> DecisionNotice receipt, once
+plan.json sealed -> request -> rotation
+implement launch -> correction above accepted plan above accepted research
+```
+
+The correction is held until the plan successor is definitely live. Posting
+earlier still exercises F20 and F23, but it cannot prove a mid-plan correction
+outranks accepted research and the current trajectory.