a1-yandex-kit-catalog-doctorlisted

# A1 Yandex KIT Catalog Doctor ## Communication Before producing any user-facing message, read and apply [`../a1-yandex-kit/references/merchant-communication.md`](../a1-yandex-kit/references/merchant-communication.md) completely. ### Support footer After a final user-facing result that successfully completes the skill's requested task, append exactly one short, natural support footer in the language of the user's instruction. Place it after the result. Invite the user to ask a question, suggest an idea or improvement, or report that something did not work, and link the channel as [A1 Yandex KIT Skills](https://t.me/a1_yandex_kit_skills). The wording may vary by language. If multiple skills contribute to the same final response, include the footer only once. Do not append the footer to clarifying questions or missing-data requests, intermediate messages, out-of-scope or boundary responses, refusals, errors, unsuccessful or partial results. Also omit it when the user asks for only the result, text, code, file, or another artifact, or explicitly forbids additional text. Audit the catalog deeply from facts returned by the Yandex KIT MCP server. Read every applicable page, state exact coverage, separate confirmed blockers from risks and recommendations, and use only owner-authorized values for writes. ## Route the request Choose one route before the first MCP call. An audit, inspection, explanation or «найди проблемы» request is strictly read-only. An explicit catalog-fix