plans: row 139, a revoke of the assistant stays with the human (Mos ruling, sage-0523)

Filbert's row 139 note 2: under 139 an arbiter could approve a cited
role.revoke of the assistant. Mos ruled it stays human-only, overridable
by Jason. Row 139 now owns the PRD note under REQ-WAIT-1 and a test.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

docs/plans/2026-10-15_q167-rows-r3.md

@@ -439,6 +439,8 @@ Jason on 2026-10-15.
 - `roles/*.json`, grants only as the PRD 1.5 text requires
 - tests in the bus and business packages, and READMEs; in
   `scripts/test-land-work.sh`, only the arbiter-resolved `not-human` case
+- `docs/prd/mosaic-stack.md`, only the note under REQ-WAIT-1 for the
+  assistant revoke ruling below
 
 ### What ships
 
@@ -462,6 +464,16 @@ Jason on 2026-10-15.
   to the arbiter, for an uncited decision still going to the human, for a
   stale spec citation, and for the land refusal: a coder raises a cited
   merge decision, the arbiter approves it, and the land refuses.
+- A test that a cited role.revoke of the assistant goes to the human and
+  that an arbiter can't resolve it, beside a test that a cited revoke of
+  another role still goes to the arbiter.
+- A revoke of the assistant stays with the human (Mos's ruling, sage-0523,
+  which Jason can override). The assistant is Jason's own channel into
+  the Stack. A role.revoke whose target's definition is in
+  `END_PROTECTED` (`broker.mjs`) routes to the human even when the raise
+  cites the current spec, and an arbiter's resolve of it is refused.
+  Every other cited revoke routes as REQ-DEC-2 says. The PRD notes this
+  under REQ-WAIT-1 as a Mos ruling Jason can override.
 - Whichever of 137 and 139 lands second makes the host land op accept an
   arbiter-resolved merge decision, as row 137's brief says. Row 139 always
   adds a test that land-work still refuses an arbiter-resolved merge