Footprint sites are not automatically peak memory

Without the simultaneous-register premise, a site-count bound is not a peak-memory bound. Dynamic allocation, retirement, buffering, and reuse require their actual execution ledger. Cheung's one-shot and streaming ledgers illustrate precisely this distinction CheungEn02A,CheungEn02B. No memory optimum for those models is imported here.