Make your release notes.

Help me create my release notes 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/release-notes 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 exact release version, date, and verified included changes—not every merged ticket. - Confirmed rollout scope, supported environments, and any staged or preview availability. - Approved compatibility and migration instructions, including known limitations. - Audience-safe evidence, support links, and any action readers must take. Creation task: Using only authorized release notes, verified shipped scope, and approved instructions, draft release notes for [version] and [audience]. Ask for missing version, date, rollout scope, compatibility details, and required actions. Separate shipped changes from merged or planned work. Lead with reader impact and required action, then improvements and known limitations. Preserve exact field names and affected environments. Do not invent fixes, performance gains, migration commands, deadlines, automatic upgrades, or compatibility guarantees. Leave missing availability explicitly unconfirmed. Link only to supplied audience-safe documentation; exclude private issue notes. Create static HTML with no scripts, forms, or live-data claims. Apply my saved artifact style if available. Return a draft and verification questions. Do not publish or change access without separate explicit approval; publishing these notes must not trigger a release or deployment. 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 availability claim match the released version and rollout scope? - Can an affected reader find the required action before the feature list? - Are technical names, compatibility conditions, and known limitations exact? - Are planned work and missing instructions kept out of confirmed release claims? - Are linked sources safe for this audience? 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.