Set up AI dev environment for recordingtest (#2)

- CLAUDE.md with collaboration rules and Planner/Generator/Evaluator cycle
- .claude/ agents, commands, skills, hooks per Claude Code conventions
- Sprint Contracts for sut-prober, normalizer, recorder, player, diff-reporter
- SUT catalog (EG-BIM Modeler, 187 plugins) and .gitignore excluding SUT tree
- PROGRESS.md / PLAN.md as shared agent handoff state
- Solution scaffold targeting sut-prober PoC

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

.claude/commands/contract.md

@@ -0,0 +1,16 @@
+---
+name: contract
+description: Create or update a Sprint Contract for a module/feature via the planner agent. Usage /contract <module-name or short description>
+allowed-tools: Read, Write, Edit, Agent, Glob, Grep
+---
+
+Create a Sprint Contract and PLAN.md entry for: `$ARGUMENTS`
+
+Delegate to the **planner** subagent. The planner must:
+
+1. Read `PLAN.md`, `PROGRESS.md`, `CLAUDE.md`, and relevant memory.
+2. Write `docs/contracts/<slug>.md` with the Sprint Contract template (Goal, DoD, Interfaces, Out of scope, Evaluation plan, Risks).
+3. Add or update the corresponding `PLAN.md` entry with priority and dependencies.
+4. Return a short briefing with file paths.
+
+If `$ARGUMENTS` is empty, ask the user what to plan. Never write code into `src/` — planning only.