Dashboard layout: Apps card header (R-909), launcher header wraps on a phone (R-907), overflow counted after the page filter (R-906)

- Apps card: title row (logo top-aligned, name, address cut with an ellipsis and full in title) over a wrapping
  .stack-tags row; the tags no longer share a space-between row with the name.
- Phone (768px block): .page-header wraps; the share button drops to its own line, text whole.
- GetBannerAlerts(page, lang): the layout's filter before the cap; baseData and /monitoring use it.
- Tests: TestStackCardHeaderLayout, TestR907_PageHeaderWrapsOnAPhone, TestR906_* (all red against 05e12921).
- No Hungarian string changed. The three stacks parity fixtures are re-captured in the next commit
  (this commit alone fails TestI18nParity on them; both are pushed together).

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

CHANGELOG.md

@@ -1,3 +1,31 @@
+## Unreleased (2026-10-08, afternoon) — three dashboard layout fixes: the Apps card header (R-909), the launcher on a phone (R-907), the empty „+5 more warnings" (R-906) — ships with tomorrow's release
+
+**MinAgent: 0.131.0** (unchanged — nothing on the wire, nothing the agent sees). Hungarian text: not one string
+changed; three Apps-page parity fixtures re-captured for the markup alone (below).
+
+- **R-909 — the Apps card header.** The title row and every tag were siblings in ONE `space-between` flex row; with
+  two or more tags (any installed app) the one-word name ran under them, and the logo was centred on the name block,
+  so a card with an address carried its logo lower. Now every card has the same two rows: logo + name (+ the address
+  under it, top-aligned), then the tags in their own `.stack-tags` row, left-aligned and wrapping. The address is one
+  line cut with an ellipsis (`.subdomain-text`, `min-width: 0`), full address in `title`, „↗" on the same line; the
+  unpublished-route warning stays under it. `TestStackCardHeaderLayout` (both languages, all 8 `stacks_full` cards +
+  the CSS rules; red against 05e12921: no tags row, no address title, `space-between`, `align-items: center`).
+- **R-907 — the launcher's share button on a phone.** In the 768 px block `.page-header` wraps, so the button drops
+  to its own line under the title and the domain chip, its text kept whole (`white-space: nowrap`). It applies to
+  every page header on a phone (a header that fits is unchanged). `TestR907_PageHeaderWrapsOnAPhone` (red against
+  05e12921: the phone block had no `.page-header` rule).
+- **R-906 — „+ 5 további figyelmeztetés" with nothing above it.** `GetAlerts` capped the list at five over ALL alerts,
+  and the layout then dropped the Inline and other-page ones; on 9202 the five visible ones were inline „not on a
+  separate drive" warnings, so only the overflow line rendered and the hub-off warning was cut. New
+  `AlertManager.GetBannerAlerts(page, lang)` filters with the layout's own rule (`bannerShows`) BEFORE the cap;
+  `baseData` and the monitoring page use it. `GetAlerts` is unchanged for the debug dump. Tests `TestR906_*` (the 9202
+  case on /launcher, /stacks, /backups, /monitoring, hu and en: no overflow line, the hub-off banner shown; red with
+  the two calls pointed back at `GetAlerts` — every page showed the overflow line and no warning).
+- **Parity fixtures re-captured, in their own commit:** `stacks_full`, `stacks_unhealthy_stop`,
+  `stacks_install_interrupted`. Measured: each equals its predecessor with exactly the template change applied
+  (wrapper `stack-title-text`, the address span + `title`, the `stack-tags` row) — byte-for-byte, 3 of 3 — and the
+  visible text is identical. No other fixture moved.
+
 ## Unreleased (2026-10-08) — a daytime press never cancels the night's whole-guest backup (R-899; operator ruling 2026-10-08, option A); an honest answer when older recovery packages were not checked, and the operator's mail (R-304) — ships with tomorrow's release
 
 **MinAgent: 0.131.0** (unchanged — the new `trigger=manual` query is ignored by an older agent, which keeps running the