docs: v0.143.0 REPORT + CONTEXT + README (guest RAM resize UI, R-24; deployed + live-validated on demo)

controller/README.md

@@ -110,6 +110,16 @@ backups, monitoring and notifications. All Proxmox/disk operations are delegated
   JetBrains Mono, variable woff2, latin+latin-ext) and a 30-icon Lucide sprite are vendored in the
   binary** (`internal/web/static/fonts/` served at `/static/fonts/`; `templates/icons.html`) — no CDN,
   no emoji. The setup wizard serves the same embedded stylesheet via `web.StyleCSS()`.
+- **Guest RAM resize (v0.143.0, R-24; MinAgent 0.90.0)** — the Rendszer page's "Szerver memória (RAM)"
+  card shows the guest's current/used memory + the allowed range and lets the customer resize it. The
+  controller only proxies + maps the agent's machine `code` to Hungarian; **the agent (felhom-agent
+  v0.90.0) enforces every bound and applies the change live via PVE SetConfig — no reboot** (min 2048 /
+  max host_total−2048 / a shrink is refused below max(2048, usage+512)). `systemPageData` calls
+  `memoryCardData` (a 2 s agent GET behind the `FeatureGuestMemoryResize` gate); `POST
+  /api/system/memory/resize` (`ServeSystemAPI`, `internal/web/system_memory_handlers.go`) →
+  `agentapi.ResizeMemory` → the code→Hungarian map. A JS confirm fires only on a shrink; an outdated agent
+  hides the control; an unreachable agent falls back to the guest's own `/proc/meminfo`. Memory only
+  (cores stay observation). The lxcfs ripple means the deploy-page memory math follows a resize for free.
 - **Page IA (v0.97.0, TASK-D1)** — the settings monolith is split into four pages, each with its own
   data builder (`systemPageData`/`storagePageData`/`notificationsPageData`/`securityPageData`, sharing
   `settingsBaseData`) and template. Routes: `/settings` (Rendszer), `/settings/notifications`