v0.147.3 — 4c follow-up 3: the run does not end with the last app

Third real run, third thing only a live run could show. The per-app legs
finished in ~15 seconds; the remaining 40 of the 57-second run was the shares leg
and forget --prune, during which the card sat frozen on "calibre-web — 8 / 8
fájl". The same frozen-looking silence 4c exists to remove, relocated to the end.

Progress now carries a phase. The post-app stages announce themselves and the
app-scoped counters are cleared when a phase starts, so the last app's finished
numbers are never shown against work that is no longer about that app. Starting
the next app clears the phase again. Pinned by a test.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Nn3VgQk9iwEGgyx6QJ2NvE

CHANGELOG.md

@@ -1,5 +1,17 @@
 ## Changelog
 
+### v0.147.3 — 4c follow-up 3: the run does not end with the last app (2026-07-19)
+
+Third real run, third thing only a live run could show. The per-app legs finished in ~15 seconds;
+the remaining **40 of the 57-second run** was the shares leg and `forget --prune` — during which the
+card sat frozen on „calibre-web — 8 / 8 fájl". The same frozen-looking silence 4c exists to remove,
+relocated to the end of the run.
+
+Progress now carries a **phase**. The post-app stages announce themselves („Megosztott mappák
+mentése…", „Karbantartás: régi mentések rendezése a távoli tárolón…") and the app-scoped counters are
+cleared when a phase starts, so the last app's finished numbers are never shown against work that is
+no longer about that app. Starting the next app clears the phase again. Pinned by a test.
+
 ### v0.147.2 — 4c follow-up 2: when NO counter can move, say what is being worked on (2026-07-19)
 
 The v0.147.1 file-count fallback fixed the incremental case but not the one the demo box actually