migration-doctorlisted

# Migration doctor Resolve the **plugin root** from this loaded file and run `python3 "<plugin-root>/migration_doctor.py"`. The doctor and public `coordinator.py` are co-packaged with the skills. For any coordinator readiness request, first read the **Coordinator request schema** in `<plugin-root>/README.md`. For an activation release, use only the co-packaged managed setup surface: `python3 "<plugin-root>/runtime_setup.py" status`, then `prepare`, and use `login-grok` only when the status result reports that managed Grok authentication is unavailable. The command accepts no provider, model, path, environment, binary, tool, or raw argument overrides. Never invoke the native runtime or a provider CLI directly. ## Workflow Run the provider-free `migration_doctor.py` beside this skill's plugin root. It reads local manifests, plugin directories, cache selections, Codex plugin tables in `~/.codex/config.toml`, the runtime manifest, and current host-profile evidence. It also verifies the canonical selected broker lane, immutable artifact and manifest, launchd job, socket, and one closed liveness exchange. That exchange never invokes a provider or returns provider output, and the doctor never downloads an artifact. Treat any installed or active legacy package as a hard routing conflict. Show each observation's source host/state and the report's exact host-manager install, verify, and uninstall actions. Cache-only residue is reported separately. After cleanup, re-run the doctor