the two messages are an obligation in the brief, not advice in the skill

A commander read the skill section on telling the owner and did not mention it in
its read-back, so the owner would have had to remind it — which is the failure, not
the remedy. Doctrine in the skill is advice a commander may or may not weigh;
the brief is the prompt and always arrives. Same lesson as moving the output
constraints there earlier tonight.

So the brief now states it as owed: two messages per event, one when the thing
happens and one when the work is done, and never having to be asked. The skill
still carries the how.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

src/workspaces/officerdev/src/apps/CommandHQ/CommandHqDetail.tsx

@@ -96,6 +96,10 @@ const startBrief = (name: string): string =>
     'If you CAN — say what you understood, in your own words, and ask me to confirm or correct it.',
     'If you CANNOT — ask me what you should be watching for here. One question, and wait.',
     '',
+    'Once you are running, you owe me exactly two messages here per event, and I should never have to ask',
+    'for them: one line when the thing you watch for happens, and a short report when the work is done.',
+    'The job panel is not where I read things. The skill explains how to wake this conversation yourself.',
+    '',
     'Either way, say it plainly. No headings, no bullet points, no file paths, no commit hashes, no tag',
     'names. Do not open with "Oriented" and do not tell me you verified anything — I asked you to look,',
     'so saying you looked is not news. Length is whatever the answer honestly needs and no more.',