chore(inbox): file processed archangel handoff to outbox

1 files changed, 11 insertions, 0 deletions

diff --git a/assets/outbox/2026-06-09-1222-from-archangel-guard-against-live-mesa-hyprland.org b/assets/outbox/2026-06-09-1222-from-archangel-guard-against-live-mesa-hyprland.org
new file mode 100644
index 0000000..01da475
--- /dev/null
+++ b/assets/outbox/2026-06-09-1222-from-archangel-guard-against-live-mesa-hyprland.org
@@ -0,0 +1,11 @@
+#+TITLE: Guard against live mesa/hyprland updates (filed from archang
+#+SOURCE: from archangel
+#+DATE: 2026-06-09 12:22:04 -0500
+
+Guard against live mesa/hyprland updates (filed from archangel — this is archsetup's domain, not the minimal-base installer).
+
+ratio's Hyprland compositor SIGABRT-crashed Sunday 2026-06-07 13:15, taking its Wayland clients (awww-daemon, insync, emacs) down with it. Root cause from the coredump: /usr/bin/Hyprland and libgallium-26.0.6 both showed "(deleted)" — a pacman -Syu replaced mesa (26.0.6 -> 26.1.2) and hyprland on disk WHILE the session was live. The next GPU-lib call hit a swapped-out library and aborted. No hardware fault (no panic/MCE/thermal/GPU-reset in the logs).
+
+Ask: consider shipping an update wrapper or a documented practice — when a pending -Syu set includes mesa/hyprland/wayland runtime libs, advise running it from a TTY (or after logging out of Hyprland) rather than live. This is the likely trigger behind ratio's high lifetime unsafe-shutdown ratio (57/53 vs 76/72 power cycles): a frozen/crashed compositor leads to a hard reset.
+
+Originally surfaced in the 2026-06-08 ratio health-check handoff to archangel; relocated here because hyprland/mesa are installed and managed by archsetup, not by the archangel ISO.