✔ REQ-ROLE-2 REQ-THREAD-1: one holder per thread, through the broker and the trigger (143.20652ms)
✔ REQ-ROLE-2 REQ-THREAD-1: the 3e triggers refuse writes that skip the broker (479.690994ms)
✔ REQ-MSG-1: a message to or from the assistant names its thread, or is refused (150.473846ms)
✔ REQ-MSG-1: the chief of staff's reply comes back to the thread that sent the work (2659.121328ms)
✔ REQ-MSG-1: a reply can't carry one thread instance's thread to another thread instance (151.625098ms)
✔ REQ-THREAD-1 REQ-USER-2: one thread's messages never reach another thread's holder (214.928441ms)
✔ REQ-LAUNCH-1: a message to a thread with no holder waits, and the next holder gets it (185.337234ms)
✔ REQ-THREAD-2 REQ-LAUNCH-1: threadIdle releases only a thread with nothing waiting, and only for its holder (167.830208ms)
✔ REQ-THREAD-2 REQ-LAUNCH-1: a message delivered to a run that ended unread doesn't hold up the next holder (149.648545ms)
✔ REQ-ROLE-2 REQ-THREAD-1: an approved role.revoke never reaches a thread run, and the thread stays held (135.018862ms)
✔ REQ-USER-2: the human verbs refuse another owner's thread (146.419949ms)
✔ REQ-THREAD-1: thread.create refuses when the business has no thread instance or more than one (109.312944ms)
✔ REQ-ORG-2: projects and threads are named once, and the repo names a business project (169.106091ms)
✔ REQ-THREAD-2: thread.messages returns the thread's history in pages and writes nothing (514.266281ms)
ℹ tests 14
ℹ suites 0
ℹ pass 14
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 5435.6372