Problem
Many processes legitimately allocate heavily at startup (loading configs, building caches, JIT compilation). --leak-check currently fires immediately from baseline, meaning any post-baseline startup allocation is flagged as a leak.
Proposed Solution
Add --warmup that suppresses all limit and leak enforcement for the first N seconds. After the warmup period, a fresh baseline snapshot is taken and enforcement begins from there.
branch: feature/cicd
Problem
Many processes legitimately allocate heavily at startup (loading configs, building caches, JIT compilation). --leak-check currently fires immediately from baseline, meaning any post-baseline startup allocation is flagged as a leak.
Proposed Solution
Add --warmup that suppresses all limit and leak enforcement for the first N seconds. After the warmup period, a fresh baseline snapshot is taken and enforcement begins from there.
branch: feature/cicd