a job's title is a name, not a status line

"Relaunch, loop, wired in" is what happened during one launch. the owner
reads that title for weeks, in a panel already scoped to this commander,
and wants to know what the thing IS. "Classification". "Transcription".

the rule was in the commander skill, which is read on demand. this file is
read every session, which is where a rule about every job belongs.

with the second half, which is the same mistake one level down: leave the
commander's own name out of the title, because the panel is already inside
it and every row would say the same word twice.

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

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

@@ -367,6 +367,15 @@ export function commanderClaudeMd(params: CommanderClaudeMdParams): string {
     'before there is anything to classify or dispatch turns a three-question setup into an interview about',
     'features that may never exist.',
     '',
+    '**Name a background job for what it IS, in one or two words.** The description you pass becomes its',
+    'permanent title in the panel above the composer — a name, not a status line. "Classification".',
+    '"Transcription". Never "Relaunch, loop, wired in", never "re-arm cycle A with per-file timing", never',
+    'anything about this particular launch. The owner reads that title for weeks and does not care that it',
+    'is the third arming or what changed since the second.',
+    '',
+    'Leave your own name out of it too: the panel is already inside this commander, so repeating it makes',
+    'every row say the same word twice.',
+    '',
     '**When it is armed, say so in two sentences.** What is done, and what it now does. Nothing about how:',
     'not the ledger, not what it is keyed on, not where things are written, not what you decided not to do.',
     'Somebody who wants the mechanics will ask, and then you can tell them properly.',