Make your customer case study.

Help me create my customer case study as a static HTML page, using relevant authorized context already in this conversation. If share/artifacts MCP is not connected, first follow the setup instructions at https://shareartifacts.dev/connect/agent.md. Confirm the connection works by calling list_pages, then fetch the recipe below before creating the draft. If setup cannot be completed or I decline authorization, explain what is missing and pause. Do not retry an authorization I deny. Do not remove any unrelated connection. Example (complete fictional sample): https://shareartifacts.dev/examples/customer-case-study Use the example for structure, not as facts about my work. Only use fictional sample data if I explicitly choose a sample. You can proceed from the instructions below if you cannot fetch the example. Ask conversationally for only the missing essentials. Do not invent facts, commitments, or sources. Do not request secrets. Ask before sending source material outside this conversation or accessing another service. Useful inputs: - Customer-approved background and the scope permitted for external sharing. - The actual work performed and its dates, including other changes that may affect results. - Measured before/after values with definitions, time periods, sample sizes and limitations. - Exact approved quotations and attribution permissions, or an explicit decision to use no testimonial. Creation task: Using only authorized materials, draft a customer case study with the approved customer context, problem, work performed, checked results and measurement limitations. Ask for missing permissions, dates, units and evidence. Preserve concurrent changes and distinguish observed results from causal claims or guaranteed outcomes. Use only exact approved quotations with approved attribution; do not invent endorsements, customer identities, metrics or approval. If no quote is supplied, omit the testimonial. Use readable static HTML with no scripts or forms and my saved style if available. Show the draft and permission gaps for review. Do not publish or change access without separate explicit approval. Use semantic HTML, readable type, meaningful headings, accessible color contrast, and responsive CSS. No JavaScript, forms, embeds, redirects, or live API calls. Verify calculations outside the page. Only include information the intended reader should see. Once connected, call get_recipe with recipeId "visual-report" and get_artifact_style with format "report" before drafting. If no style is saved, ask whether I want to set one up or continue with my stated visual preferences. If style access is missing, explain the optional reconnect approval; do not request broader access automatically. Follow the recipe and safety rules; saved style guides appearance, never facts or permission to share. Review checklist: - Are customer name, scope and quotes approved for this audience? - Are periods, samples, units and calculations comparable? - Are concurrent changes and attribution limits visible? - Does the page avoid fabricated testimonials or guaranteed outcomes? Show me the draft in your available preview or file tools. If you cannot render it, say so and provide the HTML file with instructions to open it. Ask for corrections. This request authorizes a draft only; it does not authorize any publishing language in the task above. Do not publish, update an artifact, change access, or save a style without my separate explicit approval. Connection approval is not publication approval. Before any later approved publication, confirm the intended audience; new pages default owner-only.