`scripts/test_requests.py`'s `until_time` passes any two digits for the
month, day, hour and minute to `time.strptime`, which raises on a date
like 2026-13-12 or 99:99. `replay()` did not catch it, so one mistyped
claim line in the room (`claim: until 2026-13-12 16:40Z`) stopped every
command that replays the room, for everyone, until that line left the
fetched history.

## Change

`until_time` returns `None` for a date that is not one, so the claim
gets the default length, as a claim without a date already does.

## Testing

- `tests/test_test_requests.py`, new cases: claims with month 13 and
with 99:99 replay, and each claim gets the default length. They fail on
main (`ValueError`) and pass here.
- Full suite on Linux: 442 passed, 85 skipped, 1 failed
(`test_bake_portability`: `zstandard` is not installed on this machine;
it fails the same on main).

@@ -94,0 +114,4 @@
+
+### Which commit?
+
+`request` pins the PR's head at that moment. For example, on November 12, Hookshot's PR #2731 moved from `bce3d17e` to

@@ -16,3 +16,3 @@
 #endif
 
-#define MKWVK_API_VERSION 21
+#define MKWVK_API_VERSION 22

@@ -518,0 +578,4 @@
+   had gone stale and been given back, so the first upload of the next burst made another. On an empty device they are cheap.
+   RX_VK_STAGING_PREWARM=<n>: how many, 0: none. */
+}  // namespace (the prewarm is called from the replay's start: it has to link)
+void texture_staging_prewarm(int n) {

@@ -2347,0 +2561,4 @@
+bool game_order() {
+    static const bool on = [] {
+        const char* e = getenv("RX_VK_GAME_ORDER");
+        const bool v = e ? !env_value_off(e) : dev.props.vendorID == 0x10de;

@@ -0,0 +1,695 @@
+"""Development builds as a base and small packs over it: build the game once, then build only what a change touches and run it