doctorlisted

# Orchestray Doctor Run 10 probes (11 with `--deep`) against the current Orchestray installation and print a structured health report. If `$ARGUMENTS` contains `--verbose` or `-v`, emit a `## Detail` section after the summary. ## Setup If `$ARGUMENTS` contains `--deep`, set `DEEP=true`. The deep probe (P9) runs after P8 and adds per-file install-integrity verification. Without `--deep`, P9 is skipped and behavior is identical to v2.1.2. Resolve the **plugin root** and **project root** as follows: - Plugin root: the directory containing Orchestray's own source files. Try these in order: 1. Walk up from the current working directory until you find a directory containing both `bin/install.js` and `package.json` with `"name": "orchestray"`. 2. Fall back to `~/.claude/orchestray` (global install path). Store as `PLUGIN_ROOT`. - Project root: the current working directory (where `.orchestray/` lives, if present). Store as `PROJECT_ROOT`. Read the plugin version: `cat $PLUGIN_ROOT/VERSION` (trim whitespace). If VERSION is unreadable, use `"unknown"`. ## Probes Run each probe in order. For each probe, record: - status: `OK`, `WARN`, or `FAIL` - line: the formatted one-liner (see per-probe spec below) - error: raw error detail (used only in `--verbose` output) If a probe times out or the underlying operation takes more than 5 seconds, mark it `WARN` with line `[WARN] {probe name} timed out — result may be stale`. --- ### P1: Migrations present on disk Check