5 Commits

Include renames

Author	SHA1	Message	Date
ehoandClaude Opus 4.8	0ea43af7b6	feat(registratie): WP-34 — phone field + BRP address read-only ... Reshape the adreswijziging form into a contact-change form: the BRP address is authoritative and shown read-only (you change it at the gemeente), and the phone number becomes the editable/submittable field. New Telefoonnummer value object (parse-don't-validate); backend RejectPhoneChange re-validates as authority. POST /change-requests now carries { telefoon } (typed client regenerated). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-07-22 20:11:26 +02:00
ehoandClaude Opus 4.8	4cf1147fc1	feat(beheer): WP-32 — undo/redo for the stamdata table editor ... Wire the WP-31 createHistory helper into StamdataStore: per-table undo/redo over the edited rows, recording only real edits and restoring via the existing Seed msg. Ctrl/Cmd+Z / +Shift+Z, deferring to native text-undo inside grid cell inputs. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-07-22 16:10:27 +02:00
ehoandClaude Opus 4.8	f7196768ea	fix(auth): make admin pages reachable — async capability guard + sticky dev role + nav ... The admin pages (/beheer/stamdata, /brief/huisstijl) were unreachable in the browser, for three compounding reasons — all fixed here: - **Guard raced /me.** capabilityGuard read can() synchronously while /me was still loading, so it denied even an entitled admin (deny-by-default) and bounced to /login. It's now async: awaits AccessStore.whenReady() (new — resolves once /me settles), then allows if entitled; an authenticated-but-unentitled user goes to /dashboard, anonymous to /login. + auth.guard.spec (the missing test that let this ship). - **Dev role wasn't sticky.** currentRole() read ?role= from the URL on every request, but login/nav drop the param, silently reverting admin→drafter mid-session and 403-ing the admin endpoints. It now persists the role per-tab (sessionStorage), so every role-aware request keeps it. Dev-only (the interceptor is wired only under isDevMode). - **No way in.** Added capability-gated Huisstijl + Stamdata links to the header (shown only when /me grants the cap); injecting AccessStore there also warms /me early. New en translations for the two labels; site-header story stubs AccessStore (+ AsAdmin variant) so it needs no HTTP. Verified live: with ?role=admin the header shows both links, clicking Stamdata loads the grid (GET /api/v1/stamdata → 200, was 403→redirect); a non-admin sees no link. Full `npm run ci` green (310 tests); site-header stories pass axe. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-07-21 21:03:32 +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
ehoandClaude Sonnet 5	e276629107	feat(fp): WP-20 — second locale proof (nl/en build seam) ... angular.json gains an i18n block (sourceLocale nl, en translation file) and an `en` build/serve configuration with i18nMissingTranslation: "error" so a new $localize string without an English unit fails the build, not silently falls back. CI now runs `ng build --localize` to build both locales every run. Verified end-to-end, not just "the build succeeded": the nl bundle ships "Inloggen met DigiD", the en bundle ships "Log in with DigiD". Incidental: prettier/compodoc regen noise in docs/wcag-checklist.md, src/docs/a11y.mdx, documentation.json from the same working session. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-04 18:16:11 +02:00