not b496ac9477 refactor(event-subscriber): drop the hoofdObject fallback (refs #153) ...

For a `resource: object` notification Objecten sends the object as both hoofdObject and
resourceUrl — the object *is* the main resource — so `HoofdObject ?? ResourceUrl` was a
branch that can never take its left side and that no test could distinguish. It came across
from the zaken path, where hoofdObject genuinely differed (the zaak behind a status).

Tests unchanged and green.

2026-08-28 12:38:27 +02:00

..

acceptance

refactor(event-subscriber): drop the hoofdObject fallback (refs #153)

2026-08-28 12:38:27 +02:00

e2e

docs(e2e): the happy path's public statuses now come from the register (refs #153)

2026-08-28 12:37:21 +02:00