2 Commits

Include renames

Author	SHA1	Message	Date
ehoandClaude Opus 4.8	a37dfd47a4	ci: cap storybook-a11y resources + document the ACL learnings ... - test-storybook:ci gets --maxWorkers=2 so the Jest runner stops spawning one headless Chromium per core and OOM-ing the Gitea runner host (the root cause). - storybook-a11y job gains a container resource ceiling (--cpus=2 --memory=4g) as a belt-and-suspenders guardrail; noted it needs a docker-mode act_runner. - openzaak-integration.md: add "Anti-corruption layer — two nested boundaries" teaching section (BFF ACL vs upstreams + FE ACL vs BFF, and the principles). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-07-24 15:21:28 +02:00
ehoandClaude Opus 4.8	1c3c195d32	feat(backend): expand stamdata + OpenZaak-ready cases seam (WP-49) ... Stamdata: add beroepen, opleidingen (temporal), and specialismen tables to the schema-driven catalog (zero UI code). opleidingen.beroep and specialismen.beroep both reference beroepen.code — the first stamdata->stamdata references, enforced by two new StamdataRef entries in the CI gate. OpenZaak/ZGW (WP-49, slice 1 — read-only zaken): introduce IZaakSource as the cases read seam. Default LocalZaakSource reads the local SQLite store (offline); an OpenZaakZaakSource (Zgw/ client: HS256 per-call JWT, ZGW->existing-DTO mapper, paginating HTTP source) is selected behind Zgw:Enabled (default false). The FE never changes — same ApplicationSummaryDto, no api-client drift. Unit-tested with fixtures + a stub HttpMessageHandler; no live OpenZaak needed. Docs: ADR-0005, reference/openzaak-integration.md, WP-49..52 roadmap, stamdata.md update, README index rows. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-07-24 15:01:06 +02:00