Make your customer FAQ guide.

Help me create my customer FAQ guide 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-faq-guide 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: - Recurring customer questions with identifying information removed. - Approved policies, their effective dates, scope, exceptions and owners. - The existing help route and audience-safe links customers can actually open. - Questions without an approved answer, plus the person responsible for resolving them. Creation task: Create a customer FAQ as static HTML using my authorized customer questions and approved policies. Organize by customer situation. Give each question a direct answer, relevant conditions, and an approved next step. Preserve policy dates, exceptions, and scope. Do not invent entitlements, guarantees, prices, support response times, or missing policies. Ask only for missing essentials and flag conflicting or absent answers. Use existing authorized context and my saved artifact style if available. Include only audience-safe source links; no personal ticket details. No scripts, forms, live answers, or ticket submission. Show me the draft and unresolved policy questions. 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 every answer match a current approved policy and its exceptions? - Can a customer find answers using their own situation rather than internal terminology? - Are unanswered questions resolved or accurately routed without invented promises? - Do help links work for the intended audience, with private ticket data 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.