Add v0.5.0: CCGS Skill Testing Framework, skill-improve, 4 new skills, director gate path fixes

- Add CCGS Skill Testing Framework: self-contained QA layer with 72 skill specs,
  49 agent specs, catalog.yaml, quality-rubric.md, templates, README, CLAUDE.md
- Add /skill-improve: test-fix-retest loop covering static + category checks
- Add 4 missing skills: /art-bible, /asset-spec, /day-one-patch, /security-audit
- Add /skill-test category mode (Phase 2D) with quality rubric evaluation
- Extend /skill-test audit to cover agent specs alongside skill specs
- Update all skill-test and skill-improve path refs to CCGS Skill Testing Framework/
- Remove stale tests/skills/ directory (superseded by CCGS Skill Testing Framework)
- Add director gate intensity modes (full/lean/solo) to gate-check and related skills

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

.claude/skills/bug-report/SKILL.md

@@ -10,8 +10,10 @@ allowed-tools: Read, Glob, Grep, Write
 
 Determine the mode from the argument:
 
-- No `analyze` keyword → **Description Mode**: generate a structured bug report from the provided description
+- No keyword → **Description Mode**: generate a structured bug report from the provided description
 - `analyze [path]` → **Analyze Mode**: read the target file(s) and identify potential bugs
+- `verify [BUG-ID]` → **Verify Mode**: confirm a reported fix actually resolved the bug
+- `close [BUG-ID]` → **Close Mode**: mark a verified bug as closed with resolution record
 
 If no argument is provided, ask the user for a bug description before proceeding.
 
@@ -87,6 +89,51 @@ If no argument is provided, ask the user for a bug description before proceeding
 
 ---
 
+## Phase 2C: Verify Mode
+
+Read `production/qa/bugs/[BUG-ID].md`. Extract the reproduction steps and expected result.
+
+1. **Re-run reproduction steps** — use Grep/Glob to check whether the root cause code path still exists as described. If the fix removed or changed it, note the change.
+2. **Run the related test** — if the bug's system has a test file in `tests/`, run it via Bash and report pass/fail.
+3. **Check for regression** — grep the codebase for any new occurrence of the pattern that caused the bug.
+
+Produce a verification verdict:
+
+- **VERIFIED FIXED** — reproduction steps no longer produce the bug; related tests pass
+- **STILL PRESENT** — bug reproduces as described; fix did not resolve the issue
+- **CANNOT VERIFY** — automated checks inconclusive; manual playtest required
+
+Ask: "May I update `production/qa/bugs/[BUG-ID].md` to set Status: Verified Fixed / Still Present / Cannot Verify?"
+
+If STILL PRESENT: reopen the bug, set Status back to Open, and suggest re-running `/hotfix [BUG-ID]`.
+
+---
+
+## Phase 2D: Close Mode
+
+Read `production/qa/bugs/[BUG-ID].md`. Confirm Status is `Verified Fixed` before closing. If status is anything else, stop: "Bug [ID] must be Verified Fixed before it can be closed. Run `/bug-report verify [BUG-ID]` first."
+
+Append a closure record to the bug file:
+
+```markdown
+## Closure Record
+**Closed**: [date]
+**Resolution**: Fixed — [one-line description of what was changed]
+**Fix commit / PR**: [if known]
+**Verified by**: qa-tester
+**Closed by**: [user]
+**Regression test**: [test file path, or "Manual verification"]
+**Status**: Closed
+```
+
+Update the top-level `**Status**: Open` field to `**Status**: Closed`.
+
+Ask: "May I update `production/qa/bugs/[BUG-ID].md` to mark it Closed?"
+
+After closing, check `production/qa/bug-triage-*.md` — if the bug appears in an open triage report, note: "Bug [ID] is referenced in the triage report. Run `/bug-triage` to refresh the open bug count."
+
+---
+
 ## Phase 3: Save Report
 
 Present the completed bug report(s) to the user.
@@ -101,7 +148,16 @@ If no, stop here. Verdict: **BLOCKED** — user declined write.
 
 ## Phase 4: Next Steps
 
-After saving, suggest:
+After saving, suggest based on mode:
 
-- Run `/bug-triage` to prioritize this bug alongside existing open bugs.
-- If S1 or S2 severity, consider `/hotfix` for an emergency fix workflow.
+**After filing (Description/Analyze mode):**
+- Run `/bug-triage` to prioritize alongside existing open bugs
+- If S1 or S2: run `/hotfix [BUG-ID]` for emergency fix workflow
+
+**After fixing the bug (developer confirms fix is in):**
+- Run `/bug-report verify [BUG-ID]` — confirm the fix actually works before closing
+- Never mark a bug closed without verification — a fix that doesn't verify is still Open
+
+**After verify returns VERIFIED FIXED:**
+- Run `/bug-report close [BUG-ID]` — write the closure record and update status
+- Run `/bug-triage` to refresh the open bug count and remove it from the active list