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/implement/SKILL.md

@@ -32,31 +32,37 @@ The `implementer` agent is the specialist that writes all the code — it receiv
 
 ## Context Resolution
 
-- TASKS_DIR: `_docs/02_tasks/todo/`
-- DONE_DIR: `_docs/02_tasks/done/`
-- BACKLOG_DIR: `_docs/02_tasks/backlog/`
-- TASKS_ROOT: `_docs/02_tasks/`
-- Task files: all `*.md` files in TASKS_DIR (excluding files starting with `_`)
-- Dependency table: `TASKS_ROOT/_dependencies_table.md`
+- TASKS_DIR: `_docs/02_tasks/`
+- Task files: all `*.md` files in `TASKS_DIR/todo/` (excluding files starting with `_`)
+- Dependency table: `TASKS_DIR/_dependencies_table.md`
+
+### Task Lifecycle Folders
+
+```
+TASKS_DIR/
+├── _dependencies_table.md
+├── todo/        ← tasks ready for implementation (this skill reads from here)
+├── backlog/     ← parked tasks (not scheduled yet, ignored by this skill)
+└── done/        ← completed tasks (moved here after implementation)
+```
 
 ## Prerequisite Checks (BLOCKING)
 
-1. TASKS_DIR (`todo/`) exists and contains at least one task file — **STOP if missing**
-2. `TASKS_ROOT/_dependencies_table.md` exists — **STOP if missing**
-3. At least one task in TASKS_DIR is not yet completed — **STOP if all done** (already-completed tasks live in DONE_DIR)
+1. `TASKS_DIR/todo/` exists and contains at least one task file — **STOP if missing**
+2. `_dependencies_table.md` exists — **STOP if missing**
+3. At least one task is not yet completed — **STOP if all done**
 
 ## Algorithm
 
 ### 1. Parse
 
-- Read all task `*.md` files from TASKS_DIR (excluding files starting with `_`)
+- Read all task `*.md` files from `TASKS_DIR/todo/` (excluding files starting with `_`)
 - Read `_dependencies_table.md` — parse into a dependency graph (DAG)
 - Validate: no circular dependencies, all referenced dependencies exist
 
 ### 2. Detect Progress
 
-- Scan DONE_DIR to identify tasks that were already completed in previous runs
-- Scan the codebase to determine which TASKS_DIR tasks are already completed
+- Scan the codebase to determine which tasks are already completed
 - Match implemented code against task acceptance criteria
 - Mark completed tasks as done in the DAG
 - Report progress to user: "X of Y tasks completed"
@@ -79,7 +85,7 @@ For each task in the batch:
 
 ### 5. Update Tracker Status → In Progress
 
-For each task in the batch, transition its ticket status to **In Progress** via the configured work item tracker (Jira MCP or Azure DevOps MCP — see `protocols.md` for detection) before launching the implementer. If `tracker: local`, skip this step.
+For each task in the batch, transition its ticket status to **In Progress** via the configured work item tracker (see `protocols.md` for tracker detection) before launching the implementer. If `tracker: local`, skip this step.
 
 ### 6. Launch Implementer Subagents
 
@@ -124,33 +130,39 @@ Track `auto_fix_attempts` count in the batch report for retrospective analysis.
 
 ### 10. Test
 
-- Run the full test suite
-- If failures: report to user with details
+- Read and execute `.cursor/skills/test-run/SKILL.md` (detect runner, run suite, diagnose failures, present blocking choices)
+- Test failures are a **blocking gate** — do not proceed to commit until the test-run skill completes with a user decision
+- Note: the autopilot also runs a separate full test suite after all implementation batches complete (greenfield Step 7, existing-code Steps 6/10). This is intentional — per-batch tests are regression checks, the post-implement run is final validation.
 
 ### 11. Commit and Push
 
 - After user confirms the batch (explicitly for FAIL, implicitly for PASS/PASS_WITH_WARNINGS):
   - `git add` all changed files from the batch
-  - `git commit` with a message that includes ALL task IDs (Jira IDs, ADO IDs, or numeric prefixes) of tasks implemented in the batch, followed by a summary of what was implemented. Format: `[TASK-ID-1] [TASK-ID-2] ... Summary of changes`
+  - `git commit` with a message that includes ALL task IDs (tracker IDs or numeric prefixes) of tasks implemented in the batch, followed by a summary of what was implemented. Format: `[TASK-ID-1] [TASK-ID-2] ... Summary of changes`
   - `git push` to the remote branch
 
-### 11b. Move Completed Tasks to Done
-
-- For each task in the batch that completed successfully, move its task spec file from TASKS_DIR (`todo/`) to DONE_DIR (`done/`)
-- `git add` the moved files and amend the batch commit, or create a follow-up commit
-
 ### 12. Update Tracker Status → In Testing
 
 After the batch is committed and pushed, transition the ticket status of each task in the batch to **In Testing** via the configured work item tracker. If `tracker: local`, skip this step.
 
-### 13. Loop
+### 13. Archive Completed Tasks
 
-- Go back to step 2 until TASKS_DIR (`todo/`) is empty (all tasks moved to DONE_DIR)
+Move each completed task file from `TASKS_DIR/todo/` to `TASKS_DIR/done/`.
+
+### 14. Loop
+
+- Go back to step 2 until all tasks in `todo/` are done
 - When all tasks are complete, report final summary
 
 ## Batch Report Persistence
 
-After each batch completes, save the batch report to `_docs/03_implementation/batch_[NN]_report.md`. Create the directory if it doesn't exist. When all tasks are complete, produce `_docs/03_implementation/FINAL_implementation_report.md` with a summary of all batches.
+After each batch completes, save the batch report to `_docs/03_implementation/batch_[NN]_report.md`. Create the directory if it doesn't exist. When all tasks are complete, produce a FINAL implementation report with a summary of all batches. The filename depends on context:
+
+- **Test implementation** (tasks from test decomposition): `_docs/03_implementation/implementation_report_tests.md`
+- **Feature implementation**: `_docs/03_implementation/implementation_report_{feature_slug}.md` where `{feature_slug}` is derived from the batch task names (e.g., `implementation_report_core_api.md`)
+- **Refactoring**: `_docs/03_implementation/implementation_report_refactor_{run_name}.md`
+
+Determine the context from the task files being implemented: if all tasks have test-related names or belong to a test epic, use the tests filename; otherwise derive the feature slug from the component names.
 
 ## Batch Report
 
@@ -167,7 +179,7 @@ After each batch, produce a structured report:
 
 | Task | Status | Files Modified | Tests | Issues |
 |------|--------|---------------|-------|--------|
-| [JIRA-ID]_[name] | Done | [count] files | [pass/fail] | [count or None] |
+| [TRACKER-ID]_[name] | Done | [count] files | [pass/fail] | [count or None] |
 
 ## Code Review Verdict: [PASS/FAIL/PASS_WITH_WARNINGS]
 ## Auto-Fix Attempts: [0/1/2]
@@ -183,7 +195,7 @@ After each batch, produce a structured report:
 | Implementer fails same approach 3+ times | Stop it, escalate to user |
 | Task blocked on external dependency (not in task list) | Report and skip |
 | File ownership conflict unresolvable | ASK user |
-| Test failures exceed 50% of suite after a batch | Stop and escalate |
+| Any test failure after a batch | Delegate to test-run skill — blocking gate |
 | All tasks complete | Report final summary, suggest final commit |
 | `_dependencies_table.md` missing | STOP — run `/decompose` first |