Jiang Bohan b8bc828a6b fix(daemon): consolidate every case-duplicate legacy runtime, not just the first ...

Follow-up review on #1220: after switching to `LOWER(daemon_id) =
LOWER(@daemon_id)`, the single-row lookup still only merged one legacy
row per candidate. If a machine already had two rows in the DB that
differed only in casing (e.g. `Jiayuans-MacBook-Pro.local` AND
`jiayuans-macbook-pro.local` coexisting because earlier hostname drift
already minted a duplicate), only one of them got consolidated and the
other stayed orphaned — violating the "no duplicate runtime per machine
after backfill" acceptance.

- FindLegacyRuntimeByDaemonID → FindLegacyRuntimesByDaemonID (:many)
- mergeLegacyRuntimes iterates every returned row and dedupes across
  overlapping legacy candidates so `foo` and `foo.local` both resolving
  to the same stored row don't double-process

Test: TestDaemonRegister_MergesAllCaseDuplicateLegacyRuntimes seeds two
case-duplicate rows with one agent each and confirms both rows are
deleted and both agents end up on the new UUID-keyed row.

2026-04-17 14:31:48 +08:00

..

generated

fix(daemon): consolidate every case-duplicate legacy runtime, not just the first

2026-04-17 14:31:48 +08:00

queries

fix(daemon): consolidate every case-duplicate legacy runtime, not just the first

2026-04-17 14:31:48 +08:00