## 1. Fix the date, time zone and calendar scope

Read the uploaded input only. Restate the target date, display time zone, four event ids and date fields. Separate timed and all-day events. Do not connect Calendar or create invitations. Save scope.md.

Expected: A dated event index.
Check: Use 2026-10-19; do not turn E04 into a midnight meeting.

## 2. Normalize status and time before finding overlaps

Convert start/end to Asia/Shanghai and retain originals. Mark cancelled events excluded and all-day items separate. Calculate active interval intersections with start, end and minutes. Save normalized.csv.

Expected: A 30-minute E01/E02 overlap.
Check: E01 is 10:00–11:00; E02 is 10:30–11:30; E03 is excluded.

## 3. Use only background you actually received

For E01–E04 and B01, list known topics, supporting ids, missing material and three preparation questions. Mark unavailable participants/news as not obtained. Do not infer a price, date or client position.

Expected: Preparation notes with source ids.
Check: E01 has no agenda; E02 price and delivery date remain open.

## 4. Write a brief that separates decisions from reminders

Write brief.md with the timetable, conflict, missing agendas, unanswered invitations, all-day items and unchecked sources. Retain event/background ids. Generate text only; do not accept, decline, reschedule or notify anyone.

Expected: A complete one-page meeting brief.
Check: All four inputs have an outcome; cancelled events do not inflate active counts.

## 5. Try one read-only day in your calendar

Verify <account/calendar>. Read only <specific date/time zone>, at most 10 events. Report tools, pagination, event ids and updates. Handle cancellations, all-day events and recurring instances separately. List missing context without modifying Calendar or scanning the inbox.

Expected: A traceable read-only day, or a clear blocker.
Check: Account, date and coverage are explicit; incomplete reads are not called complete.

## 6. Check reruns and date rollover before scheduling

Draft a meeting-brief Skill with explicit date, Asia/Shanghai, scope, pagination, event id/update time, overlap rules and missing sources. Propose a weekday 21:00 Routine but do not create it. Refresh changed events; report connection failures separately.

Expected: A reusable method and schedule proposal.
Check: Reruns create no invitations; an empty calendar and a failed read have different statuses.