Let somebody extend this without forking it, and say when things die

Two of Section F.

Hooks are the pressure valve. "Can Panama also do X when the theme
changes" is now a five-line file in ~/.config/panama/hooks rather than
a fork, a feature request, or a patch somebody rebases forever. Each
name takes a single file and a .d directory so several things can react
without fighting over one, and a broken hook is reported and stepped
over: somebody's script must never cost a theme change, an upgrade or a
login. Wired at theme-set, post-upgrade and post-migrate. This is the
thirty-line version of the plugin host the upstream ledger defers, and
it has no API to keep stable beyond "we will run your script and tell
you what happened".

Testing it caught a real bug the reading would not have: run_one
captured the script path but never shifted it off, so every hook got
its own filename as $1 and the real arguments arrived one place late. A
hook reading $1 as the colour scheme got a path.

The crash watcher notices when a program dumps core and says so. Under
GNOME, ABRT does this; here nothing did, and applications died silently,
which is most of how "Linux is flaky" gets earned.

Once per program per session is the entire design, not a nicety. This
machine's portal backend crashes between eleven and sixty times a day,
and a notification per crash would be one every few minutes for
something nobody can act on. The first is news; the fortieth is why
people turn notifications off. The health page keeps the running count.

It waits for the notification server before reporting, because the
crash most worth hearing about is the one that took the shell with it,
and it names the executable rather than the kernel's comm field, which
truncates at fifteen characters. Verified against real segfaults.

setup/scripts/link-dotfiles

@@ -438,6 +438,26 @@ fi
 # than by symlinking the directory itself, the same way the quadlets and
 # desktop entries are: Nautilus writes nothing here today, but a directory
 # symlink into the repository is how machine state ends up in a tracked path.
+# Hook samples. Copied rather than symlinked, and only when absent: hooks are
+# the user's own scripts, and ~/.config/panama is theirs too -- settings.json
+# lives there. A symlinked directory would put their scripts in the repository
+# working tree, which is the mistake the gtk bookmarks made.
+PANAMA_HOOK_SAMPLES="$PANAMA_DOT/panama/hooks"
+USER_HOOK_DIR="${XDG_CONFIG_HOME:-$HOME/.config}/panama/hooks"
+if [ -d "$PANAMA_HOOK_SAMPLES" ]; then
+  mkdir -p "$USER_HOOK_DIR"
+  for sample in "$PANAMA_HOOK_SAMPLES"/*.sample; do
+    [ -e "$sample" ] || continue
+    sample_dst="$USER_HOOK_DIR/$(basename "$sample")"
+    if [ -e "$sample_dst" ]; then
+      log "Keeping existing hook sample at $sample_dst"
+    else
+      cp "$sample" "$sample_dst"
+      log "Copied hook sample → $sample_dst"
+    fi
+  done
+fi
+
 PANAMA_NAUTILUS_DIR="$PANAMA_PATH/config/local/share/nautilus-python/extensions"
 USER_NAUTILUS_DIR="${XDG_DATA_HOME:-$HOME/.local/share}/nautilus-python/extensions"
 if [ -d "$PANAMA_NAUTILUS_DIR" ]; then