health

To verify your macOS development environment before a handoff mission, run a health check that inspects Brew/npm globals, gh auth scopes, MCP connectivity, dotfile symlinks, and VS Code extensions, emitting exact repair commands for any broken items.

Claude MCP connectivity fails during environment verification due to misconfigured routing or expired credentials. Running a health check validates MCP connections and surfaces re-auth needs, reporting only broken items with exact fix commands to restore operational readiness.

The best way to validate gh auth scopes and dotfile symlinks on an iMac is running a preflight health check. It verifies required CLI tooling and confirms symlink integrity, returning an all green status or exact repair commands for broken components.

VS Code extension state does not directly affect router and lane registry resolution, but both are validated during a preflight health check. The check confirms router smoke tests, lane registry resolution, and VS Code extension setup to ensure full operational readiness.

To debug persistent routing failures in your ai-coding-os workflow, run a health check to validate router smoke tests, lane registry resolution, and command registry coverage. It isolates broken items and outputs exact repair commands to fix the environment.

You should run an environment health check on your iMac right before running handoff missions or when debugging persistent routing and MCP failures. It acts as a preflight readiness gate to ensure all CLI tooling, auth, and registry configurations are intact.