Make your survey findings report.

Help me create my survey findings report 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/survey-findings 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: - Exact question wording, answer options, and whether multiple selections were allowed. - De-identified responses or approved aggregate counts, including exclusions and missing answers. - Recruitment method, field dates, invited population when known, and any reviewed weighting method. - A documented coding method for open text, approved illustrative excerpts, and the audience's decision. Creation task: Create a survey findings page using only authorized de-identified responses, exact questions, sampling details, and reviewed counts. Ask for missing essentials: recruitment, field dates, question wording, denominators, missing answers, exclusions, and coding method. Show counts beside percentages and preserve question-specific denominators. Keep respondent findings distinct from population claims. Do not invent representativeness, weighting, margin of error, causal conclusions, quotations, or missing counts. Explain overlapping themes and keep observed findings separate from proposed actions. Exclude identifiers and sensitive free text; use only explicitly approved excerpts. Create static HTML with no scripts, forms, survey collection, or live-data claims. Use my saved artifact style if available. Show the draft, calculations, and uncertain claims 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: - Does each result identify who answered that question and how many skipped it? - Are recruitment limits and any weighting accurately described? - Are themes, frequencies, and quotations traceable to the supplied method and evidence? - Are generalizations and proposed actions distinct from observed responses? - Could free text or small-group details identify a respondent? 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.