Make your event attendee guide.

Help me create my event attendee guide 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/event-attendee-guide 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: - Confirmed event date, time zone, session times, rooms and breaks. - Organizer-approved arrival instructions and venue accessibility information. - Verified attendee help contacts, registration instructions and material links. - Unresolved arrangements, change-notification plan and intended sharing audience. Creation task: Create an event attendee guide as static HTML from my authorized organizer materials. Lead with arrival date, clearly labeled local times, entrance and first destination. Organize sessions and breaks in order with known locations. Preserve exact verified accessibility arrangements and flag unknown routes or rooms without inventing assurances. Use approved help and registration links only; no private attendee details. Ask only for missing essentials using existing authorized context. Apply my saved artifact style if available and make the page easy to read on a phone. No scripts, forms, ticketing, live schedule or automatic notifications. Show me the draft and unresolved logistics. 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. 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: - Are date, time zone, arrival route, session times and locations confirmed? - Are accessibility details specific, verified and free of unsupported blanket claims? - Are unknown rooms and the organizer's follow-up responsibility visible? - Can attendees obtain essential instructions and meaningful changes without assuming live refresh? 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.