a commander's bound is a rule, not a list

the allow list shipped an hour ago was a snapshot. plugin permissions
register at mount, so a plugin installed after a commander was created was
missing from its list and failed as a bare 403 with nothing saying why —
and every future thing a commander is meant to do is exactly that shape:
notify a device, send mail, spawn a sub-agent, hand a transcription to an
idle one, reach a plugin that does not exist yet.

so a credential now narrows two ways, and both only subtract:

  permissions   an ALLOW list. exact, a snapshot. right for a credential
                with one job.
  excludedKinds kinds it may never reach, resolved against the LIVE
                registry on every request. right for a credential whose
                job is open-ended.

a commander gets the second: every kind except admin. bounded away from
installing plugins, managing users and roles and changing server settings,
forever — and open to everything the platform learns to do, with nothing
to re-issue. still intersected with the account, so for a member it
narrows itself against their role.

verified against the running server with a commander-shaped key: tasks,
notify, file-browser and the transcribe PLUGIN all reach their routes;
/api/users, /api/plugins and /api/roles are 403. the plugin case is the
one an allow list could not have passed — it was mounted long after any
key was minted.

the commander's CLAUDE.md says what it cannot do in the rule's own terms,
and that a 403 is an answer rather than a problem to route around.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Officer-Session: 656f5c85-e49a-4f1f-b9f3-042a04b4d043

src/servers/api/command-hq/directory.ts

@@ -88,9 +88,13 @@ export function commanderClaudeMd(params: CommanderClaudeMdParams): string {
           '`POST /api/tasks/<dirName>/run` runs one and returns what it did — one reviewed definition on',
           'disk instead of a re-implementation living in a loop nobody reads.',
           '',
-          'The credential is narrowed and revoked when this commander is deleted. A 403 is an answer, not a',
-          'problem to route around: it means this commander was not given that, and the owner is the one who',
-          'decides otherwise.',
+          'It reaches everything the platform does EXCEPT administering it — installing plugins, managing',
+          'users or roles, changing server settings. That holds for features added later too: the rule is',
+          'resolved per request rather than frozen into a list, so a plugin installed next year is already',
+          'covered without this commander being re-issued.',
+          '',
+          'A 403 is an answer, not a problem to route around. It means this commander was not given that,',
+          'and the owner is the one who decides otherwise. Say so rather than finding another way in.',
           '',
         ]
       : [