Architect-review remediation: enforce conventions, prod-safe tooling, one form idiom, resilience seams

Acts on the showcase review. Four workstreams; all tests green
(npm run lint, 70 FE tests, ng build, 33 backend tests).

Enforcement + CI:
- eslint.config.mjs bans `any` and enforces layer/context boundaries
  (domain ≠ Angular; herregistratie → registratie → shared, auth → shared);
  `npm run lint` added; ajv 6 scoped to ESLint via nested override.
- .github/workflows/ci.yml: FE lint+check:tokens+test+build, backend dotnet test,
  and an API-client drift check.

One form idiom (the headline finding):
- change-request-form converged onto the wizard pattern — change-request.machine.ts
  (Model/Msg/reduce + value objects) + submit-change-request.ts (Result) + a real
  POST /api/v1/change-requests (server re-validates). Spec + story added; the detail
  page no longer holds an ad-hoc success signal.

Resilience/observability seam:
- api-client.provider.ts: request timeout, X-Correlation-Id, Idempotency-Key for
  writes; comments naming the retry/auth seams.
- Backend logs correlation id + a no-PII submit-audit line; /api/v1 prefix +
  backward-compat note; client regenerated.

Quick wins:
- Dev tooling excluded from prod: scenario.interceptor wired only under isDevMode()
  (?scenario= inert in prod); debug panel @if(isDev) (tree-shaken out).
- src/environments + apiBaseUrl into provideApiClient (angular.json fileReplacements).
- Backend /health + /health/ready.
- Debug view PII-minimised (redactProfile: name/address/DOB redacted, BIG masked).
- IntakePolicyAdapter (removes inline resource in the intake wizard).
- README de-staled; CLAUDE.md gains EN/NL + forms-one-idiom + lint/CI notes.
- Stories: text-input, link, data-row, site-header, site-footer, change-request-form.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

README.md

@@ -6,20 +6,35 @@ register of healthcare professionals, run by CIBG). It looks like an NL Design S
 app, branded **Rijkshuisstijl**, and demonstrates a robust **async-state pattern** where
 the UI can never reach an inconsistent state.
 
-> Demo / POC — no real data, no real login. Free **Fira Sans** stands in for the
-> licensed Rijksoverheid font and a text wordmark for the logo.
+> Demo / POC — **no real login** (DigiD is faked) and synthetic seed data. The
+> business rules and data *are* served by a real **ASP.NET Core backend**
+> (`backend/`) consumed through a generated typed client, so the BFF + DDD design
+> is demonstrable, not hand-waved. Free **Fira Sans** stands in for the licensed
+> Rijksoverheid font and a text wordmark for the logo.
 
 ---
 
 ## Run it
 
+```bash
+docker compose up   # frontend + backend together → app http://localhost:4200, Swagger http://localhost:5000/swagger
+```
+
+Or run the two halves separately:
+
 ```bash
 npm install
-npm start          # app  → http://localhost:4200
-npm run storybook  # component library, organized by atomic layer
+npm start            # app → http://localhost:4200 (proxies /api → backend, proxy.conf.json)
+# in another terminal:
+cd backend && dotnet run --project src/BigRegister.Api   # API → http://localhost:5000/swagger
+
+npm run storybook    # component library, organized by atomic layer
+npm run gen:api      # regenerate the typed API client from the backend OpenAPI doc
 ```
 
 Flow: **Login → Dashboard → Mijn gegevens (wijziging) → Herregistratie → Intake**.
+The backend hosts the business rules (profession derivation, policy questions,
+eligibility, thresholds); see **[backend/README.md](backend/README.md)**.
 
 > **New here:** a **branching intake questionnaire** (`/intake`) where later questions
 > appear based on earlier answers and progress survives a page reload, plus a visual
@@ -96,9 +111,12 @@ import to re-theme the whole app — no component changes.
 
 ## State management (no impossible states)
 
-Data fetching uses Angular's native, signal-based **`httpResource`** (no NgRx,
-no extra dependency). `core/registration.service.ts` exposes resources that carry
-`status()`, `value()`, `error()`, `hasValue()` and `reload()` as signals.
+Data fetching uses Angular's native, signal-based **`resource`** over the generated
+typed client (no NgRx, no extra dependency). Each context's `infrastructure/*.adapter.ts`
+exposes a resource that carries `status()`, `value()`, `error()` and `reload()` as
+signals, and a `parse*` function validates the response at the trust boundary
+(DTO → domain). The screen-shaped ("BFF-lite") endpoints return server-computed
+decisions the FE renders rather than recomputes (see ADR-0001).
 
 The molecule **`<app-async>`** turns those signals into UI. It renders **exactly one** of
 four slots, chosen by a single `computed` — so loading, empty, error and loaded are
@@ -142,7 +160,10 @@ degrade to an instant navigation.
   control flow `@if/@for`).
 - Styling: `@rijkshuisstijl-community/{design-tokens,components-css}` (Utrecht + RHC CSS,
   pre-themed Rijkshuisstijl) — imported in `src/styles.scss`, no hand-written theme.
-- Mock data: JSON in `public/mock/`, timing/outcome shaped by `core/scenario.interceptor.ts`.
+- Data: ASP.NET Core backend (`backend/`, in-memory seeded) exposed via an OpenAPI
+  contract; the FE consumes an **NSwag-generated** typed client (`npm run gen:api`).
+  The `?scenario=` toggle (`shared/infrastructure/scenario.interceptor.ts`) is
+  **dev-only** — it is not wired into production builds.
 - `.npmrc` sets `legacy-peer-deps=true` because `@storybook/angular`'s peer range lags
   Angular 22; the builder runs fine (build verified).
 
@@ -157,4 +178,5 @@ Babel 8 (a breaking change across the Storybook/Babel chain) and is deliberately
 We do **not** run `npm audit fix --force`: its proposed fix downgrades Angular 22 → 21.
 
 ### Deliberately out of scope (POC)
-Real auth/DigiD, real backend, i18n, NgRx, licensed Rijkshuisstijl fonts/logo.
+Real auth/DigiD, real BRP/DUO upstreams, a database/persisted audit store, i18n,
+NgRx, licensed Rijkshuisstijl fonts/logo. (The backend itself *is* implemented.)