bump-core-req

# bump-core-req Update a fleet plugin's minimum core version in all three canonical locations. ## Background: why three places? Per this monorepo's conventions (`CLAUDE.md` → Conventions), the core version requirement lives in: 1. `plugins/<slug>/.claude-plugin/hermit-meta.json` → `required_core_version` — **authoritative**, read by `doctor-check.ts` at runtime to detect incompatible siblings 2. `plugins/<slug>/.claude-plugin/hermit-meta.json` → `requires["claude-code-hermit"]` — documentation mirror 3. `plugins/<slug>/.claude-plugin/plugin.json` → `dependencies[name=claude-code-hermit].version` — native Claude Code resolver field All three must stay in sync. This skill is the single operation that touches all of them atomically. It leaves committing to the operator via `/commit`. ## Usage ``` /bump-core-req <fleet-slug> [version] ``` - `<fleet-slug>` — directory name of the fleet plugin under `plugins/` (e.g. `claude-code-fitness-hermit`) - `[version]` — optional target version like `1.0.26`. If omitted, read `plugins/claude-code-hermit/.claude-plugin/plugin.json` → `.version` and use that. ## Steps ### Step 0: Resolve slug If no slug was passed, or it's invalid: 1. Glob `plugins/*/.claude-plugin/plugin.json`. Collect directory names. 2. Remove `claude-code-hermit` from the list — that's core, not a fleet plugin. 3. Ask via `AskUserQuestion`: "Which fleet plugin to update?" with one option per slug. If `claude-code-hermit` was explicitly passed as slug, abort: "C...