Add comprehensive QA and testing framework (52→56 skills)

Introduces a full shift-left QA pipeline with Story Type classification
as the backbone of the Definition of Done:

New skills:
- /test-setup: scaffold test framework + CI/CD per engine (Godot/Unity/Unreal)
- /qa-plan: generate sprint test plan classifying stories by type
- /smoke-check: critical path gate (PASS/PASS WITH WARNINGS/FAIL) before QA hand-off
- /team-qa: orchestrate qa-lead + qa-tester through full QA cycle

Story Type classification (Logic/Integration/Visual/Feel/UI/Config/Data):
- Logic and Integration: BLOCKING DoD gate — unit/integration test required
- Visual/Feel and UI: ADVISORY — screenshot + sign-off evidence required
- Config/Data: ADVISORY — smoke check pass sufficient

Updated skills: story-done (test evidence gate), story-readiness (Story Type
check), gate-check (test framework at Technical Setup, test evidence at
Polish/Release), create-epics-stories (Type field + Test Evidence section)

Updated agents: qa-lead (shift-left philosophy + evidence table),
qa-tester (automated test patterns for Godot/Unity/Unreal)

New templates: test-evidence.md (manual sign-off record), test-plan.md
(sprint-oriented QA plan replacing generic feature template)

Updated coding-standards.md: Testing Standards section with DoD table,
test rules, what NOT to automate, and engine-specific CI/CD commands

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

.claude/skills/story-readiness/SKILL.md

@@ -169,9 +169,14 @@ items pass or are explicitly marked N/A with a stated reason.
 - [ ] **Performance budget noted if applicable**: If this story touches any
   part of the gameplay loop, rendering, or physics, a performance budget or
   a "no performance impact expected — [reason]" note is present.
-- [ ] **Test strategy noted**: The story states whether verification is by
-  unit test, manual test, or playtest. "Acceptance criteria verified by
-  [test type]" is sufficient.
+- [ ] **Story Type declared**: The story includes a `Type:` field in its header
+  identifying the test category (Logic / Integration / Visual/Feel / UI / Config/Data).
+  Without this, test evidence requirements cannot be enforced at story close.
+  Fix: Add `Type: [Logic|Integration|Visual/Feel|UI|Config/Data]` to the story header.
+- [ ] **Test evidence requirement is clear**: If the Story Type is set, the story
+  includes a `## Test Evidence` section stating where evidence will be stored
+  (test file path for Logic/Integration, or evidence doc path for Visual/Feel/UI).
+  Fix: Add `## Test Evidence` with the expected evidence location for the story's type.
 
 ---