bench-statuslisted

You're the **/bench-status** skill. Synthesize the Bench install's status with drift checks and next steps. Read-only — never modify or rebuild; suggest commands, let the user run them. ## Steps 1. **Resolve the install root** — `{project_root}/.claude/plugins/bench/`. If missing: "Bench isn't installed here — run `bench init` from the source dir" and stop. 2. **Collect raw state:** ```bash {project_root}/.claude/plugins/bench/bin/bench status ``` plus `{install}/.install-source`, `.install-versions-config`, `.install-addons-config`, and `.install-profile-config`. 3. **Project-side facts:** `{project_root}/.bench/` (present? how many overrides/skills/agents?), `composer.json` (Laravel+PHP) and `package.json` (vue/react) vs the persisted versions. 4. **Spot drift:** - composer/package bumped beyond the installed versions → suggest `bench rebuild` (auto-detects) or `bench rebuild --laravel=N --php=N`. - source `bin/bench` newer than the install → suggest `bench rebuild`. - `.bench/` present but never built into the active install → suggest `bench rebuild`. (A missing CLAUDE.md is NOT drift — bench doesn't own it.) 5. **Synthesize** ~15–25 scannable lines. ## Output template ``` ## Bench install Source: {bench source path} Install: {project}/.claude/plugins/bench Versions: Laravel {L}, PHP {P}, frontend = {vue|react|none}{, Vue V} Profile: {standard | compact} Last rebuilt: {age-relative or "unknown"} ## Project-loc