Stacks: remote stacks editable from the hub, .env editing, deploy diff, image update checks; a gone container says so

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

BUGS.md

@@ -276,6 +276,21 @@ No native browser dialogs anywhere; no page errors on any of 100 page loads.
 has the ZFS tools and no pool, so there is nothing to import. Harmless, but it will sit on
 the rail as "1" until the unit is disabled or the rule is narrowed. Left alone.
 
-## Quality of life — proposed, not built (waiting on Mitchell)
+## Quality of life — five chosen by Mitchell, ✅ built and verified 2026-09-19
 
-See the list sent with this pass.
+1. ✅ **Stacks on `grid` and the Mac are editable from the hub.** Their files live on `core`
+   (Dockhand deploys over tcp); the hub resolves them and runs compose with `DOCKER_HOST`
+   pointed at the node. Verified on a throwaway stack: saved on `core`, recreated **on
+   `grid`**, same compose labels, nothing created on `core`, output followed on the page.
+2. ✅ **A stack's `.env` is editable**, values masked until "Reveal and edit". A `.env` that
+   breaks the compose file (a required variable removed) is refused and the old one put back.
+6. ✅ **A link to a container that no longer exists says so**, by name.
+9. ✅ **"Update available" per image** — on request, remembered six hours. Verified with an
+   image whose tag had moved on (update available) beside a current one (up to date).
+10. ✅ **What Deploy would change**: a line diff against what was last deployed from here;
+    after a deploy it says there is nothing left to change. `.env` diffs name the key and
+    never show a value.
+
+Not chosen, still open: alert acknowledge/snooze; quiet hours and per-rule channels; push
+straight from Ham Lab; a type hint in the alert editor; switching off the nodes' own alert
+engines.