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

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-15 22:36:09 +02:00
13 changed files with 83 additions and 114 deletions
@@ -19,7 +19,6 @@ 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.
@@ -57,7 +56,6 @@ Environment / Notes
 ```
 Rules:
 - Steps must be minimal and reproducible.
 - Expected vs actual: concrete and unambiguous.
 - Omit "Environment / Notes" section if not relevant.
@@ -66,7 +64,6 @@ 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?
@@ -76,7 +73,6 @@ 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`
@@ -90,7 +86,6 @@ 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)
@@ -19,7 +19,6 @@ If `$ARGUMENTS` already answers some of these, skip those questions.
 ## Step 2 — Research (if needed)
 If the topic involves unfamiliar UI flows, component structure, or technical constraints:
 - Search the repo for relevant code under `src/app/` (use `Grep`/`Bash`).
 - Use `WebSearch` if the topic involves Angular APIs, external standards or protocols.
 - Do NOT guess. Surface findings before drafting.
@@ -54,7 +53,6 @@ Implementation Notes
 ```
 Rules:
 - User story line: plain English, present tense, from user's perspective.
 - Acceptance criteria: testable, unambiguous, one condition each.
 - Implementation notes: optional — only include if there are known constraints, related tickets, or design refs.
@@ -63,7 +61,6 @@ Rules:
 Show the draft to the user.
 **Use `AskUserQuestion` tool to ask:**
 - Are the acceptance criteria complete and correct?
 - Any implementation constraints to add?
 - Priority (if known)?
@@ -73,7 +70,6 @@ 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`
@@ -87,7 +83,6 @@ If still ambiguous, ask the user.
 ## Step 6 — Create Issue
 Call `mcp__youtrack__create_issue` with:
 - `project`: determined in Step 5
 - `summary`: concise title derived from the "I want to" clause (≤72 chars, sentence case)
 - `description`: full formatted story from Step 3 (Markdown)
@@ -101,14 +96,14 @@ After creation, ask the user (use `AskUserQuestion` if interactive, otherwise in
 Collect any issue IDs the user mentions. For each, determine the correct relation and call `mcp__youtrack__link_issues`:
-| Situation                               | Relation to use |
+| Situation | Relation to use |
-| --------------------------------------- | --------------- |
+|-----------|----------------|
-| This story must be done before another  | `blocks`        |
+| This story must be done before another | `blocks` |
-| Another story must be done before this  | `is blocked by` |
+| Another story must be done before this | `is blocked by` |
-| Stories share domain or are related     | `relates to`    |
+| Stories share domain or are related | `relates to` |
-| This is a child of an epic/story        | `subtask of`    |
+| This is a child of an epic/story | `subtask of` |
-| This is a parent grouping subtasks      | `parent for`    |
+| This is a parent grouping subtasks | `parent for` |
-| This depends on another ticket's output | `depends on`    |
+| This depends on another ticket's output | `depends on` |
 If the user mentions an issue in the story description or implementation notes (e.g. "see NCS-42", "after NCWF-12 is done"), auto-detect and suggest linking it — confirm before creating the link.
@@ -7,12 +7,10 @@ This is the **NowChess-Frontend** repo. Sprint mode defaults to project `NCWF`.
 ## Step 1 — Determine Scope
 **Single-issue mode** (`$ARGUMENTS` set):
 - Call `mcp__youtrack__get_issue` on `$ARGUMENTS`.
 - Proceed with that issue only.
 **Sprint mode** (`$ARGUMENTS` empty):
 - Call `mcp__youtrack__search_issues` with query `project: NCWF Sprints: {current sprint} #Unresolved`.
 - If query returns 0 results, use `AskUserQuestion` to ask for the sprint name, then retry with `project: NCWF Sprints: {name}`.
 - Collect all returned issues.
@@ -20,7 +18,6 @@ This is the **NowChess-Frontend** repo. Sprint mode defaults to project `NCWF`.
 ## Step 2 — Build Issue Tree
 For each top-level issue from Step 1:
 1. Fetch full details via `mcp__youtrack__get_issue`: summary, description, acceptance criteria, Type, existing `Zeitschätzung`, linked issues.
 2. Identify subtasks from links with relation `subtask of` (i.e. issues where the fetched issue is the parent).
 3. Recursively fetch subtasks until all leaves are known.
@@ -32,18 +29,17 @@ For each top-level issue from Step 1:
 ## Step 3 — Estimate Leaf Nodes
 For each leaf node:
 1. Read: summary, description, acceptance criteria, implementation notes.
 2. If scope is unclear, search codebase (`Grep`/`Bash`) under `src/app/` for related files to gauge complexity.
 3. Assign estimate using this scale:
-| Size    | Criteria                                               | Estimate |
+| Size | Criteria | Estimate |
-| ------- | ------------------------------------------------------ | -------- |
+|------|----------|----------|
-| Trivial | Style tweak, copy change, 1-file tweak                 | 30m      |
+| Trivial | Style tweak, copy change, 1-file tweak | 30m |
-| Small   | 1–3 files, single component/service, no unknowns       | 1h–2h    |
+| Small | 1–3 files, single component/service, no unknowns | 1h–2h |
-| Medium  | 3–6 files, new component + service wiring, some design | 3h–5h    |
+| Medium | 3–6 files, new component + service wiring, some design | 3h–5h |
-| Large   | 6+ files, cross-feature, non-trivial state/routing     | 1d–2d    |
+| Large | 6+ files, cross-feature, non-trivial state/routing | 1d–2d |
-| XL      | New feature area, major refactor, research spike       | 3d–5d    |
+| XL | New feature area, major refactor, research spike | 3d–5d |
 4. Record: estimate + one-line reasoning.
 5. Skip leaf if it already has `Zeitschätzung` set — note it as pre-estimated.
@@ -53,7 +49,6 @@ For each leaf node:
 YouTrack auto-sums `Zeitschätzung` from subtasks up to parents — **do not write estimates to parent nodes**.
 Compute display-only rolled-up totals:
 - Parent total = sum of all descendant leaf estimates (including pre-estimated ones).
 - Flag any branch where some leaves are missing estimates (partial roll-up).
@@ -73,13 +68,11 @@ Epic  NCWF-10: Board UI overhaul             [4h 30m]  ← rolled up
 Legend: `[X]` = display-only roll-up (not written). Plain = will be written to YouTrack.
 If sprint mode, show grand total at bottom:
 ```
 Sprint total: Xd Yh Zm  (N issues, M leaves to update)
 ```
 **Use `AskUserQuestion` tool:**
 - Does the breakdown look right?
 - Any estimates to adjust before writing to YouTrack?
@@ -88,7 +81,6 @@ Incorporate all feedback before proceeding.
 ## Step 6 — Write Estimates
 On user approval, write estimates **only to leaf nodes** (bottom-up order):
 - For each leaf with a new estimate, call `mcp__youtrack__update_issue` with field `Zeitschätzung` = approved estimate.
 - YouTrack period format: `"30m"`, `"1h 30m"`, `"1d"`, `"2d 4h"`.
 - Skip leaves already pre-estimated.
@@ -3,7 +3,6 @@
 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 .`)
@@ -16,7 +15,6 @@ 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
@@ -44,7 +42,6 @@ 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.
@@ -69,7 +66,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
@@ -79,7 +76,6 @@ 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.
@@ -129,12 +125,12 @@ Files changed:
 After commenting, ask the user if `$ARGUMENTS` should be linked to any other issues not already linked:
-| Situation                           | Relation        |
+| Situation | Relation |
-| ----------------------------------- | --------------- |
+|-----------|---------|
-| This fix blocks another open ticket | `blocks`        |
+| This fix blocks another open ticket | `blocks` |
-| Another ticket must ship first      | `is blocked by` |
+| Another ticket must ship first | `is blocked by` |
-| Related defect or story             | `relates to`    |
+| Related defect or story | `relates to` |
-| Duplicate of another defect         | `duplicates`    |
+| 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.
@@ -4,7 +4,6 @@ Automated feature-implementation workflow. Ticket ID: `$ARGUMENTS`
 This is the **NowChess-Frontend** repo (Angular 20 / TypeScript). In-project =
 `NCWF`. Gates:
 - Build: `npm run build`
 - Test: `npm test -- --watch=false --browsers=ChromeHeadless`
 - Format: `npx prettier --write .` (check with `npx prettier --check .`)
@@ -41,7 +40,6 @@ are collected and reported at the end with a ready-to-run prompt.
 ## Step 3 — Create Worktree
 Derive branch name from the root ticket `$ARGUMENTS`:
 - `type` from YouTrack issue type: `feature`/`task` → `feat`, `refactor` → `refactor`, `bug` → `fix`, else `chore`
 - `scope` from affected area (kebab-case, omit if unclear)
 - `description` from ticket summary: lowercase, kebab-case, max 40 chars, drop articles
@@ -85,7 +83,6 @@ Display findings grouped by severity.
 ## Step 6b — 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.
@@ -142,12 +139,10 @@ Call `ExitWorktree` with `discard_changes: true` to delete the worktree.
 Final report to the user, in two sections:
 ### Blocked in-project tasks
 List any `NCWF` tasks that could **not** be implemented, with the blocker(s)
 that stopped them. (These can be re-run with this command once blockers clear.)
 ### Cross-project tasks (NCS / NCI / other)
 For every out-of-project task discovered in the tree (whether it was a subtask
 or a blocker), output one entry:
@@ -12,7 +12,6 @@ Extract and display: summary, description, acceptance criteria, implementation n
 ## Step 2 — Research (if needed)
 If the story involves unfamiliar UI flows or technical constraints:
 - Search repo for relevant code under `src/app/` (`Grep`/`Bash`).
 - Use `WebSearch` for Angular APIs, external standards or protocols.
 - Do NOT guess. Surface findings before proposing splits.
@@ -20,7 +19,6 @@ If the story involves unfamiliar UI flows or technical constraints:
 ## Step 3 — Propose Split
 Analyse the story and propose a set of subtasks. Rules:
 - Each subtask = one unit of work, completable independently or in sequence.
 - No subtask should exceed ~2 days of work.
 - Name subtasks in imperative mood (e.g. "Add board theme service", "Render theme picker component").
@@ -28,7 +26,6 @@ Analyse the story and propose a set of subtasks. Rules:
 Show proposed subtask list to user (titles only) and ask:
 **Use `AskUserQuestion` tool:**
 - Does the split look right?
 - Any subtasks to add, remove, or merge?
 - Should any subtask be assigned to a specific person?
@@ -60,7 +57,6 @@ What must be true for this subtask to be considered complete:
 ```
 Rules:
 - Steps/Tasks: concrete, ordered where order matters.
 - Definition of Done: adjust per subtask — not all subtasks need the same criteria (e.g. a research spike has different DoD than an implementation task).
 - Keep description short — one paragraph max.
@@ -78,7 +74,6 @@ If a subtask's project is ambiguous, ask the user before creating it.
 ## Step 6 — Create Subtasks
 For each subtask call `mcp__youtrack__create_issue` with:
 - `project`: from Step 5
 - `summary`: subtask title (≤72 chars, sentence case)
 - `description`: full formatted description from Step 4 (Markdown)
@@ -89,7 +84,6 @@ Then call `mcp__youtrack__link_issues` to link each created subtask to `$ARGUMEN
 ## Step 6b — Inter-Subtask Links
 If subtasks must be done in sequence (one depends on output of another), add ordering links:
 - For each dependency pair call `mcp__youtrack__link_issues` with relation `is blocked by` (subtask B is blocked by subtask A).
 Ask the user to confirm sequencing before adding these links:
@@ -100,12 +94,12 @@ Ask the user to confirm sequencing before adding these links:
 Scan `$ARGUMENTS` description and implementation notes for any referenced issue IDs not already linked. For each:
-| Situation                                | Relation        |
+| Situation | Relation |
-| ---------------------------------------- | --------------- |
+|-----------|---------|
-| Parent story blocks another epic/story   | `blocks`        |
+| Parent story blocks another epic/story | `blocks` |
 | Story depends on another epic completing | `is blocked by` |
-| Related story in same domain             | `relates to`    |
+| Related story in same domain | `relates to` |
-| This story duplicates or supersedes      | `duplicates`    |
+| This story duplicates or supersedes | `duplicates` |
 Suggest links to the user and call `mcp__youtrack__link_issues` on confirmation.
@@ -1,77 +1,58 @@
 ## [0.3.0](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/compare/0.2.8...0.3.0) (2026-06-10)
 ### Features
 - NCWF-5 Scaffold post-game analysis page at /analysis with board viewer and route
 - NCWF-6 FEN / PGN / Game-ID input form for custom analysis
 - NCWF-7 Integrate backend analysis API (POST /api/analysis/position) via GameApiService
 - NCWF-8 Per-move evaluation timeline SVG chart
 - NCWF-9 Annotated move list with quality labels (!! ! ?! ? ??)
 ## 0.0.0 (2026-05-12)
 ### Features
- added bot, light and dark mode ([2de003e](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/2de003e497baee72f998d0d805ca1e58aababe48))
+* added bot, light and dark mode ([2de003e](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/2de003e497baee72f998d0d805ca1e58aababe48))
- added web view 1v1 ([1828fa3](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/1828fa3275ddb8ce6bb90a9f6a970ec428ebce3a))
+* added web view 1v1 ([1828fa3](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/1828fa3275ddb8ce6bb90a9f6a970ec428ebce3a))
- NCS-63 User account implementation ([#2](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/issues/2)) ([ff75c8c](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/ff75c8ce2fad54137f04a14c15bc1d4a38fa9bb8))
+* NCS-63 User account implementation ([#2](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/issues/2)) ([ff75c8c](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/ff75c8ce2fad54137f04a14c15bc1d4a38fa9bb8))
- NCS-75 Frontend Deployment Dockerfile ([#4](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/issues/4)) ([bd7ec58](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/bd7ec581e38b5d8e775741bf16e19b4dc67b979e))
+* NCS-75 Frontend Deployment Dockerfile ([#4](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/issues/4)) ([bd7ec58](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/bd7ec581e38b5d8e775741bf16e19b4dc67b979e))
 ### Bug Fixes
- build issues ([36d72fd](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/36d72fd6cda41be51d28f8ac307dcdbcd31afa91))
+* build issues ([36d72fd](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/36d72fd6cda41be51d28f8ac307dcdbcd31afa91))
- cleaner components seperation ([8b090e4](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/8b090e4d96c64c0adb253e3aefad7930108ccfb9))
+* cleaner components seperation ([8b090e4](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/8b090e4d96c64c0adb253e3aefad7930108ccfb9))
- gitignore ([4da882f](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/4da882f481ba7a008aac868fb37de7cb2bafea5d))
+* gitignore ([4da882f](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/4da882f481ba7a008aac868fb37de7cb2bafea5d))
- GITIGNORE ([8df2d05](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/8df2d0550ab17c9afb2d19c414eac700a75add02))
+* GITIGNORE ([8df2d05](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/8df2d0550ab17c9afb2d19c414eac700a75add02))
- npm ([c11c1d4](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/c11c1d4dce9de4bd5b463e891eebf961b37feb04))
+* npm ([c11c1d4](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/c11c1d4dce9de4bd5b463e891eebf961b37feb04))
- removed .vs ([2833ead](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/2833ead7be3b47ee5c188d2d21b7326cb3cb3f26))
+* removed .vs ([2833ead](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/2833ead7be3b47ee5c188d2d21b7326cb3cb3f26))
- removed cache files ([7ee59c4](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/7ee59c434bf137a08fd560bbc02ceefbcfd90f04))
+* removed cache files ([7ee59c4](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/7ee59c434bf137a08fd560bbc02ceefbcfd90f04))
- size of pieces and removed text view of the game state ([c60d00f](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/c60d00f9d25247504845654615065fbccd7fe448))
+* size of pieces and removed text view of the game state ([c60d00f](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/c60d00f9d25247504845654615065fbccd7fe448))
- structure ([3e8c7c4](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/3e8c7c4057e55aeec7cee8c24f6751ff24912c93))
+* structure ([3e8c7c4](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/3e8c7c4057e55aeec7cee8c24f6751ff24912c93))
 ## [0.0.0](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/compare/0.1.0...0.0.0) (2026-05-12)
 ### Features
- NCS-69 Challenge request ([#3](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/issues/3)) ([bad7366](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/bad7366bdbb048c20218257b30ac22efc9ecb6db))
+* NCS-69 Challenge request ([#3](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/issues/3)) ([bad7366](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/bad7366bdbb048c20218257b30ac22efc9ecb6db))
 ## [0.0.0](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/compare/0.2.0...0.0.0) (2026-05-12)
 ### Bug Fixes
- NCWF-1 401 ([#5](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/issues/5)) ([f8f93ef](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/f8f93efff48f1d7198023fed45b675c2e225df36))
+* NCWF-1 401 ([#5](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/issues/5)) ([f8f93ef](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/f8f93efff48f1d7198023fed45b675c2e225df36))
 ## [0.0.0](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/compare/0.2.1...0.0.0) (2026-05-12)
 ### Bug Fixes
- NCWF-1 401 ([#6](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/issues/6)) ([6d1e06d](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/6d1e06dfd606b93d029e9c9b84eea6f8b3b6294e))
+* NCWF-1 401 ([#6](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/issues/6)) ([6d1e06d](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/6d1e06dfd606b93d029e9c9b84eea6f8b3b6294e))
 ## [0.0.0](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/compare/0.2.2...0.0.0) (2026-05-14)
 ### Bug Fixes
- added missing challenge routes ([61000f8](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/61000f8a22aff8b524664a756cc933834365f923))
+* added missing challenge routes ([61000f8](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/61000f8a22aff8b524664a756cc933834365f923))
 ## [0.0.0](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/compare/0.2.3...0.0.0) (2026-05-15)
 ### Bug Fixes
- build error ([51a363a](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/51a363a2432be111b804082df362975047dc8080))
+* build error ([51a363a](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/51a363a2432be111b804082df362975047dc8080))
- NCWF-2 bugs and desing fixes ([#7](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/issues/7)) ([c02414e](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/c02414ea40177b05a5e62dcf68dcb44efa6d3740))
+* NCWF-2 bugs and desing fixes ([#7](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/issues/7)) ([c02414e](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/c02414ea40177b05a5e62dcf68dcb44efa6d3740))
 ## [0.0.0](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/compare/0.2.4...0.0.0) (2026-06-01)
 ## [0.0.0](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/compare/0.2.5...0.0.0) (2026-06-02)
 ### Bug Fixes
- NCWF-4 Token Issues ([#8](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/issues/8)) ([95eff42](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/95eff42dfe6d9c23ede08c7297614369a1b00d9f))
+* NCWF-4 Token Issues ([#8](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/issues/8)) ([95eff42](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/95eff42dfe6d9c23ede08c7297614369a1b00d9f))
 ## [0.0.0](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/compare/0.2.6...0.0.0) (2026-06-06)
 ## [0.0.0](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/compare/0.2.7...0.0.0) (2026-06-10)
 ### Bug Fixes
- route play-vs-bot to /vs-bot endpoint ([a620735](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/a62073511f2ac912ceb0f6b4730bef37545dd8ea))
+* route play-vs-bot to /vs-bot endpoint ([a620735](https://git.janis-eccarius.de/NowChess/NowChess-Frontend/commit/a62073511f2ac912ceb0f6b4730bef37545dd8ea))
@@ -18,7 +18,9 @@
          "builder": "@angular/build:application",
          "options": {
            "browser": "src/main.ts",
-            "polyfills": ["zone.js"],
+            "polyfills": [
              "zone.js"
            ],
            "tsConfig": "tsconfig.app.json",
            "assets": [
              {
@@ -36,7 +38,9 @@
                "output": "/assets/ChessAssets"
              }
            ],
-            "styles": ["src/styles.css"]
+            "styles": [
              "src/styles.css"
            ]
          },
          "configurations": {
            "production": {
@@ -102,7 +106,10 @@
        "test": {
          "builder": "@angular/build:karma",
          "options": {
-            "polyfills": ["zone.js", "zone.js/testing"],
+            "polyfills": [
              "zone.js",
              "zone.js/testing"
            ],
            "tsConfig": "tsconfig.spec.json",
            "assets": [
              {
@@ -120,7 +127,9 @@
                "output": "/assets/ChessAssets"
              }
            ],
-            "styles": ["src/styles.css"]
+            "styles": [
              "src/styles.css"
            ]
          }
        }
      }
@@ -55,6 +55,7 @@ tags:
    description: Export a game as FEN or PGN
 paths:
  # ---------------------------------------------------------------------------
  # Game lifecycle
  # ---------------------------------------------------------------------------
@@ -466,6 +467,7 @@ paths:
 # =============================================================================
 components:
  securitySchemes:
    bearerAuth:
      type: http
@@ -515,6 +517,7 @@ components:
            $ref: '#/components/schemas/ApiError'
  schemas:
    # -------------------------------------------------------------------------
    # Requests
    # -------------------------------------------------------------------------
@@ -548,7 +551,7 @@ components:
        pgn:
          type: string
          description: PGN text (headers and move list)
-          example: '1. e4 e5 2. Nf3 Nc6 *'
+          example: "1. e4 e5 2. Nf3 Nc6 *"
    # -------------------------------------------------------------------------
    # Game state
@@ -584,7 +587,7 @@ components:
        pgn:
          type: string
          description: PGN move text for the full game so far
-          example: '1. e4'
+          example: "1. e4"
        turn:
          type: string
          enum: [white, black]
@@ -1,4 +1,4 @@
 window.__RUNTIME_CONFIG__ = {
-  API_URL: '${API_URL}',
+  API_URL: "${API_URL}",
-  WEBSOCKET_URL: '${WEBSOCKET_URL}',
+  WEBSOCKET_URL: "${WEBSOCKET_URL}"
 };
@@ -6,6 +6,10 @@
    "outDir": "./out-tsc/app",
    "types": []
  },
-  "include": ["src/**/*.ts"],
+  "include": [
-  "exclude": ["src/**/*.spec.ts"]
+    "src/**/*.ts"
  ],
  "exclude": [
    "src/**/*.spec.ts"
  ]
 }
@@ -4,7 +4,12 @@
  "extends": "./tsconfig.json",
  "compilerOptions": {
    "outDir": "./out-tsc/spec",
-    "types": ["jasmine"]
+    "types": [
      "jasmine"
    ]
  },
-  "include": ["src/**/*.d.ts", "src/**/*.spec.ts"]
+  "include": [
    "src/**/*.d.ts",
    "src/**/*.spec.ts"
  ]
 }
@@ -1,3 +1,3 @@
 MAJOR=0
-MINOR=3
+MINOR=2
-PATCH=0
+PATCH=8