Obsidian Incident Runbook Overview Systematic procedures for diagnosing and resolving Obsidian failures: plugin crashes, vault corruption, sync conflicts, performance degradation, and broken CSS/themes. Each section is a self-contained runbook -- jump to the relevant one. Prerequisites - Access to the affected Obsidian vault directory - Developer Console access (Ctrl+Shift+I / Cmd+Option+I) - Terminal access for filesystem operations - Backup awareness (know where your backups are before making changes) Instructions Step 1: Quick Triage Determine the category before diving in: | Symptom | Cat…