verify-stack surfaced a Flowable 500: delivering messageEventReceived to the Beoordelen task's
execution is wrong — a message boundary event's subscription lives on its own execution. Correlate
instead by the registration's process instance id (recorded at submit): query the execution
subscribed to RegistratieIngetrokken and deliver the message there. Withdrawal moves from
IUserTaskClient to IWorkflowClient.WithdrawProcessAsync; the handler no longer needs a task lookup.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The S-11b port change (WithdrawBeoordelingAsync + BeoordelingTask.ExecutionId) broke the solution
build: the acceptance in-memory IUserTaskClient still used the old signature. Implement the new
member and carry an executionId.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add an interrupting message boundary event (RegistratieIngetrokken) on the Beoordelen task that
ends the process; the Workflow Client delivers the message to the task's execution, and the
withdraw handler triggers it best-effort after the domain transition (ADR-0014).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The WithdrawRegistration handler delivers the withdrawal message to the open Beoordelen task's
execution; the Workflow Client PUTs messageEventReceived (RegistratieIngetrokken). BeoordelingTask
now carries its executionId.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
A withdrawn registration may keep a lingering Beoordelen task until the workflow cancels it; the
werkbak must list only registrations still open for beoordeling, so it drops off.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
