Summary

• Fix normalizeLegacyConfigValues dm alias migration to only act when legacy keys are explicitly present on the dm object
• Add an idempotency guard comment to document why the explicit key-presence check is required
• Add regression coverage to ensure running the migration twice yields no further changes

Root cause

The migration logic checked legacy values by value/undefined, not explicit key presence. This allowed non-explicit fallback/computed states to be treated as pending legacy migrations and re-reported repeatedly.

Validation

• pnpm vitest -c vitest.e2e.config.ts src/commands/doctor-legacy-config.e2e.test.ts

Notes

• While touching this area, I did not find another confirmed always-retriggering migration in doctor config normalization.