control-staff-request: exit 0; ℹ tests 10 ℹ pass 10 ℹ fail 0 
control-tools: exit 0; ℹ tests 18 ℹ pass 18 ℹ fail 0 
control-bundle: exit 0; ℹ tests 21 ℹ pass 21 ℹ fail 0 
m1-sender-any-role: exit 1; ℹ tests 10 ℹ pass 7 ℹ fail 3 
  failed: ✖ failing tests:
  failed: ✖ REQ-COS-1: a refused staff request leaves no staff.request action.allowed event
  failed: ✖ REQ-COS-1: only the pm can send a staff request; every other session is refused and the chief of staff hears nothing
  failed: ✖ REQ-COS-1: the sender is judged by definition: an instance `lead` of the pm definition can ask, an instance `pm` of the coder definition can't
m2-launcher-any-role: exit 1; ℹ tests 10 ℹ pass 8 ℹ fail 2 
  failed: ✖ failing tests:
  failed: ✖ REQ-COS-1: the launcher is judged by definition: an instance `boss` of the chief-of-staff definition receives, a `chief` of the coder definition gives no-chief-of-staff
  failed: ✖ REQ-COS-1: the request goes to the business launcher, and only when that is a chief of staff
m3-no-launcher-passes: exit 1; ℹ tests 10 ℹ pass 8 ℹ fail 2 
  failed: ✖ failing tests:
  failed: ✖ REQ-COS-1: a refused staff request leaves no staff.request action.allowed event
  failed: ✖ REQ-COS-1: the request goes to the business launcher, and only when that is a chief of staff
m4-messaging-lists: exit 1; ℹ tests 10 ℹ pass 9 ℹ fail 1 
  failed: ✖ failing tests:
  failed: ✖ REQ-ASSIST-2: the role definitions' messaging lists hold for a staff request, sender and recipient
m5-message-send-class: exit 1; ℹ tests 10 ℹ pass 9 ℹ fail 1 
  failed: ✖ failing tests:
  failed: ✖ REQ-COS-1: only the pm can send a staff request; every other session is refused and the chief of staff hears nothing
m6-thread-send-class: exit 1; ℹ tests 10 ℹ pass 9 ℹ fail 1 
  failed: ✖ failing tests:
  failed: ✖ REQ-COS-1: only the pm can send a staff request; every other session is refused and the chief of staff hears nothing
m7-count-max: exit 1; ℹ tests 10 ℹ pass 9 ℹ fail 1 
  failed: ✖ a staff request names a task, 1 to 10 distinct roles and counts of 1 to 20; nothing else is accepted
  failed: ✖ failing tests:
m8-count-min: exit 1; ℹ tests 10 ℹ pass 9 ℹ fail 1 
  failed: ✖ a staff request names a task, 1 to 10 distinct roles and counts of 1 to 20; nothing else is accepted
  failed: ✖ failing tests:
m9-count-integer: exit 1; ℹ tests 10 ℹ pass 9 ℹ fail 1 
  failed: ✖ a staff request names a task, 1 to 10 distinct roles and counts of 1 to 20; nothing else is accepted
  failed: ✖ failing tests:
m10-roles-max: exit 1; ℹ tests 10 ℹ pass 9 ℹ fail 1 
  failed: ✖ a staff request names a task, 1 to 10 distinct roles and counts of 1 to 20; nothing else is accepted
  failed: ✖ failing tests:
m11-roles-min: exit 1; ℹ tests 10 ℹ pass 8 ℹ fail 2 
  failed: ✖ a staff request names a task, 1 to 10 distinct roles and counts of 1 to 20; nothing else is accepted
  failed: ✖ failing tests:
  failed: ✖ REQ-COS-1: a refused staff request leaves no staff.request action.allowed event
m12-duplicate-role: exit 1; ℹ tests 10 ℹ pass 9 ℹ fail 1 
  failed: ✖ a staff request names a task, 1 to 10 distinct roles and counts of 1 to 20; nothing else is accepted
  failed: ✖ failing tests:
m13-task-ref: exit 1; ℹ tests 10 ℹ pass 9 ℹ fail 1 
  failed: ✖ a staff request names a task, 1 to 10 distinct roles and counts of 1 to 20; nothing else is accepted
  failed: ✖ failing tests:
m14-role-entry-keys: exit 1; ℹ tests 10 ℹ pass 9 ℹ fail 1 
  failed: ✖ a staff request names a task, 1 to 10 distinct roles and counts of 1 to 20; nothing else is accepted
  failed: ✖ failing tests:
m15-recipient: exit 1; ℹ tests 10 ℹ pass 7 ℹ fail 3 
  failed: ✖ failing tests:
  failed: ✖ REQ-COS-1: the launcher is judged by definition: an instance `boss` of the chief-of-staff definition receives, a `chief` of the coder definition gives no-chief-of-staff
  failed: ✖ REQ-COS-1: the pm asks the chief of staff for roles and counts; the chief receives a STAFF-REQUEST and answers it
  failed: ✖ REQ-COS-1: the sender is judged by definition: an instance `lead` of the pm definition can ask, an instance `pm` of the coder definition can't
m16-log-task: exit 1; ℹ tests 10 ℹ pass 9 ℹ fail 1 
  failed: ✖ failing tests:
  failed: ✖ REQ-COS-1: the pm asks the chief of staff for roles and counts; the chief receives a STAFF-REQUEST and answers it
m17-action-spent: exit 1; ℹ tests 10 ℹ pass 5 ℹ fail 5 
  failed: ✖ failing tests:
  failed: ✖ REQ-COS-1: a pm without message.send is refused like any other gated action
  failed: ✖ REQ-COS-1: a refused staff request leaves no staff.request action.allowed event
  failed: ✖ REQ-COS-1: only the pm can send a staff request; every other session is refused and the chief of staff hears nothing
  failed: ✖ REQ-COS-1: the pm asks the chief of staff for roles and counts; the chief receives a STAFF-REQUEST and answers it
  failed: ✖ REQ-COS-1: the sender is judged by definition: an instance `lead` of the pm definition can ask, an instance `pm` of the coder definition can't
m18-tool-any-role: exit 1; ℹ tests 18 ℹ pass 12 ℹ fail 6 
  failed: ✖ a coder gets no launch, no resolve_decision, and no task tools without a tracker
  failed: ✖ a coder with a tracker gets its own task tools and no task_reassign
  failed: ✖ failing tests:
  failed: ✖ request_staff is the pm's alone: staff.request over message.send, roles and counts bounded
  failed: ✖ the assistant gets send_message, the reads and the web tools (it holds the web grant), no launch
  failed: ✖ the chief of staff gets launch, send_message, end_run and change_organization, and no task verbs
  failed: ✖ the review loop: push_working and request_review for the coder, fetch_review and review_verdict for the reviewer, none for the PM
m19-tool-count-max: exit 1; ℹ tests 18 ℹ pass 17 ℹ fail 1 
  failed: ✖ failing tests:
  failed: ✖ request_staff is the pm's alone: staff.request over message.send, roles and counts bounded
m20-tool-verb: exit 1; ℹ tests 18 ℹ pass 17 ℹ fail 1 
  failed: ✖ failing tests:
  failed: ✖ request_staff is the pm's alone: staff.request over message.send, roles and counts bounded
m21-prompt-any-role: exit 1; ℹ tests 21 ℹ pass 20 ℹ fail 1 
  failed: ✖ failing tests:
  failed: ✖ the prompt tells the pm to ask the chief of staff for sessions, and no other role
n1-sender-by-name: exit 1; ℹ tests 10 ℹ pass 9 ℹ fail 1 
  failed: ✖ failing tests:
  failed: ✖ REQ-COS-1: the sender is judged by definition: an instance `lead` of the pm definition can ask, an instance `pm` of the coder definition can't
n2-launcher-by-name: exit 1; ℹ tests 10 ℹ pass 9 ℹ fail 1 
  failed: ✖ failing tests:
  failed: ✖ REQ-COS-1: the launcher is judged by definition: an instance `boss` of the chief-of-staff definition receives, a `chief` of the coder definition gives no-chief-of-staff
n2b-launcher-exists-only: exit 1; ℹ tests 10 ℹ pass 8 ℹ fail 2 
  failed: ✖ failing tests:
  failed: ✖ REQ-COS-1: the launcher is judged by definition: an instance `boss` of the chief-of-staff definition receives, a `chief` of the coder definition gives no-chief-of-staff
  failed: ✖ REQ-COS-1: the request goes to the business launcher, and only when that is a chief of staff
n2f-filbert-recipient: exit 1; ℹ tests 10 ℹ pass 9 ℹ fail 1 
  failed: ✖ failing tests:
  failed: ✖ REQ-COS-1: the launcher is judged by definition: an instance `boss` of the chief-of-staff definition receives, a `chief` of the coder definition gives no-chief-of-staff
mutants finished
