test(mothership): lock the queue upgrade path and tighten held waits

- rehydrate rows for the production shape (retryRequired: false, no hold)
  and for a queue already in the new shape
- the offline-hold waits check hold === 'online' instead of any hold
- the one-lookup comment names where the one-hop invariant is enforced

Author: waleedlatif1

apps/sim/app/workspace/[workspaceId]/home/hooks/use-chat.dom.test.tsx

@@ -3480,7 +3480,7 @@ describe('useChat remount send recovery', () => {
 
       await waitFor(() => state.postBodies.length === 1)
       await waitFor(
-        () => useMothershipQueueStore.getState().queues[history.id]?.[0]?.hold !== undefined
+        () => useMothershipQueueStore.getState().queues[history.id]?.[0]?.hold === 'online'
       )
 
       const queued = useMothershipQueueStore.getState().queues[history.id] ?? []
@@ -3575,7 +3575,7 @@ describe('useChat remount send recovery', () => {
       await act(async () => {
         await first.getResult().sendMessage('First message, sent offline')
       })
-      await waitFor(() => allQueuedMessages().some((message) => message.hold !== undefined))
+      await waitFor(() => allQueuedMessages().some((message) => message.hold === 'online'))
       first.unmount()
 
       const second = renderUseChat()
@@ -4352,7 +4352,7 @@ describe('useChat remount send recovery', () => {
         await first.getResult().sendMessage('Held while I was elsewhere')
       })
       await waitFor(
-        () => useMothershipQueueStore.getState().queues[history.id]?.[0]?.hold !== undefined
+        () => useMothershipQueueStore.getState().queues[history.id]?.[0]?.hold === 'online'
       )
       first.unmount()
 

apps/sim/stores/mothership-queue/store.dom.test.ts

@@ -21,6 +21,13 @@ describe('useMothershipQueueStore rehydration', () => {
               { id: 'for-network', content: 'b', retryRequired: true, heldUntilOnline: true },
               { id: 'retrying', content: 'c', sendRetries: 2, notBefore: 1_000 },
               { id: 'plain', content: 'd' },
+              { id: 'main-shape', content: 'e', retryRequired: false },
+              {
+                id: 'new-shape',
+                content: 'f',
+                hold: 'online',
+                retry: { attempt: 1, notBefore: 5 },
+              },
             ],
           },
         },
@@ -35,6 +42,8 @@ describe('useMothershipQueueStore rehydration', () => {
       { id: 'for-network', content: 'b', hold: 'online' },
       { id: 'retrying', content: 'c', retry: { attempt: 2, notBefore: 1_000 } },
       { id: 'plain', content: 'd' },
+      { id: 'main-shape', content: 'e' },
+      { id: 'new-shape', content: 'f', hold: 'online', retry: { attempt: 1, notBefore: 5 } },
     ])
   })
 

apps/sim/stores/mothership-queue/store.ts

@@ -147,7 +147,10 @@ export function liveQueuePosition(
   aheadIds: readonly string[]
 ): { chatKey: string; index: number } {
   const { migratedTo, queues } = useMothershipQueueStore.getState()
-  /** One lookup: only a new-chat key moves, and only to its chat's key, which never does. */
+  /* One lookup: only a new-chat key moves, and only to its chat's key, which never
+     does. \`useChat\` migrates only from its pending sentinel key to the resolved chat
+     id (the chat-resolution effect and the detached chat resolution), never from a
+     chat key. */
   const migration = migratedTo[chatKey]
   const key = migration?.key ?? chatKey
   const ahead = new Set([...aheadIds, ...(migration?.ahead ?? [])])