dcc-cualisted

# DCC-CUA — Project UI Control Router Use this Skill as the canonical route whenever the user explicitly names `dcc-cua`, `DCC CUA`, `our dcc-cua`, or `我们的 dcc-cua`. ## Non-substitution contract An explicit DCC-CUA request is a hard routing boundary, regardless of whether the target is Maya, Chrome, a browser, or another desktop application. - Use the project-owned `dcc-cua` runtime and DCC-MCP `ui-control` surface. - Never load or call generic Codex/OpenAI Computer Use, the `computer-use` Skill, `@oai/sky`, or Browser/Chrome automation plugins for that request. - Never treat a DCC-CUA runtime, binding, readiness, or permission failure as permission to change providers. - Repair the project route when safely possible. Otherwise report the exact blocker and stop. - Use a generic provider only after the user explicitly retracts the DCC-CUA requirement or explicitly requests that provider by name. This boundary is provider selection, not an authorization bypass. DCC-CUA task grants, target binding, interruption, and confirmation policy still apply. ## Route attestation Before the first application observation or input, report all four fields: ```text provider=dcc-cua runtime=<version> pid=<exact-pid> hwnd=<exact-native-hwnd> ``` Do not perform the operation if the provider is different or the target is not exactly bound. ## Runtime preflight Use the official component contract; do not download an arbitrary executable: ```bash dcc-mcp-cli components status dcc