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/refactor/templates/list-of-changes.md

@@ -0,0 +1,49 @@
+# List of Changes Template
+
+Save as `RUN_DIR/list-of-changes.md`. Produced during Phase 1 (Discovery).
+
+---
+
+```markdown
+# List of Changes
+
+**Run**: [NN-run-name]
+**Mode**: [automatic | guided]
+**Source**: [self-discovered | path/to/input-file.md]
+**Date**: [YYYY-MM-DD]
+
+## Summary
+
+[1-2 sentence overview of what this refactoring run addresses]
+
+## Changes
+
+### C01: [Short Title]
+- **File(s)**: [file paths, comma-separated]
+- **Problem**: [what makes this problematic / untestable / coupled]
+- **Change**: [what to do — behavioral description, not implementation steps]
+- **Rationale**: [why this change is needed]
+- **Risk**: [low | medium | high]
+- **Dependencies**: [other change IDs this depends on, or "None"]
+
+### C02: [Short Title]
+- **File(s)**: [file paths]
+- **Problem**: [description]
+- **Change**: [description]
+- **Rationale**: [description]
+- **Risk**: [low | medium | high]
+- **Dependencies**: [C01, or "None"]
+```
+
+---
+
+## Guidelines
+
+- **Change IDs** use format `C##` (C01, C02, ...) — sequential within the run
+- Each change should map to one atomic task (1-5 complexity points); split if larger
+- **File(s)** must reference actual files verified to exist in the codebase
+- **Problem** describes the current state, not the desired state
+- **Change** describes what the system should do differently — behavioral, not prescriptive
+- **Dependencies** reference other change IDs within this list; cross-run dependencies use tracker IDs
+- In guided mode, the input file entries are validated against actual code and enriched with file paths, risk, and dependencies before writing
+- In automatic mode, entries are derived from Phase 1 component analysis and Phase 2 research findings