v0.348.0: CHANGELOG heading — the release build's commit

CHANGELOG.md

@@ -1,4 +1,6 @@
-## Unreleased (2026-10-29, afternoon) — clear_hold (D64 = B), the box command through the running controller (R-1343), R-1340, R-1341; commit only, rides the next release
+## v0.348.0 (2026-10-29) — clear_hold from the hub (D64 = B); the box command clears through the running controller (R-1343); the held-app mail and line name the real cause (R-1340); the OOM line once per kill (R-1341); the restore copy safe during the stable-start watch (R-1342) — built from the commit carrying this heading
+
+### 2026-10-29 (afternoon)
 
 **MinAgent: 0.158.1** (unchanged). The next release also carries R-1342 (`652a690`, already on main, the entry below).
 **No new event type** — the hub records the operator action's result as its own `operator_action` event.
@@ -51,7 +53,7 @@
   `app_oom` event call is unchanged. Tests: `TestR1341_ASecondScanOfTheSameKillLogsNothing`, `_ANewKillLogsAgain`,
   `_ARestartedContainerLogsAgain`, `_ContainersAreJudgedApart`.
 
-## Unreleased (2026-10-29, after v0.347.0) — R-1342: the restore copy is safe during the stable-start watch; a removed app does not alarm; commit only, rides the next release
+### 2026-10-29 (after v0.347.0) — R-1342: the restore copy is safe during the stable-start watch; a removed app does not alarm
 
 **MinAgent: 0.158.1** (unchanged). Found live on Tester 1 at 10:39 CET: a false `backup_run_failures` mail („Gokapi did
 not start … the pre-restore copy is kept") after the copy had been deleted by hand mid-watch and the app removed.