Added
- Self-update failure diagnostics (#43, @LeeNX). When a self-update recreate fails (seen repeatedly on rootless Podman) the reason used to vanish — the helper container runs
--rm, so its stderr was gone before anyone could read it. The helper now also mounts Docksentry's/datahost directory (resolved from our own inspect Mounts) and redirects its whole swap-script output there. On the next boot, if the recreate rolled back, Docksentry reports the captured helper output — so the actualdocker runrejection is finally visible instead of a silent brick. On success the log is consumed silently. (This is the diagnostic that should finally reveal why the Podman recreate fails; the v1.38.2 recovery-net already made it survivable.)
Full 25-script regression sweep green.