Cross-block event handling: separate always_ff blocks don't see each other's events

When one always_ff block clears a register on an external event (e.g. RESUME clearing throttle_limit), a separate always_ff countdown block (pace_count) has no visibility into that event and keeps counting down the old value. Fix by giving the consuming block its own event input (e.g. resume_hit) as the highest-priority branch that reloads the countdown immediately. Check this whenever two blocks share a state variable's lifecycle.