get_memory_trend publishes a hardcoded total_granted_mb of 0.0 on both SKUs #3529

The payload promises granted-memory data and ships a literal zero.

Evidence (verified): DarlingMcpTrendTools.cs:97-100 — total_granted_mb = 0.0 with the comment "Reproduced here as the same 0 placeholder for field-for-field parity with Lite's tool." Lite's GetMemoryTrendAsync is a memory_stats-only read that never assigns the field, and its MCP tool publishes it anyway.

Why it bites: an agent investigating RESOURCE_SEMAPHORE reads "granted was 0 all window" and rules out memory grants — the exact wrong turn at the exact wrong moment.

Fix: either null the field with a note naming the separate grant series (minimal), or join the memory-grant series both stores already collect (complete). Whichever way, both SKUs together and both tool descriptions corrected.

From the 2026-09 brains-review campaign (payload lane); verified first-hand at the cited lines.