actually-lsp-doctorlisted

# /actually-lsp-doctor Parse the user's args from the invocation: - `fix` as the first arg means skip the diagnostic report and jump straight to action. - `rust` | `typescript` | `ruby` as an arg narrows focus to that ecosystem. - No args: full diagnostic report followed by interactive fix. ## Step 1: Read project state Read `.claude/actually-lsp.json` in the current project root. If missing, run detection: source `lib/detect.sh` and `lib/ecosystems.sh` from the plugin root (the env var `CLAUDE_PLUGIN_ROOT` points there), call `detect_ecosystems "$PWD"`, and for each detected ecosystem compute the current state per the rules in `CONTEXT.md`. ## Step 2: Diagnose (unless `fix` arg present) Output a per-ecosystem report. For each ecosystem: - State (from `CONTEXT.md`'s six states) - For non-`ready` ecosystems: what's needed to reach `ready` - For `dismissed` ecosystems: note them but don't propose action Keep tone terse. No celebration messaging. ## Step 3: Act For each ecosystem in `no-lsp-plugin`, `server-not-runnable`, or `error`: **`no-lsp-plugin`**: try `claude plugin install <recommended_plugin>@claude-plugins-official` via Bash. The user gets a permission prompt. If denied, output the slash command form (`/plugin install <recommended_plugin>@claude-plugins-official`) and ask the user to run it themselves. **`server-not-runnable`**: run env fixes per ecosystem via Bash. All env fixes auto-run; the user has implicit project consent. Check `readiness_source` in t