Always treat session observations as a persistent engineering log and reference prior build state as ground truth

Always treat session observations as a persistent engineering log and reference prior build state as ground truth. The user treats timestamped session observations (🔴/🟡 entries) as an authoritative engineering journal. They expect the assistant to recall and reason from prior session facts without re-investigation. When resuming work, the user references prior build artifacts, decisions, and failures as settled context. The assistant should treat 🔴 entries as hard directives and 🟡 entries as confirmed facts. Example identity facts confirmed across sessions: Burak Yigit Kaya works at Sentry, email ben@byk.im, reports to David Cramer. Match precision in synthesis — comprehensive recaps welcome when explicitly requested ('tell me everything you know about me').