Files
orca/src
Neil 958de6c246 fix(cloud): V3-01b a held structured chat on Orca Cloud keeps its hold across a restart; DUP-EXPIRED-STRIP
- cloud-structured-held-launch-memory: one record per held structured chat
  (session, workspace, environment, agent), per Orca profile; never prompts
  or secrets; bounded, ages out.
- holdStructuredCloudLaunch remembers a chat while it holds and forgets it on
  settle; a chat with a record holds as restored (a failed or covered read
  waits as awaitingStart, never creates signed out); a launch joins a hold
  already placed for its key (joinCloudAgentHold) instead of holding twice.
  In-session launches are unchanged.
- cloud-held-launch-resume: at the host subscription, each held chat's hold is
  put back as soon as its tab is in the store, whatever becomes of its
  launch's retry (probes that throw leave the hold and strip up). If no retry
  joined it, Start retries the launch once and Cancel abandons it.
- While a chat is held on its cloud strip, the host's not-signed-in verdict is
  the strip's to explain (useCloudHeldChatUnavailable in the structured pane
  notices); unheld chats keep the generic notice.
- DUP-EXPIRED-STRIP: CloudRunningStripPortal yields to a tab-key hold too, so
  a host-published held strip never stacks with the running strip.
2026-11-12 13:21:32 -08:00
..