4 Commits

Include renames

Author	SHA1	Message	Date
ehoandClaude Opus 4.8	f8cd77a48a	feat(test): WP-46 — Vitest coverage (report-only) ... Enable coverage via the @angular/build:unit-test builder's first-class options: a `coverage` configuration on the test target (v8 provider, text-summary/html/lcov, excludes for specs/stories/contracts/generated client) + `npm run test:coverage`. Report-only (no thresholds) — visibility first. CI's test step now runs test:coverage (strict superset: fails on a failing test, never on coverage). Baseline ~71% stmts. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-07-23 14:23:55 +02:00
ehoandClaude Opus 4.8	7d2a36ff22	feat(arch): WP-38 — dependency graph + declarative boundaries (dependency-cruiser) ... Adopt dependency-cruiser as the single declarative source for bounded-context + atomic-layer boundaries, replacing the per-context no-restricted-imports blocks that had to be hand-copied (and had left herregistratie uncovered). `.dependency-cruiser.js` encodes context direction (everyone→shared, herregistratie→registratie, showcase→*), domain-purity, contracts-import-nothing, ui↛infrastructure, ApiClient confinement, and no-circular. `npm run dep:check` enforces (wired into ci-local.sh + the frontend CI job); `npm run dep:graph` emits a committed mermaid context×layer graph. ESLint slimmed to no-explicit-any + template a11y. Docs + new-context skill updated to the single source. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-07-23 13:51:04 +02:00
ehoandClaude Opus 4.8	2820cd3476	fix(ci): e2e — let Playwright manage both servers (fixes the 2-hour hang) ... The e2e job backgrounded `dotnet run &` and `ng serve &` in separate Actions steps, then `npx wait-on` (no timeout) in a later step. A process started with `&` in one step is killed when that step's shell exits, so wait-on waited forever on servers that were already gone — the job hung until the runner's hard limit (~2h; Gitea's act_runner doesn't reliably enforce timeout-minutes). Move both servers into Playwright's `webServer` (an array: backend + `npm start`), so Playwright starts them, waits for readiness, runs the suite, and tears them down in the one `npm run e2e` process — CI and local alike. The CI e2e job is now just npm ci / playwright install / npm run e2e. `reuseExistingServer` is on locally (reuses a running app, incl. the docker stack) and off in CI (fresh start). Verified locally via `CI=1 npm run e2e` against free ports + a clean db: both smoke tests pass in ~15s (no hang). The earlier local failure was leftover SQLite state (WP-22) from a dirty run resuming a Concept — CI checks out fresh, so its db is always empty. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-07-21 20:07:35 +02:00
ehoandClaude Opus 4.8	6fa155caa3	fix(ci): green build — en translations, quiet docker npm, local CI check ... Three fixes so Gitea CI is green and stays that way: - **ng build --localize**: `messages.en.xlf` (hand-maintained, matched by id) had drifted ~93 units behind the source since WP-24 — `beheer.*`, `brief.canvas.*`, `brief.diff.*`, `orgTemplate.*`, `brief.besluit.*`, etc. With `i18nMissingTranslation: "error"` that fails the frontend job. Added English `<target>`s for every missing unit (interpolation `<x/>` tags preserved); both nl + en bundles build clean. - **docker npm noise**: the web container's `npm ci` now runs `--no-fund --loglevel=error`, so `docker compose up` boots without npm 11's deprecation / allow-scripts / funding warnings (verified in the running container: 0 warning lines). The underlying Angular webpack-builder deprecation is upstream; migrating to @angular/build is out of scope. - **local CI check**: `scripts/ci-local.sh` + `npm run ci` mirror the CI jobs (lint, format:check, check:tokens, test, build --localize, audit, backend format+test, api-client drift; `--full` adds storybook-a11y) so a red build is caught before pushing. Opt-in pre-push hook at scripts/githooks/pre-push. Documented in CLAUDE.md. Verified: `npm run ci` passes end-to-end; storybook-a11y 169/169 (the local parallel-worker timeouts were the docker stack starving chromium, not a regression). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-07-21 17:20:56 +02:00