Make your reading page from a deck.

Help me create my reading page from a deck 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/deck-to-reading-page 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: - The source deck and approved speaker notes or transcript you may use. - The intended reader's question and the decision or next action. - Original chart data, labels and definitions where available. - Disclosure restrictions, source references and any commentary that must stay private. Creation task: Adapt my authorized source deck and approved speaker notes into a standalone static HTML reading page for [audience and question]. Reconstruct the argument rather than embed slide screenshots. Preserve evidence, data definitions, caveats and source references. Distinguish slide content from supplied explanatory notes; flag missing context instead of inventing it. Use readable narrative headings and explain visuals in text. Do not infer exact chart values, fabricate transitions as facts or include private presenter reminders. Ask only for missing essentials using existing authorized context. Use my saved artifact style if available. No scripts, forms, slide-conversion fidelity or animation promises. Show me the source-to-section mapping and draft. 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: - Can someone who missed the talk understand the argument and next step? - Are the page's claims supported by the slides or approved notes? - Are chart values, definitions and spoken caveats preserved accurately? - Have private notes and unsupported contextual additions been excluded? 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.