[aicayzer]

Summary

Describes the core's new call that removes a working copy (withmarfa/marfa#2409). An app passes the number of unsent writes the person agreed to lose, and the core removes the copy only when it holds exactly that number. The devices page explains what is removed and when it is refused, and the wrong_schema entry in Troubleshooting offers it as the way to discard a refused copy that holds unsent writes.

Changes

• devices.mdx: a paragraph under "The working copy" about removing a copy. It covers what goes, the symbolic-link rule, and the refusals unsent_differs, reading_handle and invalid for a folder's copy. It also says that a path with no copy counts as none unsent.
• troubleshooting.mdx: the wrong_schema entry says an app can remove the copy with the count the person agreed to lose, and links to Devices.

Testing

• pnpm test passed (706 tests, including the content lint).
• Each claim was checked against the contract statements device/remove-store through device/remove-store-kept in feat(core): remove a working copy with the unsent writes agreed to marfa#2409, and against the code there.
• Not run: pnpm build.

Notes for reviewers

• Marfa v0.0.38 shipped the core call, and the changelog has its entry. Reviewed together with feat(core): remove a working copy with the unsent writes agreed to marfa#2409.
• docs(swift-sdk): say a replaced refused copy keeps its file budget #643 edits the neighboring paragraph in both files. These additions are separate paragraphs, so the two pull requests should merge in either order.

Checklist

• The title is a scoped Conventional Commit.
• New behavior has a test that was seen failing first, or no test was needed and the reason is above.
• Docs, comments and the contract still say what is true after this change.