Resume: follow-ups for #6 and #30 after the 2026-10-22 sync #41

Smaller resume follow-ups left by the 2026-10-22 sync (#38). Each item says what the sync did and what is still open.

#6, auto-resume after a host restart

• Native-chat-owned conversations. feat(resume): auto-resume an agent session after a host restart #6 can pick a conversation that a native chat owns and resume it in a terminal, giving two writers. Upstream refuses this (fix(session-history): refuse desktop resumes of chat-owned conversations stablyai/orca#28229, Refuse chat resume until terminal writers have exited stablyai/orca#29242). Fix: skip candidates whose session has structuredSession.
• SSH panes. These no longer auto-resume. Upstream deleted SSH relay scanning, so an ssh: scope returns a host issue row and the pane safely stays a plain shell. Decide whether to scan through the managed orcad runtime that serves the pane.
• Host platform. Optionally replace the fork's hostPlatform with upstream's remotePlatform (fix(agent-resume): quote resume commands for a Windows SSH host's own shell stablyai/orca#29409), which also covers WSL and cmd.exe.
• Coverage stamp on cache hits. A cache hit stamps the requested depth, even when the stored answer had a tighter one. feat(resume): auto-resume an agent session after a host restart #6 never hits this, because its unlimited requests come back untouched.

#30, host resume of a re-created pane

• Managed-orcad SSH hosts. The fork's SSH skip tests workspace.connectionId, which a managed-orcad catalog sets to null. So a fork-built orcad now runs the host resume on managed SSH hosts. This is inferred from the code and untested; decide whether that is wanted.
• Automatic-restore pauses. The no-record fallback declares no restore intent, so it ignores an operator, unclean-death or pressure pause, while upstream's record resumes wait. This keeps the "daemon replaced" journey working. Decide whether it should wait too.
• Native-chat adoption. The terminal-loss remnant drops its process presence, so upstream's writer check (Refuse chat resume until terminal writers have exited stablyai/orca#29242) refuses "Resume in New Native Chat" and chat adoption until the pane is re-created. A tested alternative is to keep the presence marked ended: it passes the fork's 117 related tests. Its cost is that it marks a process ended that was never proven ended, so later hooks from that process are dropped. The alternative, in server-retained-identity.ts:

  -  const { agentPresence: _agentPresence, ...terminalIdentity } = resumeIdentity
  +  const { agentPresence, ...terminalIdentity } = resumeIdentity
     return {
       ...terminalIdentity,
  +    ...(agentPresence ? { agentPresence: { ...agentPresence, ended: true as const } } : {}),
       providerSessionOnly: true,

• Layout-owner build. In upstream's dark layout-owner build, the fallback does not resume while a window is attached; main-written records cover that case. Recheck when upstream switches the build on.
• Legacy records and [Bug]: Creating a Claude tab from mobile spawns it on the desktop, then reaps it ~10s later — mobile tab creation broken stablyai/orca#7587. The fresh-launch suppression also applies to panes with an originless legacy record. Narrowing it is a one-token change.

Hardening nits

• resolvePaneScopedTuiAgent reads …?.identity.agentType without guarding identity. Upstream guards its sibling reads.
• When upstream does its P5b-2 retyping, move fix(session): treat an unprovable connectionId as no host, not as ssh #5's folderWorkspaces read in workspace-session-host-persistence.ts to the typed selector and drop the raised workspace-record-read baseline.