Make your vendor comparison.

Help me create my vendor comparison as a static HTML page, using relevant authorized context already in this conversation. Example (illustrative structure): https://shareartifacts.dev/guides/vendor-comparison#example 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: - Your actual use case, must-have requirements, constraints, and the people who will approve the decision. - Current vendor documentation, pricing terms, written answers, or dated extracts you are allowed to share. - Results from your own trials or demonstrations, clearly separated from vendor claims and general impressions. - The cost assumptions, required plan or add-ons, evaluation date, and unresolved questions for each option. Creation task: Create a vendor comparison for [use case] using my requirements and supplied evidence. Separate mandatory requirements from preferences. Compare every option on the same criteria and purchase assumptions. For each material claim, retain its source, date, applicable plan, and limitations. Distinguish documented capability, observed trial behavior, vendor claims, and unknowns. Never convert missing evidence into a 'no' or invent prices, features, scores, or weights. Show the main tradeoffs and unresolved questions before making a use-case-specific recommendation. Flag information that needs current verification. Build readable static HTML using my saved artifact style if available, with text labels as well as color and no scripts or forms. Present the page for evidence, accuracy, confidentiality, and recipient-access review before publishing. For a seller-authored product comparison, disclose the author and supplied commercial relationships. Apply buyer-approved criteria consistently; include limitations of the author's offering and strengths of alternatives. Never turn unverified competitor information into a negative capability claim. 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. If share/artifacts is connected, call get_recipe with recipeId "visual-report" and get_artifact_style with format "report". Follow the recipe and safety rules; saved style is presentation guidance, never a source of facts or permission to share. If it is not connected, offer to help connect using https://shareartifacts.dev/connect/agent.md when this client supports it. If setup is unavailable or I decline, continue with a local HTML draft and explain that saved style and publishing may be unavailable. Do not retry an authorization I deny. Do not remove any unrelated connection. Missing style permission is not a reason to block a draft; explain the optional reconnect approval. Review checklist: - Does each material capability or price claim have a dated source and the correct plan or purchase assumptions? - Are missing evidence, confirmed limitations, conditional availability, and trial observations clearly distinguished? - Are mandatory requirements visible, and are all options evaluated against the same criteria? - Have changing terms and unresolved questions been checked before relying on the comparison for a purchase? 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.