Repository navigation
Description
Current status - 2026-11-09
Unblocked and partly implemented. F2 #4442 is closed (#4463). Windows Fabric and Win32 Paper remain distinct qualification endpoints.
Delivered on main by #4469 (ledger):
- Job Object containment. The helper places applications it launches in a Job Object. On Win32 (REX FluentTester), killing the helper ended
ReactTest.exewithin 5 s (Pass,job-object). - Packaged launches. A packaged Windows launch is reported
uncontained. It survived helper death, its claim stayed fenced, and the survivor was ended manually after its identity was checked. - Launch-capable discovery. Now a Pass on both endpoints (runs
0876d93b-f689-47e5-8379-4c09d95d6cc9and101c5916-027d-40cf-a26a-163535df4c03), replacing the earlier Partial. Committed Storybook targets remain attach-only. - Physical foreground and input. Passed in a connected session (Infrastructure: Live-qualify the desktop driver and MCP foundation on macOS, Windows, and Win32 #4441).
Remaining work:
- Exact AUMID/executable/REX incarnation and process-start/session evidence; PID reuse and ambiguity rejection.
- Containment for packaged launches, or keep them explicitly
uncontainedand fenced. - Name launched applications, especially uncontained ones, in the claim. Today neither the claim nor the settlement journal names the survivor; recording launched applications as claim resources belongs with F11 Infrastructure: Add scoped runner grants and drain-confirmed desktop controller handoff #4448.
- Cross-service exact-application exclusion and input-mutex qualification, carried over from F2 Infrastructure: Implement settled desktop lifecycle supervision and fenced ownership records #4442.
Windows hard-terminates non-detached children when their owner crashes, so the three cooperative crash-disposal contracts stay skipped there. 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 indesktop-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-componentoverlay anddesktop-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 itsyarn format,yarn lint,yarn build, andyarn test. Finish withyarn clean-lage-cachethenyarn lage buildci; runyarn lage test-links --verbose --groupedafter markdown changes. - Add a patch changeset for each changed published package. Update the owning
references/current-status.mdrows (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.mdat0569e1b86, section 8 (F10-W).
Activity
feat(desktop): extend exact application ownership to Windows
feat(desktop-test): qualify Windows application ownership and contain…