Infrastructure: Add scoped runner grants and drain-confirmed desktop controller handoff
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
- 25/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- node.js, react-native, typescript
- Ambito
- devtools, mobile-dev, testing-qa
Direzione di ricerca
Start with the cited "MCP/WDIO handoff" and "Standalone WDIO/Jasmine execution" sections in packages/agentic/desktop-test/references/current-status.md, then inspect the listed WDIO paths and storybook-desktop/src/testing/{runWdioTests,worker}.ts. The generic handoff is blocked by #4436 and #4442; Storybook work also depends on #4449. Done means implementing the scoped grant and drain flow, adding required status and guidance updates and changesets, and completing the package and native consumer validation described in the issue.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Current status - 2026-11-07
Blocked for generic handoff by F2 #4442 (in #4463); F1 is already merged. New input-lane selection in #4464 does not provide controller ownership transfer.
Remaining behavior: agent-served mode and ordinary WDIO still exclude each other; implement bounded busy/relinquish/operator-authorized preemption, stop new work, await cancellation/settlement and session DELETE, invalidate old references/cursors/proofs/artifact links, and only then grant the runner a session. Worker-crash drain and credential confinement remain acceptance requirements.
F9 #4449 gates only the Storybook phase. F10-M #4446 / F10-W #4447 gate only opt-in retained supervisor-owned applications; attach-only handoff does not need them. Cross-MCP-connection resume and automatic replay are not supported by this PR.
Goal
Agent-served mode (serve --agent) and WDIO runs currently exclude one another, so moving between MCP control and suite execution requires restarting services. Add scoped runner grants and a handoff that waits for the previous controller to drain before a runner opens its own session.
Part of #4435 (plan item F11).
Scope
- Owner: WDIO and CSF runner integration.
- Paths (under
packages/agentic/):desktop-test/src/wdio/*, the driver's grant transport and drain contracts, andstorybook-desktop/src/testing/{runWdioTests,worker}.ts. - Default to a bounded
busyresult. An explicit relinquish or operator-authorized preempt stops new work, cancels and awaits settlement, confirms session deletion, invalidates references, cursors, proofs, and artifact links, and only then authorizes a new runner session. Grant revocation callbacks are not a drain barrier. - Keep the documented CSF exception, where the runner owns the session and an isolated Node worker borrows it, unless it is deliberately migrated.
Dependencies
- Blocked by: F2 #4442 for the generic handoff; F1 #4436 is delivered by #4455.
- Phased prerequisites: Storybook integration requires F9 #4449. Retaining a supervisor-launched app across handoff requires F10-M #4446 or F10-W #4447 and an explicit ownership option. Attached-app handoff needs neither.
- Unblocks: F13 #4450.
- Parallel with: F3 #4444, F6 #4445, F10-M, and F10-W.
Acceptance
- MCP and WDIO cannot control the same reserved target concurrently.
- A worker crash drains its session.
- Stale references, cursors, and artifact links fail after handoff.
- Credentials never enter capabilities, generated config, logs, or model output.
Validation
- Iterate with focused
yarn test <name>in each changed package, then run itsyarn format,yarn lint,yarn build, andyarn test. Finish withyarn clean-lage-cachethenyarn lage buildci; runyarn lage test-links --verbose --groupedafter markdown changes. - Add a patch changeset for each changed published package. Update the owning
references/current-status.mdrows (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: "MCP/WDIO handoff" and "Standalone WDIO/Jasmine execution" in
packages/agentic/desktop-test/references/current-status.md. - Retired plan:
driver-next.mdat0569e1b86, sections 6 (cancellation, handoff, and recovery) and 8 (F11).
- Lingua principale
- TypeScript
- Stelle
- 1.4k
- Fork
- 179
- Merge medio
- 1g 8h
- PR unite (30g)
- 60
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di microsoft/fluentui-react-native
-
MenuList: FocusZone not wired for react-native-windows ('windows'), so menu items are Tab-only (no arrow-key roving focus)Forse già presa @UditDewan l’ha presa 24 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
microsoft/fluentui-react-native#4174 ·
I maintainer di solito rispondono entro 1 giorno
-
Platform: MacOS Platform: Win32 Platform: Windows Status: Blocked
Difficoltà 5/5 Più di una settimana Idoneità per principianti 12/100
microsoft/fluentui-react-native#4451 ·
I maintainer di solito rispondono entro 1 giorno
-
Status: Blocked
Difficoltà 5/5 Più di una settimana Idoneità per principianti 24/100
microsoft/fluentui-react-native#4450 ·
I maintainer di solito rispondono entro 1 giorno
-
Infrastructure: Convert Storybook lifecycle takeover into desktop-test resource contributionsApertaStatus: Blocked
Difficoltà 5/5 Più di una settimana Idoneità per principianti 25/100
microsoft/fluentui-react-native#4449 ·
I maintainer di solito rispondono entro 1 giorno
-
Platform: Win32 Platform: Windows Status: Blocked
Difficoltà 5/5 Più di una settimana Idoneità per principianti 30/100
microsoft/fluentui-react-native#4447 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di microsoft/fluentui-react-native
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
langchain-ai/langchainjs#12157 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 86/100
activescott/home-infra-k8s-flux#511 ·
I maintainer di solito rispondono entro 1 giorno
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 72/100
lingdojo/kana-dojo#33753 · 1 commento · 5 reazioni ·
I maintainer di solito rispondono entro 1 giorno
-
android:player
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
-
follow-up needs-triage S3: minor
Difficoltà 1/5 1-3 ore Idoneità per principianti 85/100
manaflow-ai/cmux#38032 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno