Update to Recomaze

{
  "description": "Use right after a Recomaze write, save, publish or job (a product written to the store, an article or post saved, a lead or step saved, the AI chatbot changed, a scan started) and when the merchant asks \"did it save?\", \"is it ready?\" or \"what happened?\". Reads the result back and answers in one or two sentences, with the blocker when there is one.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 331
    }
  ],
  "name": "completion-report",
  "skill_md_contents": "---\nname: completion-report\ndescription: Use right after a Recomaze write, save, publish or job (a product written to the store, an article or post saved, a lead or step saved, the AI chatbot changed, a scan started) and when the merchant asks \"did it save?\", \"is it ready?\" or \"what happened?\". Reads the result back and answers in one or two sentences, with the blocker when there is one.\n---\n\n# What happened, in one line\n\nA write is reported only after it is read back. The tool's answer is the claim; the read is the proof.\n\n## After a write\n\n1. The call that did it answered `needs_confirmation` first and ran with `confirmed: true` on the merchant's yes; `apply_product_content` runs on its `change_id`, `set_chatbot_voice` on its `change_id` alone, without the voice fields sent again.\n2. Read the thing back with its own read of the very fields that changed: the product (`get_product`), the article or a saved post (`get_article`, by the article id the save answered), the lead (`get_lead_detail`), the chatbot's voice, tone and rules (`get_chatbot_voice`), its look, words and visibility (`get_popup_settings`), the routine's weekly budget and the kinds that run on their own (`get_daily_routine` with `preview: true`, its credits section), lead capture (`get_setup_status`, `plugin_setup.lead_capture`), the job (`scan_run_status`). Another tool's read is no proof of the change.\n3. Answer in one sentence: what is saved, where it landed and, when there is one, the link. A second sentence only for a blocker or something the merchant must do. No list of ids, no restating of the approval, no cost unless it differs from the quote.\n\n## A job still running\n\nSay what runs and when to look again; do not poll it in a loop and do not start it a second time. A started job is not a finished one, and a saved draft is not a published one: say which it is.\n\n## A failure\n\nName what did not happen and why, in the merchant's words, and what would make it work. Never report a save that only happened in the chat.\n"
}