[s1f102500012]

With RimBridgeServer installed, TickManager.UltraSpeedBoost is switched on at startup and stays on, so speed 4 changes for normal play too: vanilla Ultrafast jumps to the debug rate, and mods that mirror vanilla's boost branch (e.g. Smart Speed, where a configured 15x becomes 150x) multiply their own rate. Players who only have the mod installed for occasional agent sessions see this without asking for it — similar to the camera zoom extension in #4.

This keeps the boost for automation but scopes it to the runs that need it:

• RimBridgeStartup no longer sets UltraSpeedBoost.
• play_for and play_until_letter turn the boost on when the requested speed is Ultrafast (or forceRequestedSpeed is set) and restore the previous value afterwards, including on the failure path. Other speeds leave the flag untouched.
• set_time_speed with ultraSpeedBoost still sets it explicitly for the session.
• Tool descriptions and the README playback note are updated; docs/tool-reference.md and the README tool surface are regenerated.

Testing:

• scripts/build-mod.sh --test: build ok, 212 tests pass.
• Live check over GABP against a running game (quicktest map), before vs after:

	2.3.0	this branch
UltraSpeedBoost right after startup	true	false
play_for Normal, 1.5 s	flag stays true	flag untouched (false)
play_for Ultrafast, 1.5 s	8720 ticks, flag still true after	6886 ticks, flag restored to false
set_time_speed with ultraSpeedBoost true/false	works	works

The live check ran on the RimWorld 1.7 unstable branch (that is the build I have locally), not on 1.6.