Make your project handoff.

Help me create my project handoff as a static HTML page, using relevant authorized context already in this conversation. Example (complete fictional sample): https://shareartifacts.dev/examples/project-handoff 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 deliverables and their current versions, with the supplied review criteria and acceptance evidence. - Open issues and dependencies, their consequences, confirmed owners, and any agreed target dates. - The outgoing and receiving owners, the conditions for transfer, and the authoritative acceptance record if one exists. - Approved operating instructions, audience-safe reference links, and the receiving team's known access limitations. Never include credentials. - The next review request, confirmed support arrangements, and what remains outside the delivered scope. Creation task: Using only materials I provide or have authorized you to access, create a project handoff for [receiving owner] covering [delivered work]. Ask only for missing essentials: deliverables and versions, acceptance evidence, open issues, current owners, transfer conditions, required access, and the next review request. Lead with what is ready to take over and what still needs confirmation. Separate received, reviewed, and accepted work. For each open issue preserve its consequence, current owner, next action, and supplied target date; keep missing information unresolved. Distinguish a target from a commitment. Do not infer acceptance from receipt or silence, invent owners or dates, close issues, grant access, or transfer responsibility. Keep known restrictions beside affected deliverables, and preserve scope exclusions. Include only audience-safe references, not credentials or private source notes. Explain how to record acceptance in our existing project workflow; this page must not collect it. Create readable static HTML with no scripts, forms, signature fields, or live-data claims. Use my saved artifact style if available. Show me the draft and unresolved 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. 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: - Can the receiving owner see what is ready and what they must confirm without reading the full history? - Are receipt, acceptance, permission, and ownership transfer distinct and supported by the sources? - Does each open issue retain its current owner, consequence, and honest target status? - Are the operating references useful to the recipient at their actual access level, with no credentials exposed? - Are scope exclusions and conditions for transfer still visible? - Does the page point to the authoritative acceptance process rather than pretending to complete it? 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.