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/fix-defect.md

@@ -3,6 +3,7 @@
 Automated defect-fix workflow. Ticket ID: `$ARGUMENTS`
 
 This is the **NowChess-Frontend** repo (Angular 20 / TypeScript). Gates:
+
 - Build: `npm run build`
 - Test: `npm test -- --watch=false --browsers=ChromeHeadless`
 - Format: `npx prettier --write .` (check with `npx prettier --check .`)
@@ -15,6 +16,7 @@ Extract and display: summary, description, steps to reproduce, Priority, Subsyst
 ## Step 2 — Create Worktree
 
 Derive branch name from ticket:
+
 - `type` from YouTrack issue type: `bug` → `fix`, `feature`/`task` → `feat`, `refactor` → `refactor`, else `chore`
 - `scope` from affected area (kebab-case, omit if unclear)
 - `description` from ticket summary: lowercase, kebab-case, max 40 chars, drop articles
@@ -42,6 +44,7 @@ After root cause confirmed, assess scope:
 **Complex** (3+ files, multiple concerns, or estimated > 1 hour): create subtasks before coding.
 
 To create subtasks:
+
 1. Break fix into discrete, independently-completable tasks (e.g. "Fix selection state in BoardComponent", "Add spec for flip behaviour", "Update GameService move stream").
 2. For each subtask call `mcp__youtrack__create_issue` with:
    - `project`: based on subtask content — do **not** inherit from parent. Frontend/UI → `NCWF`; backend code → `NCS`; Kubernetes/pipelines/CI-CD/infrastructure → `NCI`. If ambiguous, ask user.
@@ -66,7 +69,7 @@ Then proceed to Step 4, implementing subtasks in order.
 5. Run `npx prettier --check .` — **blocking, foreground only** (never `run_in_background`). Wait for exit code 0. Must be green.
    - If it fails, fix all issues and re-run until exit code 0.
    - **Do NOT proceed to Step 5 until the build, tests and format check all pass.**
-If any step fails, iterate until all pass.
+     If any step fails, iterate until all pass.
 
 ## Step 5 — Review
 
@@ -76,6 +79,7 @@ Display findings grouped by severity.
 ## Step 5b — Apply Review Findings
 
 If the review produced any findings (any severity):
+
 1. Implement all agreed fixes.
 2. Run `npm run build` — must be green.
 3. Run `npm test -- --watch=false --browsers=ChromeHeadless` — must be green.
@@ -125,12 +129,12 @@ Files changed:
 
 After commenting, ask the user if `$ARGUMENTS` should be linked to any other issues not already linked:
 
-| Situation | Relation |
-|-----------|---------|
-| This fix blocks another open ticket | `blocks` |
-| Another ticket must ship first | `is blocked by` |
-| Related defect or story | `relates to` |
-| Duplicate of another defect | `duplicates` |
+| Situation                           | Relation        |
+| ----------------------------------- | --------------- |
+| This fix blocks another open ticket | `blocks`        |
+| Another ticket must ship first      | `is blocked by` |
+| Related defect or story             | `relates to`    |
+| Duplicate of another defect         | `duplicates`    |
 
 Scan the ticket description and comments for any issue IDs that were mentioned but not yet linked. Suggest those automatically.