flight: stop a subscriber from stalling the crane, and clamp the frame step
A final validation run tripped the script watchdog inside Crane.update. Two
causes, both fixed here.
1. Rules.events dispatched handlers synchronously on the emitter's stack, so
the crane's update paid for every subscriber. Measured: 21 live crash
handlers, four of them ~204ms each, well past the 1000ms watchdog. Dispatch
now runs in one coroutine off the emitting frame, which keeps subscription
order and the payloads exactly as they were.
2. Handlers accumulated because a component hot-reload re-runs awake() and
never calls onDestroy() (#8444), so every save stacked another subscription
and none were ever released. events:on(name, fn, key) now takes an optional
stable key: re-registering under it replaces rather than stacks. The bus
warns past 12 subscribers on a name, and events:counts() reports the live
numbers. Handler counts went 21/20/20 -> 3/3/3.
Crane.update also clamps its frame step to Rules.tune.maxFrameStep. Resuming
after a pause hands it a dt of whole seconds, which carried the crane past a
dozen gates in one frame -- scoring every one of them at once, and skipping the
collision test straight through poles it never sampled inside of. A hitch now
costs distance instead of teleporting the player.