[Bug] Companion personality persists across npm to standalone installer migration

Bug Description
bug: Companion personality persists after uninstall and reinstall with standalone installer

Originally installed Claude Code via npm. After using it for a period, the companion hatched as an uncommon Goose named Quartz. After uninstalling the npm version and reinstalling using the new standalone installer, the companion appeared as a blob but retained the Goose personality from the previous install.

Steps to reproduce:

1. Install Claude Code via npm
2. Use Claude Code — companion hatches as uncommon Goose
3. Uninstall npm Claude Code
4. Install Claude Code via standalone installer
5. Companion appears as a blob with carried-over Goose personality

Question: Is companion state intended to persist across installs? If so, the blob/Goose mismatch (visual variant not matching personality) may be the actual bug rather than the persistence itself.

Likely cause: Companion state persisting in a config or data directory that survives uninstall, but visual variant resolving differently under the standalone installer.

Environment Info

• Platform: darwin
• Terminal: Apple_Terminal
• Version: 2.1.92
• Feedback ID: a49a7232-34bc-42a2-94f2-14796cb58bd5