setuplisted

# /aiagentminder:setup One-time initialization of AIAgentMinder in the current project. Run this in the target project's repo root, NOT in the AIAgentMinder repo itself. ## Inputs - Current working directory (= target project root) - User interaction for project identity questions ## Process ### 1. Detect existing install Read `.claude/aiagentminder-version` if it exists. - **If present:** Tell the user "AIAgentMinder is already installed (version X)." This skill is also the re-sync / upgrade path — only the version stamp and plugin-managed files (e.g. `.claude/rules/`) are refreshed; user-owned files (`CLAUDE.md`, `DECISIONS.md`, `BACKLOG.md`, `SPRINT.md`, `docs/strategy-roadmap.md`) are preserved. If they want a newer plugin version on disk first, ask them to run `/plugin update aiagentminder` before continuing. **v5.1+ upgrade cleanup.** When upgrading from a pre-5.1 install, delete any leftover artifacts of the retired auto-cycle protocol if present in the project root: `.sprint-continuation.md`, `.sprint-continue-signal`, `.sprint-tool-count`, `.sprint-phase-guard-count`. Also remove the old `.claude/rules/context-cycling.md` file (replaced by `context-warnings.md`). Use `rm -f` — silent when the files don't exist. - **If absent:** Continue to step 2. ### 2. Codebase fingerprint Inspect the project root for stack signals (do this via Read/Glob tools, not by asking the user). Note what you find: | Signal | Indicates | |---|---| | `package.json` | Node.js / Ja