Infrastructure: Implement neutral Windows desktop application ownership and containment

Aperta
  • Qualcosa non va?
#4,447 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
30/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
desktop, testing-qa

Direzione di ricerca

Start with the Windows / Win32 row in packages/agentic/desktop-test/references/current-status.md and the native protocol at packages/agentic/desktop-driver/native/PROTOCOL.md; the issue gives no exact adapter or test filenames. F2 #4442 must land first. Done means implementing and separately qualifying Windows Fabric and Win32 Paper ownership, identity checks, and supported containment, with matching OS native contracts and status and guidance updates.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Platform: Win32 Platform: Windows Status: Blocked

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 #4442. Independent of F10-M #4446.
  • Enables: the retained supervisor-launched app option in F11 #4448.
  • Parallel with: F10-M, F5 #4443, and F6 #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).
Lingua principale
TypeScript
Stelle
1.4k
Fork
179
Merge medio
1g 8h
PR unite (30g)
60

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/fluentui-react-native

Tutte le issue di microsoft/fluentui-react-native

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.