Skip to content

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

Closed

Description

@JasonVMo

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 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

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 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 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's references/current-status.md keeps 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.md at 0569e1b86, section 8 (F10-W).

Activity

  1. JasonVMo commented on Nov 16, 2026

    @JasonVMo
    ContributorAuthor

    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:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions