update-taptap-mcplisted

# TapTap Maker MCP Upgrade Workflow Use the CLI upgrade entry instead of hand-writing npm cache or client-config scripts. Maker local development is published by `@taptap/maker`; do not update the legacy main Open API package for Maker workflows. ## Scope This workflow upgrades only the current machine and the current Maker project directory. - Do not scan unrelated Maker projects. - Do not batch-upgrade multiple projects. - Do not delete old config backup files. Historical `.bak.*` files have no reliable ownership marker and must be left untouched. - The MCP status surface only checks the package policy and reports `required_upgrade`, `update_available`, `current`, `unavailable`, or `skipped`. It never runs `taptap-maker upgrade` by itself. ## Required Steps 1. Read `maker://status`; if resources are unavailable, fall back to `maker_status_lite`. If the `Maker MCP package update` section reports `required_upgrade`, explain the version reason to the user first. Do not run any upgrade command before that explanation and approval step. 2. Identify the current Maker project directory. Use `--target-dir` only when the directory is confirmed to be a Maker project, which means it or one of its parents contains `.maker-mcp/config.json`. 3. If the AI client has exactly one attached workspace and that workspace is the Maker project, use that workspace as `<PROJECT_DIR>`. If there are multiple workspaces, or the current directory is not clearly a Maker