Run compose like the terminal does, and follow changes made there (0.67.2)

StackPilot called `docker compose -p <folder> -f compose.yaml`, which is
not what `docker compose` typed in the stack's folder does. A
compose.override.yaml or a COMPOSE_FILE in .env applied in a terminal
and was dropped by the next Start in StackPilot, which recreated the
containers without it. A compose file's `name:` or a COMPOSE_PROJECT_NAME
in .env made the terminal's containers invisible: the stack showed as
stopped while running, and Start set up a second copy next to it.

Compose now runs in the stack's folder without -f, so it loads the same
files, and -p is the name compose itself picks there: COMPOSE_PROJECT_NAME
from .env, else the last `name:` among the compose files (${VAR} from
.env), else the folder name. A stack StackPilot already runs under its
folder name keeps that name while it has containers or volumes under it
and none under the declared one: switching would have brought it up
again on empty volumes. Backups record the project, and a restore takes
it from the files it has just put back.

Changes made outside StackPilot now reach every view:

- docker_watch_service reads Docker's events once for the backend. The
  dashboard rollup (cached 25s) and the stats cache are stale as soon as
  the event generation moves; the tiles followed a terminal `compose
  stop` after 15-30s, now within a second.
- Image events re-read the local digests, so a `docker compose pull` in
  a terminal clears the update badge instead of leaving it until the
  next registry check (an hour by default).
- The browser catches up when its event socket reconnects; what changed
  while it was down waited for the 60s poll.
- The stack detail carries a revision of the compose file and .env;
  saving after they changed on disk is refused with 409 and the editor
  offers to overwrite or to load the version on disk. A save used to
  replace a terminal edit without a word.
- A stack whose folder is gone is flagged "folder missing" instead of
  passing for an ordinary stopped stack.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fx7gcuy8d6nPd95g43rGHu

backend/services/stats_service.py

@@ -19,6 +19,7 @@ import time
 from concurrent.futures import ThreadPoolExecutor
 
 from docker_client import DockerError, get_client, safe_call
+from services import docker_watch_service
 
 COMPOSE_PROJECT_LABEL = "com.docker.compose.project"
 
@@ -85,18 +86,27 @@ def stack_stats(refresh: bool = False) -> dict:
     when none of them have that limit set. Served from a short-lived cache
     unless ``refresh`` is set.
     """
-    if not refresh and _cache["data"] is not None:
-        if time.monotonic() - _cache["ts"] < CACHE_TTL:
-            return _cache["data"]
+    def fresh() -> bool:
+        # Also stale once Docker reported a change (a container stopped in a
+        # terminal), see services/docker_watch_service.py.
+        return (
+            _cache["data"] is not None
+            and time.monotonic() - _cache["ts"] < CACHE_TTL
+            and _cache.get("gen") == docker_watch_service.generation()
+        )
+
+    if not refresh and fresh():
+        return _cache["data"]
 
     with _lock:
         # Somebody may have refreshed it while we waited for the lock.
-        if not refresh and _cache["data"] is not None:
-            if time.monotonic() - _cache["ts"] < CACHE_TTL:
-                return _cache["data"]
+        if not refresh and fresh():
+            return _cache["data"]
+        gen = docker_watch_service.generation()
         data = _sample()
         _cache["data"] = data
         _cache["ts"] = time.monotonic()
+        _cache["gen"] = gen
         return data