Fix A (found live on 9202): the container sampler reads docker inspect JSON — a -f template stopped at 'no entry for key Health' for every app without a healthcheck, so a healthy restore read 'not started'. Commit only.

CHANGELOG.md

@@ -39,6 +39,11 @@ says „not started yet", alarms the operator; a late start is a success; never
   testing: the watch starts inside its own restore, before the page's record ends, so „a restore of the app runs"
   alone ended every watch at once and would have kept every copy (`TestFixA_AStableAppReleasesTheCopyAfterTheWindow`
   in the production order, seen failing with the plain check). Each watch reads its timing once, at its start.
+- **Found live on 9202:** the container sampler first read `docker inspect -f '…{{if .State.Health}}…'`; for a
+  container with NO healthcheck Docker stops with „map has no entry for key Health", so every such app read „not
+  started" (a healthy Vikunja restore was reported not started). It reads the inspect JSON now
+  (`parseContainerSamples`, `TestFixA_ParseContainerSamples`); the sampler's error keeps Docker's stderr, and a DEBUG
+  line says why a sample was not ok.
 - **Fix B (R-1279, `appexport/restore.go`):** the import asks the restores' own D48 helper (`PrepareRestoreImages`,
   passed in by main.go — the package may not import `backup`) about the bundle's definition BEFORE step 1 removes the
   running app's volumes; a version that cannot be downloaded refuses with the two D48 sentences and nothing changed.