Fix Mise

Diagnose and repair mise trust, runtime, and version-drift failures with the smallest safe change set.

Standards snapshot (March 2026)

• Diagnose the actual trust or runtime blocker before changing config.
• Prefer project-local fixes first and global config edits only when required.
• Treat mise doctor, mise list, and retrying the failing command as mandatory verification.
• Keep any global config change explicit, backed up, and easy to audit.

When to use

• Commands fail because of untrusted mise config.
• Required runtimes are missing or stale.
• ~/.config/mise/config.toml or project mise files are out of sync with expected tool versions.

When not to use

• The failure is unrelated to mise.
• The user wants a broad toolchain upgrade with no actual mise blocker.
• The issue is generic shell configuration with no mise trust or runtime involvement.