hub v0.137.0 source + burn-down round 2 in felhom.eu: R-277 R-581 R-600 R-544 R-855 R-134 R-92 R-292 R-599 R-725 R-728 (hub), R-819 R-857 R-555 R-364 R-587 (gates/tools), R-571 R-129 R-124-runbook (docs); 28 rows closed incl. catalog + agent v0.147.0 rows, R-350 merged into R-132, R-888 opened, R-887 mechanism (249 -> 222)

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
2026-10-05 19:43:37 +02:00
parent e0d884565f
commit 557629d2bf
65 changed files with 2680 additions and 122 deletions
@@ -370,6 +370,23 @@ own; every caller that is not the customer must decide for itself whether the ap
 | `storage_handlers.go` (1600 L) | **DELETE (→agent)** | Format/attach/mount/disconnect/migrate-drive/decommission disk UI. Any survivor is a **thin client calling the agent API** (e.g. per-volume placement requests). | hazard |
 | `templates/` (HTML, non-Go) | **PORT** | Remove disk-wizard + DR pages; keep app/deploy/backup/settings pages. | needs-rework |

+#### Alert placement — inline under the storage bars, or the top banner (R-571)
+
+**[FACT, read from source 2026-10-05, felhom-controller `114ff27`, `controller/internal/web/alerts.go`]** Every
+dashboard alert is an `Alert` with two placement fields: `PageOnly` (the pages it may appear on; empty = every
+page) and `Inline` (rendered by the page template in place, not by the layout's banner). `GetAlerts` returns
+the list (endpoint-drift, agent-channel and dead-app alerts first, then the rest sorted error > warning > info,
+capped at five plus an overflow line), and `layout.html` paints only those that are not `Inline` and match the
+page; `GetInlineAlerts(page)` hands the dashboard and monitoring pages their inline ones.
+
+**Exactly one warning is inline today:** the „storage is not on a separate drive" health warning. It is
+`PageOnly: dashboard, monitoring` and `Inline: true`, so it sits quietly under the storage bars; **every other
+warning, including every off-site failure (`07` §6.7), renders in the top banner on every page.** The choice
+is made by the warning's KIND (`monitor.WarnKindStorageNotSeparate`, read with `report.WarningKindAt`), never
+by its words — the earlier Hungarian-substring test would have moved the warning to the red banner on every
+page the day the sentence was translated (R-553, pinned by `TestR553_DiskWarningPlacementSurvivesWordingChange`).
+A new inline warning needs its own kind, not a text match.
+
 ### `scripts/`
 | File | Class | Reason | Risk |
 |---|---|---|---|