Make your travel briefing.

Help me create my travel briefing as a static HTML page, using relevant authorized context already in this conversation. Example (illustrative structure): https://shareartifacts.dev/guides/travel-briefing#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: - Current booking confirmations, with reservation codes, payment details, and personal identifiers removed before creating a broadly shared draft. - Official transport and venue information you have checked, including the date of verification and relevant local time zone. - The group’s agreed priorities, accessibility needs, and pace preferences, sharing personal requirements only with permission. - Proposed activities and fallback options clearly marked as unbooked, with outstanding checks and decisions listed separately. Creation task: Create a practical travel briefing as static HTML from the booking details, official source information, and preferences I supply. Organize it by local date. Separate confirmed arrangements, tentative ideas, planning estimates, and outstanding checks. Include locations, clearly labeled local times when known, transfer assumptions, and fallback options without implying availability. Do not invent reservations, opening hours, prices, travel durations, restrictions, or official advice. Link only to supplied sources and show when changeable details were checked. Remove reservation codes, payment details, identity documents, and unnecessary personal information. Apply my saved artifact style if available and make it easy to read on a phone. No scripts or forms. Return a draft for verification; do not publish or change access until I approve. 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: - Is every booking distinguished from an idea, estimate, or item that still needs verification? - Have dates, local times, addresses, and changeable details been checked with official providers? - Are booking codes, identity and payment data, and sensitive personal details excluded? - Can travelers access essential confirmations separately, and is the page’s sharing audience appropriate? 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.