ehoandClaude Opus 4.8
6fa155caa3
CI / frontend (push) Successful in 1m51s
CI / storybook-a11y (push) Successful in 5m4s
CI / backend (push) Successful in 1m21s
CI / codeql (csharp) (push) Has been cancelled
CI / codeql (javascript-typescript) (push) Has been cancelled
CI / api-client-drift (push) Has been cancelled
CI / e2e (push) Has been cancelled
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>