an update re-applies routed configs on the next daemon start

[DexterStorey]

Closes #17

What

healInstalledConfigs runs at daemon start: when the running version differs from the last version that wrote configs (a healed-version stamp in ~/.tokenmaxx), it re-applies install for whatever installStatus says is currently routed, then records the version. Since ensureDaemon already restarts the daemon on a version change, this fires exactly once after every update — v0.0.58's dummy-token removal (#15) would have reached existing installs without anyone rerunning tokenmaxx install.

It never adds routing: a harness the user uninstalled or never routed stays untouched, and a heal failure logs to the daemon's stderr without keeping the daemon down.

Testing

bun run check is green: typecheck, biome, and 56 tests, including new coverage for re-applying routed configs after a version change, leaving unrouted harnesses alone, and running once per version rather than on every start.

🤖 Generated with Claude Code

[github-actions]

try this branch: bun add -g tokenmaxx@0.0.59-alpha.82