dcc-mcplisted

<!-- BEGIN GENERATED PRODUCT DISCOVERY ROUTING --> ## Released Product and Application UI Routing Load `references/PRODUCTS.json` only when released-product support, aliases, or routing are ambiguous; do not load every product record for unrelated tasks. Use typed DCC-MCP tools first. `DCC-CUA` and `ui-control` name one project-owned `dcc-cua` route for DCC application UI, browser UI, non-DCC application UI; they are not competing automation systems. An explicit DCC-CUA request is a hard provider boundary. Do not recommend or silently fall back to `Codex/OpenAI Computer Use`, `computer-use Skill`, `@oai/sky`, `Browser plugin`, `Chrome plugin`. If the project route is unavailable, repair it or report the blocker. Before the first UI observation or input, visibly attest `provider=dcc-cua runtime=<version> pid=<exact-pid> hwnd=<exact-native-hwnd>`. Missing or stale binding data stops the action. For every state-dependent UI action, require fresh observation before every state-dependent action; latest snapshot or semantic reference only; post-action state readback; stop on interruption or permission failure. Stop fail-closed on interruption or permission failure, and hand CAPTCHA, authentication challenge, security challenge to a human instead of bypassing it. Local application path cache: when the user gives an absolute local software path, record it with `python scripts/app_path_cache.py set --product <id> --path "<path>"` and retain only the normalized path and verificatio