Post-1.0. Not for the 1.0 launch. From the WWDC 2026 review — see docs/wwdc-2026-macos-27-opportunities.md (PR #911), opportunity #3.
Why
Intent QA currently leans on Computer Use UI automation, which is slow and flaky by nature. The new App Intents Testing Framework (macOS 27 SDK) validates intents through real system pathways with no UI automation — cheap, deterministic coverage for GetCurrentLayerIntent, ServiceControlIntent, SendActionIntent, and any new schema-backed entities (see the Entity Schemas issue).
Plan
- Add an intent test target once CI runs on the macOS 27 SDK / Xcode 27.
- Cover the three existing intents plus the
keypath:// action URI dispatch path.
- Respect existing test-safety rules (no real
pgrep; keep suite fast per CLAUDE.md).
https://claude.ai/code/session_01Nsiqm39oCwHkbrHytefnGM
Post-1.0. Not for the 1.0 launch. From the WWDC 2026 review — see
docs/wwdc-2026-macos-27-opportunities.md(PR #911), opportunity #3.Why
Intent QA currently leans on Computer Use UI automation, which is slow and flaky by nature. The new App Intents Testing Framework (macOS 27 SDK) validates intents through real system pathways with no UI automation — cheap, deterministic coverage for
GetCurrentLayerIntent,ServiceControlIntent,SendActionIntent, and any new schema-backed entities (see the Entity Schemas issue).Plan
keypath://action URI dispatch path.pgrep; keep suite fast per CLAUDE.md).https://claude.ai/code/session_01Nsiqm39oCwHkbrHytefnGM