Fix .cursor skills consistency: flow resolution, tracker-agnostic refs, report naming, error recovery

- Rewrite autopilot flow resolution to 4 deterministic rules based on source code + docs + state file presence
- Replace all hard-coded Jira references with tracker-agnostic terminology across 30+ files
- Move project-management.mdc to _project.md (project-specific, not portable with .cursor)
- Rename FINAL_implementation_report.md to context-dependent names (implementation_report_tests/features/refactor)
- Remove "acknowledged tech debt" option from test-run — failing tests must be fixed or removed
- Add debug/error recovery protocol to protocols.md
- Align directory paths: metrics -> 06_metrics/, add 05_security/, reviews/, 02_task_plans/ to README
- Add missing skills (test-spec, test-run, new-task, ui-design) to README
- Use language-appropriate comment syntax for Arrange/Act/Assert in coderule + testing rules
- Copy updated coderule.mdc to parent suite/.cursor/rules/
- Raise max task complexity from 5 to 8 points in decompose
- Skip test-spec Phase 4 (script generation) during planning context
- Document per-batch vs post-implement test run as intentional
- Add skill-internal state cross-check rule to state.md

.cursor/skills/refactor/phases/02-analysis.md

@@ -50,7 +50,7 @@ Write `RUN_DIR/analysis/refactoring_roadmap.md`:
 
 ## 2c. Create Epic
 
-Create a Jira/ADO epic for this refactoring run:
+Create a work item tracker epic for this refactoring run:
 
 1. Epic name: the RUN_DIR name (e.g., `01-testability-refactoring`)
 2. Create the epic via configured tracker MCP
@@ -68,12 +68,12 @@ Convert the finalized `RUN_DIR/list-of-changes.md` into implementable task files
    - **Task**: `PENDING_refactor_[short_name]`
    - **Description**: derived from the change entry's Problem + Change fields
    - **Complexity**: estimate 1-5 points; split into multiple tasks if >5
-   - **Dependencies**: map change-level dependencies (C01, C02) to task-level Jira IDs
+   - **Dependencies**: map change-level dependencies (C01, C02) to task-level tracker IDs
    - **Component**: from the change entry's File(s) field
    - **Epic**: the epic created in 2c
    - **Acceptance Criteria**: derived from the change entry — verify the problem is resolved
-3. Create Jira/ADO ticket for each task under the epic from 2c
-4. Rename each file to `[JIRA-ID]_refactor_[short_name].md` after ticket creation
+3. Create work item ticket for each task under the epic from 2c
+4. Rename each file to `[TRACKER-ID]_refactor_[short_name].md` after ticket creation
 5. Update or append to `TASKS_DIR/_dependencies_table.md` with the refactoring tasks
 
 **Self-verification**:
@@ -85,7 +85,7 @@ Convert the finalized `RUN_DIR/list-of-changes.md` into implementable task files
 - [ ] No task exceeds 5 complexity points
 - [ ] Task dependencies are consistent (no circular dependencies)
 - [ ] `_dependencies_table.md` includes all refactoring tasks
-- [ ] Every task has a Jira ticket (or PENDING placeholder)
+- [ ] Every task has a work item ticket (or PENDING placeholder)
 
 **Save action**: Write analysis artifacts to RUN_DIR, task files to TASKS_DIR
 

.cursor/skills/refactor/phases/04-execution.md

@@ -7,7 +7,7 @@
 ## 4a. Pre-Flight Checks
 
 1. Verify refactoring task files exist in TASKS_DIR (created during Phase 2d):
-   - All `[JIRA-ID]_refactor_*.md` files are present
+   - All `[TRACKER-ID]_refactor_*.md` files are present
    - Each task file has valid header fields (Task, Name, Description, Complexity, Dependencies)
 2. Verify `TASKS_DIR/_dependencies_table.md` includes the refactoring tasks
 3. Verify all tests pass (safety net from Phase 3 is green)
@@ -24,7 +24,7 @@ The implement skill will:
 4. Launch implementer subagents (up to 4 in parallel)
 5. Run code review after each batch
 6. Commit and push per batch
-7. Update Jira/ADO ticket status
+7. Update work item ticket status
 
 Do NOT modify, skip, or abbreviate any part of the implement skill's workflow. The refactor skill is delegating execution, not optimizing it.
 
@@ -33,7 +33,7 @@ Do NOT modify, skip, or abbreviate any part of the implement skill's workflow. T
 After the implement skill completes:
 
 1. Read batch reports from `_docs/03_implementation/batch_*_report.md`
-2. Read `_docs/03_implementation/FINAL_implementation_report.md`
+2. Read the latest `_docs/03_implementation/implementation_report_*.md` file
 3. Write `RUN_DIR/execution_log.md` summarizing:
    - Total tasks executed
    - Batches completed
@@ -46,14 +46,14 @@ After the implement skill completes:
 
 For each successfully completed refactoring task:
 
-1. Transition the Jira/ADO ticket status to **Done** via the configured tracker MCP
+1. Transition the work item ticket status to **Done** via the configured tracker MCP
 2. If tracker unavailable, note the pending status transitions in `RUN_DIR/execution_log.md`
 
 For any failed or blocked tasks, leave their status as-is (the implement skill already set them to In Testing or blocked).
 
 **Self-verification**:
 - [ ] All refactoring tasks show as completed in batch reports
-- [ ] All completed tasks have Jira/ADO status set to Done
+- [ ] All completed tasks have work item tracker status set to Done
 - [ ] All tests still pass after execution
 - [ ] No tasks remain in blocked or failed state (or user has acknowledged them)
 - [ ] `RUN_DIR/execution_log.md` written with links to batch reports