Infrastructure: Implement neutral Windows desktop application ownership and containment

未關閉
  • 哪裡不對？
#4,447 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
30/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
typescript
領域
desktop, testing-qa

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

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).
主要語言
TypeScript
星號
1.4k
分支
179
平均合併
1 天 8 小時
30 天內合併 PR
62

環境準備

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

microsoft/fluentui-react-native 的其他 Issue

查看 microsoft/fluentui-react-native 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。