full constant

pumpAndSettle's own semantics, ten-minute timeout and throw included.

The one policy that records no motion: pumpAndSettle is the SDK's loop and offers no per-frame hook, and reimplementing it here to get one would be trading the exact semantics this policy exists to provide for a nicety.

apply lands around the loop rather than inside it, which is the whole of what a hookless policy can do. Before is enough for anything that only needs to be told where to head: the software keyboard reads the app's focus there, points its ticker at the right height, and pumpAndSettle waits the slide out like any other animation. After is for what the loop itself changed — a settle that navigates away from a form takes the focus with it, and a policy that only sampled at the start would leave the keyboard staged at a height nothing on screen is asking for, for the next verb to discover.