3 Commits

Include renames

Author	SHA1	Message	Date
ehoandClaude Opus 5	868fb55783	docs: close WP-68, record verification result ... npm run ci passed fully green (lint, format, tokens, all four test suites, both localized builds, audit, backend dotnet test at 216 passing, snippet + api-client drift checks). npm run e2e could not be verified this session: port 4200 was occupied by an unrelated container from a different repo, so Playwright reused it instead of starting this app — a pre-existing local port collision, not a regression, and not part of the local GREEN gate per CLAUDE.md. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-05 15:47:35 +02:00
ehoandClaude Opus 5	472a49f19f	docs(backend): correct IntakePolicy's false re-validation claim (WP-68 F5) ... The doc-comment claimed "the backend re-validates on submit as the authority" — it doesn't. Neither SubmitApplicationRequest nor IntakeRequest carries a scholing answer at all, so there's nothing to re-validate; both submit paths only apply SubmissionRules.RejectZeroUren. A crafted POST can bypass the scholing requirement entirely. States the gap and points to WP-69 (opened, not yet planned) for the enforcement, which needs a wire change. Also strengthens the F2 concurrency test to assert the persisted status matches whichever request actually won the race, and updates WP-68's own Decisions/ acceptance-criteria text to reflect two implementation choices that improved on the original write-up once real constraints surfaced: ProcessingWindow stays on ApplicationStore (StatusAt is already in the same file), and AanvraagStatusTag is not given a Concept member (would have broken AanvraagStatusTag_covers_the_published_lifecycle) — AanvraagStatus.Tag is nullable instead, null exactly for Concept. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-05 15:42:21 +02:00
ehoandClaude Opus 5	6a4a0ad435	docs: add WP-68, aggregate invariants + status modelling ... Architecture review found the context boundaries, FP/TEA idioms and read/write separation sound, and rejected explicit CQRS as the fix for anything found. It located four real defects clustered in one place: the backend's aggregate roots don't guard their own invariants, and the aanvraag status lifecycle is a computed string living in the contracts layer instead of the domain. Full Decisions block pre-made so implementation can proceed without re-litigating scope. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-05 15:20:55 +02:00