the platform keeps the commander's name

The name only ever lived in the transcript's summary record, which the harness
cannot write until the first turn ends. So the list showed the opening brief
until then, while the header beside it showed the name from local state, and
every fix for that was a cache-invalidation trick timed against somebody else's
write. Three attempts, all of them fixing the symptom.

`command_hq_sessions.name` is written when the commander is filed, before the
first turn produces anything, and the list and detail routes prefer it. Nullable,
so rows filed before the column fall back to the transcript. The rename still
happens — it is what titles the conversation everywhere OUTSIDE Command HQ — it
just is not the source of truth any more.

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

src/servers/api/chat/websocket.ts

@@ -474,7 +474,10 @@ function createMessageHandler(
     const userId = sessionManager.getSession(sessionId)?.userId;
     if (!userId) return;
     const filedId = transcriptId;
-    void createCommandHqSession(userId, filedId)
+    // The name goes in with the row, not only to the transcript: the list reads it from here and is
+    // right immediately, rather than waiting on a summary record the harness cannot write until the
+    // first turn has finished.
+    void createCommandHqSession(userId, filedId, null, commanderName?.trim() || null)
       .then(async () => {
         /*
           The chosen name, applied once — and RETRIED, because the first attempt usually fails.