Memory and Stack Budget Agent

Small increases in flash, RAM and stack use add up until a build no longer fits or a task overflows in the field. After each build this agent reads the linker map file and totals the sections. It compares them with the budget and with the previous build, and traces the largest growth to specific files and functions. It reads stack high-water marks from test runs and flags tasks using more than a set share of their stack. It proposes savings such as compiler flags, a smaller buffer or removing dead code, then rebuilds to confirm the numbers. The engineer approves any code change. Edge case: the map shows growth from a debug option left on, so the agent proposes switching it off instead of rewriting code.