a commander's children stay out of the chat list

/chat already hid commanders. it did not hid their spawned agents, and a
commander that fires once an hour spawns one per run — each with its own
transcript, titled after whatever its first message happened to be. one
commander had thirteen sessions under its directory, twelve of them reading
"Read /home/.../procedures/classify-t…". a loop's bookkeeping, filling the
list you keep conversations in.

listCommandHqOwnedSessionIds is the union: commanders plus their children.
kept separate from listCommandHqSessionIds rather than replacing it,
because a CHILD is not a commander — isCommander has to stay false for one
or the composer would offer it the handoff watcher.

/chat/live is deliberately untouched. it is the "what is running right
now" panel, and a spawned agent that is still going belongs there — hiding
it would mean an agent running with nowhere showing it.

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

src/servers/api/chat/chat.ts

@@ -8,6 +8,7 @@ import {
   getChatSessionModel,
   getChatSessionModels,
   listCommandHqSessionIds,
+  listCommandHqOwnedSessionIds,
   getChatNotifyPreference,
   getChatNotifyPreferences,
   setChatNotifyPreference,
@@ -156,7 +157,7 @@ chatRouter.get('/sessions', async (ctx) => {
     that excludes commanders has nothing to say about which of its rows is one. `/chat/live` is where the
     flag is real, because that route keeps both kinds.
   */
-  const filed = await listCommandHqSessionIds(user.id).catch(() => new Set<string>());
+  const filed = await listCommandHqOwnedSessionIds(user.id).catch(() => new Set<string>());
   const sessions = merged.filter((s) => !filed.has(s.id));
 
   /*