Infrastructure: Implement neutral Windows desktop application ownership and containment #4447

Current status - 2026-11-07

Blocked by F2 #4442's exact ownership/claim contract (in #4463). Windows Fabric and Win32 Paper remain distinct qualification endpoints.

The follow-up survivor/cleanup evidence proves bounded exact-resource reconciliation and attached-app preservation, not neutral supervisor-owned launch or descendant containment. Remaining work: exact AUMID/executable/REX incarnation and process-start/session evidence; PID reuse and ambiguity rejection; supported Job Object/descendant containment; uncontained/restricted cases explicitly Unsupported or fenced; and cross-service application/input ownership qualification.

Launch-capable comparison remains Partial because only attach-only discovery was exercised. Windows physical foreground acquisition remains Fail in #4441; do not classify a semantic activation or hosted physical-input skip as proof. Do not place externally attached applications in owned termination groups.

Goal

On Windows Fabric and Win32 Paper, the harness has no neutral application ownership model: Storybook attaches by a verified AUMID or REX executable, and descendant processes are not contained. Add exact identity, interactive-session checks, and supported containment for supervisor-owned applications.

Part of #4435 (plan item F10-W).

Scope

• Owner: Windows lifecycle backend.
• Paths (under packages/agentic/): neutral Windows application ownership adapters in desktop-test, the driver's Windows authority and native support as needed, and packaged and Win32 contracts.
• Support exact AUMID and executable or REX identities, process start-time and interactive-session checks, identity re-resolution, and supported descendant containment.
• Native helper changes follow the implement-native-component overlay and desktop-driver/native/PROTOCOL.md.

Dependencies

• Blocked by: F2 Infrastructure: Implement settled desktop lifecycle supervision and fenced ownership records #4442. Independent of F10-M Infrastructure: Implement neutral macOS desktop application ownership and identity recovery #4446.
• Enables: the retained supervisor-launched app option in F11 Infrastructure: Add scoped runner grants and drain-confirmed desktop controller handoff #4448.
• Parallel with: F10-M, F5 Infrastructure: Authorize and settle every controlled Storybook mutation entrance #4443, and F6 Infrastructure: Tighten Storybook manifest provenance and native helper trust handoff #4445.

Acceptance

• PID reuse, ambiguous identity, and unknown evidence fail closed.
• Attached applications are never assigned to owned termination groups.
• Job Object restrictions or uncontained descendants are reported as explicit unsupported or fenced outcomes.
• Windows Fabric and Win32 Paper are qualified separately on interactive desktops.

Validation

• Iterate with focused yarn test <name> in each changed package, then run its yarn format, yarn lint, yarn build, and yarn test. Finish with yarn clean-lage-cache then yarn lage buildci; run yarn lage test-links --verbose --grouped after markdown changes.
• Add a patch changeset for each changed published package. Update the owning references/current-status.md rows (done, work in progress, unsupported) and affected README/AGENTS guidance in the same change.
• Native, provider, or process-topology changes need matching-OS native contracts and the affected consumer lane. JavaScript tests and bundles do not qualify native behavior; hosted capability skips are not passes. Report each check as passed, failed, skipped, not run, or unsupported.

Evidence

• Current state: the Windows / Win32 row of "Full-submission checklist" in packages/agentic/desktop-test/references/current-status.md.
• Retired plan: driver-next.md at 0569e1b86, section 8 (F10-W).