jared e4048f5480 docs: log Chrome SIGBUS incident from Btrfs csum corruption ... Chrome crashed repeatedly with SIGBUS on launch. Root cause was a corrupt data block in ~/.config/google-chrome/Profile 2/Favicons on a single-copy Btrfs volume (csum failures correlated to the second with each crash). A scrub found two further uncorrectable blocks (a Chrome cache file and a gdm help file); both fixed. SSD SMART is clean and the corruption is static across scrubs, pointing at a past RAM/bus event rather than a failing drive. Adds docs/incidents.md (dated incident log) and a CLAUDE.md pointer. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-06-24 13:49:13 -04:00
..
hyprland	docs(wm): Phase 4 progress, Hyprland config reference, and keybindings	2026-05-07 09:43:43 -04:00
keyboard	docs(keyboard): add Keychron K15 Pro keymap documentation	2026-05-07 09:43:46 -04:00
superpowers	feat(backup-monitor): fix MailPace body field and add explicit headers	2026-05-07 13:45:28 -04:00
window-manager	docs(wm): Phase 4 progress, Hyprland config reference, and keybindings	2026-05-07 09:43:43 -04:00
incidents.md	docs: log Chrome SIGBUS incident from Btrfs csum corruption	2026-06-24 13:49:13 -04:00
synology.md	fix(backup): correct Synology SFTP path and remove pre-flight check	2026-06-05 11:47:03 -04:00
vps-inventory.md	docs: record DigitalOcean VPS deletion in vps-inventory	2026-06-24 11:48:25 -04:00