feat(spec): #48 Three.js game — SpecKit specify + clarify (Phase 0.5)

features/enhancements/047-threejs-game/checklists/requirements.md

@@ -0,0 +1,39 @@
+# Specification Quality Checklist: Three.js Game
+
+**Purpose**: Validate specification completeness and quality before proceeding to planning
+**Created**: 2026-05-14
+**Feature**: [spec.md](../spec.md)
+
+## Content Quality
+
+- [x] No implementation details (languages, frameworks, APIs)
+  - Note: Spec references Three.js, R3F, drei, and DaisyUI by name. This is unavoidable because the feature is _defined by_ the choice of WebGL via R3F — there is no technology-neutral way to specify "render a 3D scene that integrates with the existing 32-theme system." The PRP at `047_threejs-game_feature.md` made the same choice. Acceptable trade-off.
+- [x] Focused on user value and business needs
+- [x] Written for non-technical stakeholders (modulo the unavoidable WebGL/Three.js terms above)
+- [x] All mandatory sections completed
+
+## Requirement Completeness
+
+- [x] No [NEEDS CLARIFICATION] markers remain
+- [x] Requirements are testable and unambiguous
+- [x] Success criteria are measurable (every SC-\* has a quantitative or observable target)
+- [x] Success criteria are technology-agnostic (SC items describe outcomes — render time, theme update, animation absence, build success, bundle size — not implementations)
+- [x] All acceptance scenarios are defined (US-1 through US-5 each have Given/When/Then scenarios)
+- [x] Edge cases are identified (WebGL unavailable, GPU context loss, runtime preference toggles, theme switch during animation, Pa11y exclusion regression, dice game regression, static export at build)
+- [x] Scope is clearly bounded (Out of Scope section enumerates 8 explicit exclusions)
+- [x] Dependencies and assumptions identified (Assumptions section + Dependencies section both present)
+
+## Feature Readiness
+
+- [x] All functional requirements have clear acceptance criteria (FR-_ map cleanly to US-_ acceptance scenarios)
+- [x] User scenarios cover primary flows (P1 = visit + theme; P2 = reduced motion + Pa11y; P3 = mobile)
+- [x] Feature meets measurable outcomes defined in Success Criteria (each SC-\* is independently verifiable)
+- [x] No implementation details leak into specification beyond the unavoidable WebGL/R3F naming
+
+## Notes
+
+- Items marked incomplete require spec updates before `/speckit.clarify` or `/speckit.plan`.
+- All items pass on first iteration; no rework required.
+- `/speckit.clarify` completed 2026-05-15 — 4 questions resolved (v1 scene content, fallback UX, camera control bounds, analytics scope). All 11 taxonomy categories now Clear. Spec amended with FR-008 (fallback panel), NFR-006 (observability scope), expanded FR-005 (camera constraints + auto-orbit), and SC-009/SC-010 (fallback + auto-orbit success criteria).
+- Wireframe gate per Constitution v1.0.2 Principle III completed 2026-05-15. Two wireframes generated and approved: `01-game-3d-main.svg` and `02-game-3d-fallback.svg`. Both PASS the v5.0 validator (zero errors). Twelve patch-classified issues resolved across the two SVGs (signature alignment, callout positioning to avoid button overlap, callout count parity with annotation groups, US-badge minimum, XML hygiene). Audit trails preserved at `wireframes/01-game-3d-main.issues.md` and `wireframes/02-game-3d-fallback.issues.md`. Spec.md `## UI Mockup` block records the sign-off.
+- `/speckit.plan` is unblocked.

features/enhancements/047-threejs-game/wireframes/01-game-3d-main.issues.md

@@ -0,0 +1,35 @@
+# Issues: 01-game-3d-main.svg
+
+**Feature:** 047-threejs-game
+**SVG:** 01-game-3d-main.svg
+**Last Review:** 2026-05-15
+**Validator:** v5.0
+
+---
+
+## Summary
+
+| Status   | Count |
+| -------- | ----- |
+| Open     | 0     |
+| Resolved | 3     |
+
+---
+
+## Resolved Issues (2026-05-15 Review)
+
+### Signature
+
+| ID   | Issue                                                                                                                    | Code          | Classification | Resolution                                                                               |
+| ---- | ------------------------------------------------------------------------------------------------------------------------ | ------------- | -------------- | ---------------------------------------------------------------------------------------- |
+| X-01 | Signature must be left-aligned at x=40, got x=960                                                                        | SIGNATURE-003 | PATCH          | Moved signature `<text>` from `x="960" text-anchor="middle"` to `x="40"` (left-aligned). |
+| X-02 | Signature must NOT use `text-anchor="middle"` — use left-alignment at x=40                                               | SIGNATURE-003 | PATCH          | Removed `text-anchor="middle"` from signature.                                           |
+| X-03 | Signature format wrong: `'047:01 \| Three.js Game - Main \| SpecKit'` — must be `NNN:NN \| Feature Name \| ScriptHammer` | SIGNATURE-004 | PATCH          | Renamed trailing token `SpecKit` → `ScriptHammer` per project signature convention.      |
+
+---
+
+## Notes
+
+- All issues classified as PATCH per `features/CLAUDE.md` decision table (cosmetic/positional, not layout/spacing).
+- Validator re-run after patches: **PASS** (zero errors).
+- Auto-generated initially by validator v5.0; manually annotated with resolutions by `/speckit.wireframe.review` (2026-05-15).