Record the post-1.0 queue, and close the competitor's post-paste pair as superseded

ROADMAP now carries the queue in the order it should be done - baseline profile, thumbnail hardening, the 5k/20k scaling numbers, then Copy to / Move to (M16, specified with acceptance criteria), then a CI emulator run - and states why nothing there is scheduled yet.

The interesting part is the copy decision. The competitor's Copy again and Return to source folder are not deferred, they are superseded: both exist because their flow makes you leave the source folder to paste. Copy to / Move to removes that constraint at the source, so the selection is still there for the next destination and there is no back-to-source to offer. The spec records that the engine half already exists - paste() calls planTransfer(paths, target, policy) with the current folder as target and the engine is target-agnostic, so FileOpService and the conflict prompt work from anywhere - and that the missing piece is a folder picker. COMPETITIVE_ANALYSIS points at the same decision in both places it mentioned the pair, so the two documents cannot drift apart.

docs/COMPETITIVE_ANALYSIS.md

@@ -309,7 +309,7 @@ requested feature in the market leader, and the permission line is a claim it ca
 | Duplicate finder | **No** | Explicitly requested, with an offer to pay. Pure local computation over a listing we can already do |
 | Batch rename, including continuing an existing numbering sequence | **No** | **Closed in M14.** Several files are renamed to one name with a number after each, and the numbering continues the folder's own series, so the "Ice (3), Ice (4)" wish from the top complainant is what the dialog now defaults to |
 | Bookmarks | **No** | **Closed in M15.** A star on any folder puts it in **Favourites** on the home screen, above the libraries; a folder that has gone is kept and marked rather than dropped |
-| "Copy again" / "Return to source folder" after a paste | **No** | Shipped in their 3.6.8 and cheap for us — the post-paste moment is when a user most needs a way back |
+| "Copy again" / "Return to source folder" after a paste | **No** | **Closed as superseded.** Both exist because their flow makes you leave the source folder to paste; [ROADMAP](ROADMAP.md) specifies **Copy to… / Move to… (M16)** instead, which never leaves the source — so the selection is still there for the next destination and there is no "back to source" to offer |
 | New-file dot after an operation | **No** | Their 3.6.5. Cheap, and it answers "what did that 4 GB copy just do?" |
 | Date-format setting | **No** | We deliberately leave the timestamp pattern unlocalised (README); a *user setting* is a different thing |
 | Music-player engine switch, video gesture toggle | **No** | Deep settings; low priority for a first release |
@@ -355,9 +355,10 @@ In the ROADMAP's own vocabulary (💡 = candidate, proposed, not scheduled; ✅
 2. ✅ **Duplicate finder** — shipped as **M12**. Asked for by name, by a user offering to pay.
 3. ✅ **Batch rename with sequence continuation** — shipped as **M14**, including the "continue from
    Ice (2)" case that the top complainant names.
-4. ✅ **Bookmarks** — shipped as **M15**. 💡 **"Return to source folder" and "Copy again"** after a
-   paste remain: cheap, local, and the post-paste moment is the one the competitor's changelog
-   calls out.
+4. ✅ **Bookmarks** — shipped as **M15**. ~~💡 "Return to source folder" and "Copy again" after a
+   paste remain~~ — **closed as superseded**: both are workarounds for having to leave the source folder
+   to paste, and **Copy to… / Move to…** ([ROADMAP](ROADMAP.md), M16) removes that constraint, so the
+   selection is still there for the next destination and there is no "back to source" to offer.
 5. 💡 **Highlight files changed by an operation.** Their 3.6.5; answers an obvious question.
 6. **Thumbnail hardening before the next release**: register an explicit Coil `ImageLoader` with a
    decided cache policy and a placeholder, and record a large-folder device pass in