[Lucrona]

Do not merge. This sits on PR 26 (4af682d). PR 27 mockups are not part of this branch.

When a linked Battle.net refresh sees the same Blizzard character id with a new name or realm, that one verified row is updated in place. Its /played snapshots, imported totals, tracked hours, and visibility stay. The old name and realm are stored, and the WoW character manager shows formerly …. A Blizzard id is copied only from that user's current account list, which already had a nullable wow_characters.bnet_id. This migration does not fill any id.

If a second row already exists under the new name, the two are combined only when both are verified to this same linked account. Snapshots are unioned. /played becomes the higher accepted counter, never the sum and never a lower one. The removed row is written to wow_character_merges before it is deleted. A second refresh does not add another history row or another merge.

These are left as they are and recorded in wow_played_quarantine: another owner holds the id, the new-name row is not verified, the new name already has a different id, or the newer counter is lower than the older one. An account entry with no Blizzard id is not used to combine rows.

Retail runs on the existing character refresh. Forever does not, while BNET_FOREVER_ACCOUNT is off. Before that flag is turned on, check from this server that the Forever account list returns a stable character id for the same character on two calls, including after a rename, and a different id for a different account. No Battle.net call was made here.

Migration 0057_wow_rename_merge.sql only creates empty wow_character_names and wow_character_merges. It does not update, delete, or insert character, snapshot, or hours rows. Re-running it against a database that already has a character leaves that row unchanged.

cargo fmt --all, cargo clippy --workspace --all-targets -- -D warnings, and cargo test --workspace passed. Head bd7e7f1a8171379a09fabd3271583a4c29d8e338. No installer was built.