Consolidate 36 per-change specs into 4 feature-level specs and align workflow

Replace granular change-level specs (001–036) with living feature specs:
- 001-combatant-management (CRUD, persistence, clear, confirm buttons)
- 002-turn-tracking (rounds, turn order, advance/retreat, top bar)
- 003-combatant-state (HP, AC, conditions, concentration, initiative)
- 004-bestiary (search, stat blocks, source management, panel UX)

Workflow changes:
- Add /integrate-issue command (replaces /issue-to-spec) for routing
  issues to existing specs or handing off to /speckit.specify
- Update /sync-issue to list specs instead of requiring feature branch
- Update /write-issue to reference /integrate-issue
- Add RPI skills (research, plan, implement) to .claude/skills/
- Create docs/agents/ for RPI artifacts (research reports, plans)
- Remove update-agent-context.sh call from /speckit.plan
- Update CLAUDE.md with proportional scope-based workflow table
- Bump constitution to 3.0.0 (specs describe features, not changes)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

.claude/commands/sync-issue.md

@@ -38,23 +38,31 @@ Extract:
 - `REPO` — the repo name (strip `.git` suffix)
 - `API_BASE` — `https://<GITEA_HOST>/api/v1`
 
-3. Locate the spec file. Run:
+3. Locate the spec file. List the available feature specs:
 
 ```bash
-.specify/scripts/bash/check-prerequisites.sh --json --paths-only
+ls specs/*/spec.md
 ```
 
-Parse `FEATURE_SPEC` from the output. If it fails, ask the user to ensure they're on a feature branch with a spec. For single quotes in args, use escape syntax: e.g `'I'\''m Groot'` (or double-quote if possible: `"I'm Groot"`).
+Present the specs to the user and ask which one contains the acceptance criteria for this issue. If only one spec exists, use it automatically.
 
 ## Execution
 
 ### Step 1 — Read the spec
 
-Load the spec file at `FEATURE_SPEC`. Parse the **User Scenarios & Testing** section, specifically:
+Load the spec file at `FEATURE_SPEC`. Extract user stories and acceptance scenarios using these patterns:
 
-- Each `### User Story N - [Title]` block
+**Flat specs** (001-combatant-management, 002-turn-tracking):
+- Look for the `## User Scenarios & Testing` section
+- Each `### ... Story ...` or `**Story ...** ` block
 - The **Acceptance Scenarios** numbered list within each story (Given/When/Then format)
-- The **Edge Cases** section
+- The **Edge Cases** section(s)
+
+**Per-topic specs** (003-combatant-state, 004-bestiary):
+- Stories are nested inside topic sections (e.g., `## Hit Points` > `### User Stories` > `**Story HP-1 — ...**`)
+- Scan ALL `##` sections for `**Story ...` or `**US-...` patterns
+- Extract acceptance scenarios from each story regardless of nesting depth
+- Collect edge cases from each topic section's `### Edge Cases` subsection
 
 ### Step 2 — Condense into business-level acceptance criteria