Skip to content

Infrastructure: Live-qualify the desktop driver and MCP foundation on macOS, Windows, and Win32 #4441

Open

Description

@JasonVMo

Current status - 2026-11-16

Partial qualification; not globally blocked. Continue the available cases now. Per-run evidence (command, selection, counts, cleanup, artifact locator) lives in the pull request descriptions linked here or in issue comments. Each package's references/current-status.md keeps only the latest result per endpoint with a link. F1-F6 (#4436, #4442, #4444, #4437, #4443, #4445), F10-M #4446, F10-W #4447, F11 #4448 and F16 #4467 are closed as implemented; their unqualified macOS and Windows/Win32 native residuals are consolidated in the checklists below.

Endpoint Latest result Remaining
macOS Fabric #4493 (source 141b88b4b): strict 3/0/0, preservation 1/0/0, lifecycle 10/1/0 (physical Checkbox click refused), smoke 223/2/0 (Accordion focus click). #4500 fixed the physical-input defects: local physical smoke 343 passed (+3 declared unsupported), advisory hosted physical job 343 passed (0 failed). Ownership and accessible lanes at 16558610f (#4492). Checklist below
macOS Paper #4493: lifecycle 14/4/0, input 4/1/0, smoke 223/2/0. #4500: same reproductions pass; local physical smoke 343 passed (+3 declared unsupported). Paper semantic activation is Unsupported by the provider. Checklist below
Windows Fabric #4469 (fec94cec4, console connected, 2026-11-08): Checkbox and Callout physical smokes 203/203, receipts 2 and 3. #4498: physical secondary window with confirmed focus, activation-unsupported refusal before dispatch, MCP physical clicks (unlocked remote RDP session, not the console). #4494: ownership consumer cases 11/11 locally. Checklist below
Win32 Paper #4469 (fec94cec4): Checkbox and Callout physical smokes 177/177, receipts 2 and 3. #4498: secondary tool popup registered, injected fresh-preview fencing passed, MCP physical clicks passed (RDP). #4494: ownership consumer cases 11/11 locally. Checklist below

Landed: #4469 (Windows ownership and physical input), #4490 (provenance), #4491 (attach-only handoff), #4492/#4494 (application ownership), #4493, #4496 (direct story selection), #4498, #4500 (macOS physical postconditions and advisory physical lane). Windows Fabric and Win32 Paper MCP measurements (discovery 4,691 tokens / 20,277 bytes on each; click p50 299.107 ms Windows, 308.003 ms Win32) are in #4498. Launch-capable discovery passed on Windows and Win32; committed Storybook targets remain attach-only. Real physical console Ctrl+C of serve --agent passed on Windows Fabric and Win32 Paper at b1bbb26df (four SendInput key events in an unlocked remote RDP session; exit codes 0/0/0, terminal passed report, claim released, descriptor withdrawn, #4491); the earlier claim-stays-active failure was repaired in #4478. Hosted skips are not passes, and none of this requalifies later main-merge SHAs.

Unsupported: Windows/Win32 doctor --permissions; Win32 production-bundle Metro reload; macOS Paper semantic activation. Conservative by design: failed-cleanup claims stay fenced and require exact-resource/operator reconciliation; there is no automatic reclaim or mutation replay. Packaged Windows launches are uncontained and fenced (accepted limit from #4447). Protected story args remain refused.

Goal

The #4434 foundation (MCP lifetime handling, story-change settlement and quarantine, protected args refusal, failed-cleanup claim retention, and launch-mode discovery) was validated by deterministic fake-host tests and hosted CI. Requalify it through real descriptors and native helpers on each endpoint, and record the measurements that are still missing (see the checklists).

Part of #4435 (plan item F15).

Scope

  • Through the real descriptor path on macOS Fabric, macOS Paper, Windows Fabric, and Win32 Paper, qualify:
    • MCP same-port service restart and replacement, grant revocation, dispose during open, failed delete, ambiguous create, and resource invalidation;
    • unknown-effect story quarantine and its recovery, and story-args-unsupported on protected services;
    • failed-cleanup workload-claim retention and launch-mode discovery.
  • Windows and Win32: an interactive rerun of the current input and capture native contracts; 200% and mixed DPI; minimized and negative-origin windows; lock, RDP, and elevation transitions; popups; capture cancellation; and process-tree containment and ownership checks.
  • macOS: live failed-cleanup and service-restart cases, Paper separately from Fabric, and exact attached-app preservation.
  • Record the remaining MCP measurements (see the checklists) using the documented method; discovery cost is already recorded on all four endpoints.
  • Serialize physical-input runs per interactive desktop. Separate machines can run endpoints in parallel.

Remaining gaps by endpoint

Each unchecked item is Not run or unqualified. Record results in a pull request description or issue comment. Keep Fabric and Paper separate.

macOS Fabric and macOS Paper

  • Rerun the MCP lifecycle and the Checkbox click and keyboard-clear cases through the real descriptor on both renderers at current main (Fix macOS physical-input postconditions and add an advisory physical CI lane #4500 fixed the driver defects; no MCP rerun exists)
  • F6 trust paths with Accessibility/PostEvent granted and stable signing: v3 manifest plus private-credential handoff, channel-child helper re-verification, live authenticated bridge on a head containing Tighten Storybook manifest provenance and credential isolation #4490 (the Tighten Storybook manifest provenance and credential isolation #4490 macOS smokes failed on Accessibility apiDisabled, zero tests executed)
  • Real native failed-cleanup claim retention, startup/shutdown faults, and revocation, dispose-during-open, failed delete, ambiguous create, same-port rediscovery (probes so far used SDK in-memory injection)
  • Supervisor, Metro, channel and helper survivors; supervisor crash with descendants; interrupted native publication (via desktop-test/application-ownership, Add neutral macOS application ownership with exact workload identity #4492)
  • Unknown-effect story quarantine and trusted recovery; post-dispatch mutation cancellation
  • Correlated readiness/render faults; lost-context fencing and authenticated recovery; registered secondary windows
  • Anonymous/foreign HTTP/WS protected ingress; manifest lifetime
  • Launch-capable discovery and explicit legacy-lane separation; cross-service exact-app and input-mutex exclusion
  • Hosted physical input beyond the advisory Fabric lane (full lanes keep the physicalClick mask); Paper hosted physical lane; Paper current-head physical smoke after a locked console blocked it
  • Idle-channel lifetime (Fabric not remeasured; Paper one 22 s interval) and a reliability window
  • Durable TCC continuity (grant/revoke/regrant/restart; owned by Infrastructure: Complete Desktop Driver production release qualification #4345 for policy)
  • Strict-clear contracts with stable signing at current main
  • Measurements: Paper MCP click and cancellation cost; Paper Menu observations hit the 100-node cap (100 of 103 emitted), so no complete-tree sample exists

Windows Fabric

Win32 Paper

MCP

  • Independent qualification of supported clients' image, resource and cancellation behavior (SDK stdio qualification is not universal client qualification)

Untriaged observed failures

The owner may split these into sub-issues of #4435 later.

Dependencies

Acceptance

Validation

  • Use the supported workflows (yarn storybook test, yarn storybook driver --agent, desktop-test serve --agent) and the helper contracts documented in each package. Report each check as passed, failed, skipped, not run, or unsupported.
  • Update the affected topic section and its status-overview line in the owning references/current-status.md.
  • Code changes made to fix failures follow the package validation and changeset rules, ending with yarn clean-lage-cache then yarn lage buildci.

Evidence

  • Per-run evidence is recorded in the pull request description or an issue comment; each package's references/current-status.md keeps the latest result per endpoint with a link.
  • Retired plan: driver-next.md at 0569e1b86, sections 7 and 11.

Activity

  1. JasonVMo commented on Nov 16, 2026

    @JasonVMo
    ContributorAuthor

    Updated the issue body. The status block now lists the latest result per endpoint with PR links (#4469, #4493, #4494, #4498, #4500) instead of the 2026-11-09 ledger snapshot. The Windows 203/203 and Win32 177/177 smokes are attributed to #4469. Per-endpoint checklists now hold the remaining gaps, including the macOS and Windows/Win32 residuals from #4445, #4446, #4447 and #4448, which are now closed. An "Untriaged observed failures" list was added. Acceptance and Validation now say per-run evidence lives in PR descriptions or issue comments, and the status docs keep only the latest result per endpoint with a link. #4441 stays open.

  2. JasonVMo commented on Nov 19, 2026

    @JasonVMo
    ContributorAuthor

    Desktop preview follow-up from #4515

    Full Win32 Storybook service-graph crash recovery is deferred and remains open here. At ce084180a, the focused Win32 physical smoke, neutral fixture recovery (earlier 929b0281b), and protected graceful Win32 teardown passed. For the mixed graph, a protected Storybook run exited cleanly and the exact supervisor/channel exit was verified. An isolated copy of its real journal was then replayed: recovery refused before making any change. This verifies the existing fence, not successful native crash recovery. No live workload was fault-injected or manually reclaimed.

    Follow-up: provide a supported isolated workload claim/store and record exact ownership and exit evidence for the separately hosted channel, retained app, and descriptors before reconciling them. Qualify takeover and teardown on the real endpoint while keeping unknown, live, and changed records fenced. Desktop Test implementation follow-ups remain in #4518; the native gate stays on this issue.

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