Infrastructure: Add scoped runner grants and drain-confirmed desktop controller handoff
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 25/100
- issue の種類
- 機能追加
- 明瞭さ
- 明確に書かれている
- 活発さ
- 活発
- 技術スタック
- node.js, react-native, typescript
- 領域
- devtools, mobile-dev, testing-qa
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
説明
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).
- 主要言語
- TypeScript
- スター
- 1.4k
- フォーク
- 179
- 平均マージ
- 1日 8時間
- マージ済み PR(30日)
- 60
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
microsoft/fluentui-react-native のほかの issue
-
MenuList: FocusZone not wired for react-native-windows ('windows'), so menu items are Tab-only (no arrow-key roving focus)対応中かも @UditDewan が 24 日前に担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
microsoft/fluentui-react-native#4174 ·
メンテナーはふだん 1 日以内に返信
-
Platform: MacOS Platform: Win32 Platform: Windows Status: Blocked
難易度 5/5 1週間以上 初心者へのやさしさ 12/100
microsoft/fluentui-react-native#4451 ·
メンテナーはふだん 1 日以内に返信
-
Status: Blocked
難易度 5/5 1週間以上 初心者へのやさしさ 24/100
microsoft/fluentui-react-native#4450 ·
メンテナーはふだん 1 日以内に返信
-
Status: Blocked
難易度 5/5 1週間以上 初心者へのやさしさ 25/100
microsoft/fluentui-react-native#4449 ·
メンテナーはふだん 1 日以内に返信
-
Platform: Win32 Platform: Windows Status: Blocked
難易度 5/5 1週間以上 初心者へのやさしさ 30/100
microsoft/fluentui-react-native#4447 ·
メンテナーはふだん 1 日以内に返信
microsoft/fluentui-react-native の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 74/100
langchain-ai/langchainjs#12157 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 86/100
activescott/home-infra-k8s-flux#511 ·
メンテナーはふだん 1 日以内に返信
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
難易度 1/5 1時間未満 初心者へのやさしさ 72/100
lingdojo/kana-dojo#33753 · コメント 1 件 · リアクション 5 件 ·
メンテナーはふだん 1 日以内に返信
-
android:player
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
メンテナーはふだん 1 日以内に返信
-
follow-up needs-triage S3: minor
難易度 1/5 1〜3時間 初心者へのやさしさ 85/100
manaflow-ai/cmux#38032 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信