[brennanb2025]

	Files	Added	Deleted	Net
Test	4	$\color{#1a7f37}{\Huge{\mathbf{+}}}$​260	$\color{#cf222e}{\Huge{\mathbf{−}}}$​1	$\color{#1a7f37}{\Huge{\mathbf{+}}}$​259
Prod	16	$\color{#1a7f37}{\Huge{\mathbf{+}}}$​177	$\color{#cf222e}{\Huge{\mathbf{−}}}$​50	$\color{#1a7f37}{\Huge{\mathbf{+}}}$​127

ELI5

The planned desktop flow creates a workspace and starts its agent through one host operation. The host can announce that the workspace is open before that operation finishes delivering the first prompt. Without the launch identity, the window cannot tell which pending creation owns that announcement, so it can open an extra empty shell or show a workspace after the user has moved elsewhere.

This PR adds that identity to the existing announcement. It prepares the window to let the creating launch decide whether to show the workspace and supply its first tab. Existing desktop controls remain unchanged: this PR has no production caller registering that ownership yet. It stays draft and must land together with the companion creation flow, which waits for #26007.

What Changed

• The existing workspace-activation event gains optional launch: { operationId }. The host includes it only for a desktop-owned agent launch that explicitly opens its created workspace.
• A window with a matching registered launch hands the workspace ID to that launch. Without an owner, it uses the existing activation path and suppresses an unnecessary fallback shell while preserving explicit setup, agent startup, and configured default tabs.
• Phone and command-line launches do not carry the identity. Older clients ignore the optional field; a new client receiving an event without it follows the existing path. Local, SSH, and folder-workspace creation keep their existing execution paths.
• The original CI failure came from the creation module exceeding its line limit. The setup-result description now lives in the existing setup module, with the same values and precedence; no line-limit suppression was added.

Why

Adding one optional field to the existing event reuses the host's activation channel and the window's existing initial-tab behavior. A second notification channel would duplicate the same creation event. The launch identity is temporary window ownership, not another persisted copy of the workspace.

The first owner must preserve the full activation work, including setup and configured tabs, release ownership when the launch settles or is abandoned, and respect navigation away. Those checks belong to the companion flow. This PR does not prove recovery after a missed notification: a successful final reply includes the workspace ID, but a failure before the final surface is published is not guaranteed to do so. A durable created-workspace checkpoint remains separate follow-up work (#26060).

A desktop connected to another Orca runtime remains a paired client there and does not receive the desktop-owned marker. Its current behavior is preserved; expanding that ownership needs explicit client identity handling.

Linked Issue

Step 3 of the agent-launch plan, preparation for the desktop workspace-and-agent creation flow. The companion producer waits for #26007; this PR is not being readied alone.

Visual Proof

QA deferred to the combined 4a+4b run. This PR has no production owner yet, so the new navigation and first-tab behavior cannot be exercised here. No main-versus-PR tab-strip comparison or navigation-away result is claimed, and no screenshots are presented as proof. The Windows setup attempt was stopped when its driver proceeded through a pending launch hold; that evidence is not accepted as functional QA.

Testing

• Scoped Node and renderer typechecks passed on the merged tree.

• Seven named test files passed 28 tests, covering launch metadata, renderer owner/fallback handling, local setup receipts, startup, folder creation, remote creation, and execution-host routing.

• Six selected runtime creation/activation cases passed.

• Formatting, changed-code quality, lint, and PR Checks passed at f172e6f960e13590e7f8abdfad2cf96cef956387, including cross-version wire compatibility.

• Source review covered the optional-field consumers in current/prior mobile code and desktop runtime streams. Native mobile, WSL, Linux, and live SSH ownership behavior were not exercised. Full ownership and recovery QA waits for the first producer.

• I manually tested the new ownership flow locally

• Automated tests added/updated

Author: @BrennanKB5

[brennanb2025]

The planned desktop workspace-and-agent flow receives the workspace activation before the launch finishes delivering its first prompt. This change adds the launch identity to that existing event so its creating window can own navigation and the first tab; current desktop entry points remain unchanged because the production owner is in the companion flow.

Fixed the CI line-limit failure by moving setup-result construction into the existing setup module, preserving behavior. The original aggregate verification failure was downstream of that lint failure. Fresh host, renderer, architecture, and final readiness reviews found no additional reachable PR-caused regressions; scoped Node/renderer typechecks, 34 selected tests, lint/code-quality checks, and PR Checks, including cross-version wire compatibility, passed on f172e6f.

QA deferred to the combined 4a+4b run. This PR has no production owner yet, so the new navigation and first-tab behavior cannot be exercised here. No main-versus-PR tab-strip comparison or navigation-away result is claimed, and no screenshots are presented as proof. The Windows setup attempt was stopped when its driver proceeded through a pending launch hold; that evidence is not accepted as functional QA.

The first producer must preserve setup and configured tabs, release ownership, and prove navigation-away and recovery behavior. A successful final launch reply does not guarantee recovery from a failure before surface publication. Live SSH and native-mobile ownership QA are deferred to that combined flow; optional-field source compatibility was reviewed here. Review has converged, but this remains draft and must land with the companion flow after #26007.