Repository navigation
Description
Status: Done
Delivered by #4469 (Job Object containment, launch-capable discovery), #4494 (exact Windows application ownership and containment, built on the neutral application host and application resources from #4492), and #4498 (Windows activation and Win32 secondary content windows).
- Exact identity: packaged AUMID or canonical executable/REX incarnation with native 100-ns creation time and session; stale pins, mismatches and ambiguous candidates are refused.
- Containment: unpackaged and REX launches use a Job Object; packaged activation is explicitly
uncontained, recorded in the claim as an application resource, and fenced; external attachments stay external. - Cross-service exclusion by an application semaphore plus a separate physical-input mutex. Native qualification at
da89fe9bc: 11/11 actual-endpoint cases on Windows Fabric (packaged) and Win32 Paper (REX), reported separately, plus 6/6 provider cases; 5/5 repeats and 3/3 concurrent pairs per endpoint.
Residuals (not acceptance items) live in open issues: actual kernel PID recycling, the shared-PID packaged-activation race, arbitrary uncontained descendants and mixed Storybook-graph recovery in #4451; hosted selection of the actual-endpoint suite and physical mutex case in #4349; Windows qualification of the retained supervisor-launched app option in #4449 and #4441.
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
- Depended on: F2 Infrastructure: Implement settled desktop lifecycle supervision and fenced ownership records #4442 (closed, Desktop driver: typed resources, process lifelines, story lifetimes, exclusive agent ingress, and native qualification runbook #4463). Independent of F10-M Infrastructure: Implement neutral macOS desktop application ownership and identity recovery #4446.
- Enables: the retained supervisor-launched app option, now tracked in F9 Infrastructure: Convert Storybook lifecycle takeover into desktop-test resource contributions #4449 (F11 Infrastructure: Add scoped runner grants and drain-confirmed desktop controller handoff #4448 delivered the generic handoff).
- 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 (#4494)
- Attached applications are never assigned to owned termination groups (#4494)
- Job Object restrictions or uncontained descendants are reported as explicit unsupported or fenced outcomes (#4494)
- Windows Fabric and Win32 Paper are qualified separately on interactive desktops (#4494)
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 affected topic section and its status-overview line in the owning
references/current-status.md, and affected README/AGENTS guidance, in the same change. Per-run evidence lives in the pull request description or an issue comment; each package'sreferences/current-status.mdkeeps a status overview, stable topic sections, and only the latest result per native endpoint with a link. - 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
- Qualification: the #4494 pull request description; the latest per-endpoint results are in the Windows Fabric and Win32 Paper sections of "Native qualification" 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…
JasonVMo commentedon Nov 16, 2026
Closing as completed. Windows application ownership and containment landed in #4469 and #4494 (built on the neutral application host from #4492), with Windows activation and Win32 secondary windows in #4498.
Acceptance: stale PID pins, mismatches and ambiguous candidates are refused; external attachments are never placed in owned termination groups; packaged activation is explicitly
uncontained, recorded in the claim as an application resource and fenced, while REX launches use a Job Object; Windows Fabric (packaged) and Win32 Paper (REX) were qualified separately on interactive desktops (11/11 actual-endpoint cases and 6/6 provider cases, with 5/5 repeats and 3/3 concurrent pairs per endpoint). Hosted CI passed but did not run the actual-endpoint suite, so it is not the qualifier. The claim-naming note in #4494 is superseded by the application resources from #4492.Residual items moved to open issues: