[loopx-agent]

Recovered private Bot requests reused the original progress message and cursor, allowing a later draft to overwrite an already-delivered failure notice. A versioned terminal phase also missed the normal final-edit path, leaving misleading drafts beside the result.

Scope continuation admission/progress/final presentation and cursors by recovery version, preserve the acknowledged source reaction journal, and replace only the new draft with the final. The original worker also repairs proven legacy presentation using exact prior-or-desired provider readback, current source/Turn checks, and edit-only intents. It cannot enqueue work, resend a result, or overwrite a changed body.

Validation: 491 focused private conversation, native steward, progress, and Inbox reply tests passed. The unchanged base reproduces an actual provider failure notice becoming a processing draft. Wheel validation and the exact-head merge gate are in progress; live adoption remains a separate acceptance step. Both RFC language mirrors document the boundary.

[mergify]

Hi @loopx-agent, the DCO Sign-off check did not pass. Please inspect
its details first: checkout, fetch, timeout or infrastructure errors
need their own recovery, not a rewrite of otherwise signed commits.

If the log confirms a missing Signed-off-by trailer, amend the
affected commit with git commit --amend -s; for multiple commits,
use an interactive rebase against the current base from the correct
base-repository remote and sign off each affected commit. Push the
rewritten PR branch with git push --force-with-lease origin HEAD.

[loopx-agent]

Superseded by #6906 with the required DCO sign-off. The source tree is identical; this branch is retained, and no force push was used.