2 Commits

Include renames

Author	SHA1	Message	Date
ehoandClaude Opus 5	6cfd70eeeb	fix(backend): resolve besluit endpoint's id via Referentie, not local PK ... POST /beoordeling/{id}/besluit always 404'd against a real OpenZaak: {id} is the FE-facing case id from IZaakSource.ListCases, which under OpenZaakZaakSource is the ZGW zaak's own uuid, not ApplicationStore's primary key. Resolve the case through ListCases first (same seam the GET sibling already uses), then to the local Aanvraag via its Referentie — the one identifier stable across both sources. Adds ApplicationStore.GetByReferentie and a regression test that reproduces the divergence with a decorating IZaakSource test double instead of a live OpenZaak. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-05 15:20:36 +02:00
ehoandClaude Sonnet 5	ba24784586	feat(openzaak): one-command UI-OpenZaak bridge, real BSN fix, flake mitigation ... scripts/openzaak-ui-up.sh brings up the root app and the OpenZaak harness together, wires them onto one docker network, seeds the catalogus, grants the container-alias zaaktype scope, and verifies a real aanvraag submitted through the UI lands in OpenZaak. Along the way: DocumentStore.DemoOwner was reusing the seeded doctor's 11-digit BIG-nummer as a stand-in BSN, which isn't a valid 9-digit BSN shape — OpenZaak rejects it, breaking both submit's rol-creation step and the citizen's own applications list under Zgw:Enabled=true. Fixed to a real elfproef-valid BSN. Also adds mitigation for a still-unexplained per-container flake (every outbound ZGW POST fails as if the body were empty, for that container's whole lifetime) that correlates with host memory pressure: the script now warns when host swap is heavily used, and an opt-in ZgwDiagnosticHandler (ZGW_DEBUG_HTTP=1) logs Content-Length vs. actual bytes sent so the next reproduction can confirm or rule out client-side body corruption. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-31 08:23:01 +02:00