2 Commits

Include renames

Author	SHA1	Message	Date
ehoandClaude Sonnet 5	73172510ea	feat(zgw): real per-request identity seam + citizen-scoping (WP-53) ... Replaces the hardcoded DocumentStore.DemoOwner and the static ZgwOptions UserId/UserRepresentation with one per-request CallerIdentity, resolved by a pluggable IIdentityProvider (StubIdentityProvider reads X-Role/X-Subject today; a real OIDC/DigiD provider swaps in without touching any consumer). - Domain/Authorization/{CallerIdentity,IIdentityProvider,StubIdentityProvider}.cs + a resolution middleware in Program.cs, right after correlation-id. - Authz.ResolvePrincipal(ctx) keeps its signature (now reads ctx.Caller().Role), so its ~15 call sites needed no changes. - Every endpoint that passed DocumentStore.DemoOwner to a store now passes ctx.Caller().Bsn. - ZgwTokenProvider gains Mint(CallerIdentity) alongside the original Mint() (kept for calls not tied to one citizen); ZgwHttpClient threads an optional caller through to pick the right overload. - IZaakSource gains ListMyCases(caller, now) — the citizen-scoped read OpenZaakZaakSource backs with ZGW's rol__...__inpBsn filter. GET /applications now routes through it instead of ApplicationStore directly, closing the last "reads a static store" gap for a citizen-facing endpoint. Backend 159/159 tests (+8, incl. an HTTP-level two-identity scoping proof), npm run ci green, no api-client drift. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-30 08:27:53 +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