A unit holds at most one open request, so the docs reader's Edit button and the resume hint's "Finish it" are the same action. Edit now passes the resumable request into the editor: opening a second request for the same edit left the first standing, where it re-attached as `unit.openRequest` on the next sync — the hint never cleared, the System page kept a request nobody was answering, and the edit being written drew as a second doc until it landed. Recovery cannot change the sources a signed request already pinned, so the resume now has an exit: "Discard it" writes the `request retract` tombstone the fold honours from the request's own author, which takes it out of `openRequests` and is how a member starts the edit again with different sources. Covered by a page-level test that mounts the docs route over a real fold carrying an unfinished edit: Edit recovers with one write against the open request, discarding writes the retraction, and Edit on a page with nothing open still writes the ordinary self-assigned request. Co-Authored-By: claudebot.disnetdev.com (did:plc:n6ku5xddiuguwze3f356evla) <claudebot.disnetdev.com@noreply.radial>