3 Commits

Include renames

Author	SHA1	Message	Date
not	2bb7d9c165	test(acl): ObjectenGateway integration test against live Objecten (refs #149) ... Drives the real gateway against a running Objecten + Objecttypen pair: two writes for the same id leave exactly one object carrying the second write's status, and nothing outside the public-safe schema. Runs under verify-acl, inside the compose network — which it must, because Objecttypen echoes the request Host into the objecttype `url` and Objecten only accepts the one matching its configured api_root. ADR-0028 records that constraint.	2026-08-14 09:44:15 +02:00
not	4a047c618c	fix(infra): let Objecten actually accept the register record (refs #149) ... Replaying the gateway's calls against a live Objecten + Objecttypen pair turned up two blockers CI would only have found after the fact: - Objecten rejects an objecttype it has not been configured with, and it identifies one by uuid — assigned at seed time by a one-shot that runs after Objecten's static setup_configuration. Pin the uuid on both sides instead. - Objecten notifies on every write and notifications_api_common *raises* when that config is absent, so every POST 500'd after rolling the object back. Objecten → NRC has no broker, worker, kanaal or abonnement yet, so disable notifications rather than wire a client that drops every message; S-19b turns them on for real. With both in place the full exchange verifies end to end: lookup → version → search → create → update (still one object), and a record carrying a bsn is rejected by the schema. ADR-0028 records both.	2026-08-14 09:41:00 +02:00
not	3705a18e18	docs: ADR-0028 + demo note — Objecten holds the register (refs #149) ... ADR-0028 records why the register record lives in Objecten rather than as zaak eigenschappen, why the ACL owns the hop, and how two non-atomic writes are made to converge instead. Also retires the PRD §15 out-of-scope line the slice supersedes.	2026-08-14 09:23:41 +02:00