Make your sales pipeline review.

Help me create my sales pipeline review as a static HTML page, using relevant authorized context already in this conversation. Example (complete fictional sample): https://shareartifacts.dev/examples/sales-pipeline-review 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: - Dated opportunity exports with stable IDs, amount currency, stage, forecast category, and expected close date. - The comparison snapshot and exact reporting-period filters, with the stage and forecast definitions used. - Authorized evidence for movement, next steps, and known blockers—not private speculation about buyers. - Confirmed owners, agreed actions, and disclosure limits for customer and commercial information. Creation task: Create a sales pipeline review from only the authorized dated CRM snapshots, definitions, and deal notes I provide. Ask for missing period filters, currency, stage definitions, comparison snapshot, owners, and next-step evidence. Reconcile period movement without treating moved-out deals as lost. Separate opportunity value, forecast categories, closed-won status, and recognized revenue. Do not invent probabilities, weighted forecasts, buyer commitments, reasons for movement, or dates. Distinguish seller-proposed next steps from buyer-confirmed ones. Keep sensitive customer details and private speculation out of the shared draft. Create static HTML with no scripts, forms, live CRM claims, or writeback. Use my saved artifact style if available. Show the draft and figures to verify. Do not publish or change access without separate explicit approval. Do not change opportunities, assignments, or forecast records. 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: - Are period filters, currencies, and comparison snapshots consistent? - Does movement reconcile without counting moved-out deals as lost or double-counting won value? - Are pipeline, forecasts, bookings, and revenue clearly distinguished? - Are next actions and buyer commitments supported rather than inferred? - Are commercial details appropriate for the approved 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.