kg rename-project with the same name removes the project from every memory

[kevintseng]

What happens

memesh kg rename-project --from X --to X --apply (the same name twice, e.g. a typo) reports 0 renamed, N merged and exits 0, and afterwards no memory carries project:X any more. The dry run warns about it but --apply goes ahead.

Related: the backup --apply writes goes to ./data/backups/ under the current directory, not next to the database, so running it from another directory scatters backups; and the dry run always reports 0 blocked message rows, so it cannot predict what the apply will refuse.

Steps

1. memesh kg rename-project --from acme --to acme --apply on a graph where 286 memories carry project:acme.
2. Output: 0 renamed, 286 merged.
3. project:acme is gone from all 286.

Expected

Renaming a project to itself is refused. The backup is written beside the database. The dry run reports the same numbers the apply will produce.

[kevintseng]

The product fix is merged in #546. Reopened pending integration verification of the data audit dependency in #562.

[kevintseng]

Verified after #546 and #562 merged into main (9d4e5bb). The same controlled CLI/SQLite replay fails on pre-fix 8c10143 (exit 1, 40 failed assertions) and passes on the integrated tree (exit 0, 87 assertions). Same-name rename refuses without losing project tags; preview/apply counts agree; backups are beside the database. The data invariant passes on a clean real-data copy (exit 0) and rejects a controlled missing-project defect (exit 1). Both PR candidates passed all 12 required checks. Closing after integration verification.