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

@@ -106,8 +106,7 @@ Categorize each as: **missing dependency**, **broken import**, **logic/assertion
 ══════════════════════════════════════
  A) Investigate and fix failing tests/code, then re-run
  B) Remove obsolete tests (if diagnosis shows they are no longer relevant)
- C) Leave as-is — acknowledged tech debt (not recommended)
- D) Abort — fix manually
+ C) Abort — fix manually
 ══════════════════════════════════════
  Recommendation: A — fix failures before proceeding
 ══════════════════════════════════════
@@ -115,8 +114,7 @@ Categorize each as: **missing dependency**, **broken import**, **logic/assertion
 
 - If user picks A → investigate root causes, attempt fixes, then re-run (loop back to step 2)
 - If user picks B → confirm which tests to remove, delete them, then re-run (loop back to step 2)
-- If user picks C → require explicit user confirmation; log as acknowledged tech debt in the report, then return success with warning to the autopilot
-- If user picks D → return failure to the autopilot
+- If user picks C → return failure to the autopilot
 
 ## Trigger Conditions