Generalize tracker references, restructure refactor skill, and strengthen coding rules

- Replace all Jira-specific references with generic tracker/work-item
  terminology (TRACKER-ID, work item epics); delete project-management.mdc
  and mcp.json.example
- Restructure refactor skill: extract 8 phases (00–07) and templates into
  separate files; add guided mode for pre-built change lists
- Add Step 3 "Code Testability Revision" to existing-code workflow
  (renumber steps 3–12 → 3–13)
- Simplify autopilot state file to minimal current-step pointer
- Strengthen coding rules: AAA test comments per language, test failures as
  blocking gates, dependency install policy
- Add Docker Suitability Assessment to test-spec and test-run skills
  (local vs Docker execution)
- Narrow human-attention sound rule to human-input-needed only
- Add AskQuestion fallback to plain text across skills
- Rename FINAL_implementation_report to implementation_report_*
- Simplify cursor-meta (remove _docs numbering table, quality thresholds)
- Make techstackrule alwaysApply, add alwaysApply:false to openapi

.cursor/skills/research/SKILL.md

@@ -112,9 +112,6 @@ When the user wants to:
 - Assess or improve an existing solution draft
 
 **Differentiation from other Skills**:
-- Needs a **visual knowledge graph** → use `research-to-diagram`
-- Needs **written output** (articles/tutorials) → use `wsy-writer`
-- Needs **material organization** → use `material-to-markdown`
 - Needs **research + solution draft** → use this Skill
 
 ## Stakeholder Perspectives