FV: enforce terminal resource limits in the padding replay entrypoint #1099

The existing contracts/verification/sha256-padding/replay.py checks elapsed time and allocated bytes only inside while proc.poll() is None. A child that exits between observations bypasses the terminal resource checks. It then records/accepts a completed proof without checking the final allocation/time against the configured limits.

This is the same concrete termination-boundary pattern reproduced and corrected in the new constructor runner in #1098 (commit 638171c374d5ae22bad0074b2bc4cdebe92ddb70). It concerns resource enforcement, not a newly demonstrated false mathematical theorem. The frozen original evidence is unchanged.

Bounded follow-up: add terminal elapsed/allocation checks before proof credit to the padding replay entrypoint, including receipt-allocation handling, and test immediate child completion at/over limits plus a successful below-limit control. Inspect other direct consumers of that replay implementation for the same boundary. Do not launch another full solver campaign unless source/model changes require it.

Banked outside #1098's frozen constructor publication scope. This does not activate the broader deferred assurance sweep in #509.