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

CONTEXT.md

@@ -7,7 +7,22 @@
 >
 > Ask Claude Code: "Please update CONTEXT.md with what we did today"
 
-Last updated: 2026-07-17 (v0.142.0 — offsite repo continuity: orphaned-repo guard + run-status auto-refresh)
+Last updated: 2026-07-17 (v0.143.0 — guest RAM resize UI, R-24; MinAgent 0.90.0)
+
+> **2026-07-17 — v0.143.0: guest RAM resize UI (R-24), LIVE on demo. MinAgent: 0.90.0.** The customer
+> sees the guest's current memory + allowed range on the **Rendszer** settings page and resizes it
+> ("Szerver memória (RAM)" card). The controller proxies + maps the agent's machine `code` to Hungarian;
+> the AGENT (felhom-agent v0.90.0) enforces every bound and applies live (no reboot — R-24's old
+> hub-desired-state framing is SUPERSEDED by Viktor's controller-direct ruling). agentapi
+> `GuestMemory`/`ResizeMemory` (`*MemoryRefusedError` carries the code); capability
+> `FeatureGuestMemoryResize` (featureMinAgent 0.90.0, probe type-asserts GuestMemory so the shared
+> SupportProber/netAgent stay untouched); `POST /api/system/memory/resize`; JS confirm only on a shrink;
+> agent-outdated hides the control, agent-unreachable falls back to the guest's `/proc/meminfo`. Deployed
+> to BOTH demo guests (felhom-pve 9201 + nested demo-vm-felhom-4846bc 9201). **LIVE-validated** through the
+> real endpoint on the nested demo (above_max + below_min refusals render the Hungarian message; the agent
+> English never leaks; the capability gate resolves SupportYes via the 0.90.0 version header). A successful
+> grow couldn't be shown on the tiny 4 GB nested host (max<current, correctly refused); the apply is
+> Phase-0-proven at the agent layer. See REPORT.md.
 
 > **2026-07-17 — v0.142.0: offsite repo continuity (Parts A + C), LIVE on demo.** Closes the
 > reinstall-orphaned-repo incident (a recreated data volume mints a new repo passphrase → the offsite