`--dry-run clone` leaves a `.lore` directory behind when the destination already exists (regression in v0.10.0)

Lore version

lore 0.10.0+1172-lore_v0.10.0__urc_main

Installation method

Prebuilt release binary

Operating system / architecture

Windows -- x86_64

Steps to reproduce

--dry-run is documented as "only report what would have been changed and perform no changes to local file system", but since v0.10.0 a dry-run clone into an EXISTING directory initializes a repository there and leaves it.

Repro

  mkdir dest
  lore --dry-run clone lore://.../repo dest
  # exit 0
  ls -A dest/.lore

A destination that does NOT exist yet is cleaned up correctly. Consequence: the dry run makes the operation it was meant to preview impossible. The real clone into the same directory then fails:

  lore clone lore://.../repo dest
  # [Error] Repository already exist in path .../dest
  #   at lore-revision\src\repository\clone.rs:864:24
  # exit != 0

v0.9.0 is clean in all of the above cases.

Expected vs actual behavior

--dry-run should not change the file system / should not leave state in the file system

Component

Client (CLI)

Server context

No response

Regression?

worked in 0.9.0

Relevant logs or output