brief: row 65 routing table names the chief of staff's Q169 assistant exception and its tests (round 2 ruling, sage-1006, #1558)

docs/plans/2026-10-11_managed-session-config.md

@@ -284,9 +284,12 @@ A change outside this list is named in the packet with its reason.
   to its route and writes them in one organization write, with the
   writer's identity log and receipt. It is human-only and outside
   `ORGANIZATION_KEYS`, as row 165's `instances.set` is, so the chief of
-  staff's tool can't change a harness, a thinking level or a fallback.
-  That tool keeps changing only the model key through
-  `organization.set`, as it does now. The table replaces the "Role
+  staff's tool never reaches it. Through `organization.set` that tool
+  changes only an instance's model key, with one exception: the
+  assistant, whose whole vars it may set under Q169 ("The COS and the
+  user should have the ability to (re)configure the assistant role and
+  seat name", Jason). That write runs the same route checks as
+  `routes.set` (round 2 ruling, sage-1006). The table replaces the "Role
   models" fieldset, which edited only the model key. The write checks the
   same rules as every other write of these vars: `harness-off`,
   `thinking-unsupported`, unknown model, partial fallback. The Role
@@ -303,7 +306,9 @@ A change outside this list is named in the packet with its reason.
   limit check sees the fallback's provider and model; thinking reaches
   the Pi and Claude Code fake adapters as the recorded flag; a level the
   harness can't apply refuses with `thinking-unsupported` at a write and
-  at launch.
+  at launch; the chief of staff's write of the assistant's vars refuses
+  `harness-off`, `thinking-unsupported` and a partial fallback, and a
+  valid one saves with the chief as the actor.
 - Console tests: the routing table lists every instance with its six
   values; a browser test edits a harness, a model, a thinking level and
   a fallback, saves, and reads each back from the file; a partial
@@ -323,7 +328,8 @@ A change outside this list is named in the packet with its reason.
   write, a partial fallback, a fallback taken when the primary passes),
   and one that puts a harness name back in core, plus one for
 `thinking-unsupported` and one that drops the fallback columns from the
-table.
+table, and one where the chief's write of the assistant skips the route
+checks.
 - Gate suites: `node --test 'packages/plugins/tests/*.test.mjs'`,
   `node --test 'packages/bus/tests/*.test.mjs'`,
   `node --test 'packages/business/tests/*.test.mjs'`,