feat: NCWF-5/6/7/8/9 chess analysis page and engine integration

- NCWF-5: scaffold /analysis route with ChessBoard viewer and navigation
- NCWF-6: FEN / PGN / Game-ID input form with depth selector
- NCWF-7: extend GameApiService with analyzePosition(); add AnalysisService
  with game-wide annotation pipeline; proxy /api/analysis -> :8087
- NCWF-8: EvalTimelineComponent — SVG win-chance chart per ply
- NCWF-9: AnnotatedMoveListComponent — quality labels (!! ! ?! ? ??)
  derived from win-chance delta

Also fix pre-existing app.spec.ts failure (missing provideHttpClient).
Apply project-wide prettier formatting pass.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

.claude/commands/create-defect.md

@@ -19,6 +19,7 @@ If `$ARGUMENTS` already answers some of these, skip those questions.
 ## Step 2 — Research (if needed)
 
 If the bug involves component logic, a service, or routing:
+
 - Search repo for relevant code (`Grep`/`Bash`) under `src/app/{components,services,models,core,pages}`.
 - Check `.spec.ts` files for existing coverage of the broken area.
 - Do NOT guess at root cause. Surface findings before drafting.
@@ -56,6 +57,7 @@ Environment / Notes
 ```
 
 Rules:
+
 - Steps must be minimal and reproducible.
 - Expected vs actual: concrete and unambiguous.
 - Omit "Environment / Notes" section if not relevant.
@@ -64,6 +66,7 @@ Rules:
 
 Show the draft to the user.
 **Use `AskUserQuestion` tool to ask:**
+
 - Are steps to reproduce complete and accurate?
 - Severity: Blocker / Critical / Major / Minor / Trivial?
 - Any related tickets or recent changes to link?
@@ -73,6 +76,7 @@ Incorporate feedback. Repeat until user approves.
 ## Step 5 — Determine Project
 
 > **Project routing rules (always apply these):**
+>
 > - Frontend code (UI, UX, web app, components, services) → `NCWF`
 > - Backend code (game engine, bots, API, services, coordinator) → `NCS`
 > - Infrastructure (Kubernetes, pipelines, CI/CD, DB setup, cloud infra) → `NCI`
@@ -86,6 +90,7 @@ If ambiguous, ask the user.
 ## Step 6 — Create Issue
 
 Call `mcp__youtrack__create_issue` with:
+
 - `project`: determined in Step 5
 - `summary`: concise title describing what is broken (≤72 chars, sentence case)
 - `description`: full formatted defect report from Step 3 (Markdown)