Infrastructure: Complete Desktop Driver production release qualification
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- node.js, react-native, typescript
- Domain
- ci-cd, desktop, release, testing-qa
Research direction
Start with packages/agentic/desktop-driver/PLAN.md, then read README.md and references/ci-integration.md to understand the supported targets, release gates, and evidence model. Qualification requires authoritative Windows and macOS sessions, compatibility and security checks, artifact validation, sustained reliability evidence, and completion of every applicable V1 plan item without promoting deferred work.
Written by the indexing model from the issue text.
Description
Goal
Complete authoritative native qualification and release hardening for the public Desktop Driver after the delivered implementation/integration milestones #4257 and #4258. Parent: #4275.
Status - 2026-10-01
Open; native providers and repository integration are complete, production release qualification is not. #4257 was explicitly closed as an implementation milestone in its September 3 completion comment. This issue gives the remaining release work a distinct open tracker instead of hiding it in a closed issue or only in a package plan.
The authoritative remaining-work inventory is Desktop Driver PLAN.md. Versioned packages and successful hosted jobs do not by themselves satisfy its release gate.
Acceptance criteria
- Complete the required Windows Fabric/Win32 physical click, keyboard, wheel, full lifecycle, process/input recovery, live DPI/capture, and sustained-provider qualification in the plan on authoritative interactive sessions.
- Complete stable Apple Development signing, grant/revoke/regrant/restart TCC matrix, managed auto-logged-in Aqua CI, PPPC/MDM policy, signing rotation, clean-machine install/upgrade/rollback, and explicit optional Screen Recording behavior.
- Freeze/test native wire and feature compatibility across Node/macOS/Windows/Win32 and publish verified OS, architecture, toolchain, runtime, and capability support.
- Complete the plan's focused security review, performance/timeout budgets, long-lived resource bounds, wheel conversion decisions, and remaining cache/multi-consumer/corruption/in-use-artifact qualification.
- Validate the packed public artifact, native-source completeness, narrow runtime dependencies, platform import policy, external-consumer/read-only package operation, and source builds without install scripts, Appium, or implicit helper downloads.
- Retain at least 100 representative executions per endpoint over 14 days, at least 99% infrastructure success, zero leaked app/helper processes or unreleased-input incidents, and complete failure/helper metadata.
- Required capabilities are actually available; missing required authority and all-skipped runs cannot satisfy release proof. Attached apps survive, owned resources clean up, and cancellation/helper failure release owned input.
- Complete publishing/changeset gates after native qualification; publish the final supported operating model and close every remaining V1 plan item with durable evidence.
- Decide whether a distributed macOS prebuilt is required. If selected, complete its external trust/signing/notarization/stapling/install/rotation gates; otherwise record a source-build-only decision without adding unnecessary distribution machinery.
Scope and dependencies
Coordinate #4347 (regression parity), #4343/#4346 (accessibility), #4349 (authoritative CI/reliability), #4348 (capture), #4342 (reporting), and #4344 (native catalog). Shared qualification evidence can satisfy multiple gates but must identify the tested revision/cohort.
Explicitly deferred items in the package plan (extra platforms/concurrency, persistent broker, MCP adapter, legacy E2E migration, minimized-window policy) are not silently promoted into V1. Visual comparison delivery remains #4328.
Evidence
- Dominant language
- TypeScript
- Stars
- 1.4k
- Forks
- 179
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 30
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/fluentui-react-native
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/fluentui-react-native#4174 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
microsoft/fluentui-react-native#4343 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/fluentui-react-native#4344 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
microsoft/fluentui-react-native#4346 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/fluentui-react-native#4347 ·
Maintainers usually reply within 1 day
All issues in microsoft/fluentui-react-native
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
MystenLabs/MemWal#1085 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
📕documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
db-ux-design-system/core-web#8343 ·
Maintainers usually reply within 1 day
-
enhancement triage/needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
heygen-com/hyperframes#4944 ·
Maintainers usually reply within 1 day
-
ai-driven-qa bug claude
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
linagora/twake-calendar-frontend#1493 · 1 comment ·
Maintainers usually reply within 1 day