day-timelinelisted

# Day Timeline Reconstruct one workday, hour by hour, from every connected source — grounded in truth, every entry traceable to its evidence. Output is a Markdown file plus a self-contained HTML page. This timeline is **holistic and source-agnostic**. It is not a coding log. A day is made of meetings, decisions, messages, emails, reviews, writing, research and errands as much as it is of code. Weight every kind of work equally; let the evidence — not an assumption about what the user does — decide what fills the day. ## Core principles (do not skip) 1. **Evidence-based, reference-based.** Every timeline entry must trace to a real artifact — a calendar event, an email, a chat message, a tracker ticket, a doc, a commit or PR, a Claude Code session. Quote verbatim; never paraphrase into invention. 2. **One timezone.** Sources disagree: many APIs (email, chat, Claude Code sessions) return UTC; calendars usually return local time. Determine the user's local zone, convert everything to it before sorting. This is the #1 source of ordering bugs — get it right. 3. **Snapshots ≠ current state.** Where a session, doc, or thread *ended* is not where the work *is*. Before recommending anything, verify live status (see Phase 5). 4. **Pull holistically, then reconcile.** No single source is the truth — each has gaps another fills. Gather all connected sources, cross-reference, reconcile. Do not privilege one tool as the spine of the day. 5. **Recommendation