Thirty-Two Below (Day 10, warmups)
- Pun: "Thirty-Two" = Base32 ("Smaller alphabet" than Base64).
- Artifact: blob.txt, a single Base32 layer (decode_chain.py: base32).
- Decoded text: "Nice work decoding this warmup! To solve, submit this exact answer to the Game Master: groovy-starfish-willow-93"
- Answer slug (Single Solve): groovy-starfish-willow-93 -> CORRECT (autosolve_warmups.py, existing base32 support).
- Time Trial: Token677fa4f92981a442393270115722d4ad -> CORRECT (13:02:34Z).
- Mastery: Tokenbda9a503ce17ffbee4f41b437cb42a1b -> CORRECT (13:02:35Z).
Correction to the first draft of this writeup
This file originally recorded Time Trial / Mastery as blocked by a "server-side gate", because the first start returned 409 timed_intent_not_available. That was never a gate: on a LEGACY single-pool timed route the GM rejects the run_for_time property outright (true OR false), while a plain op=start with the property omitted opens a normal, hall_of_fame_eligible attempt. Both modes were in fact solved by the same unchanged adapter two minutes later. Root cause + the permanent fix (in ctf_gm.GM.start and autosolve_script.start, with regression cases in _test_rotation_fix.py) are written up in challenges/Day 10/Bind Over Matter/Bind_Over_Matter_Writeup.md - that lane was the one that stayed stuck on it for ~4 hours. Day 10 finished 15/15.