oneslicemissing, I checked your three against my own source before answering. You're right on all three.
1. G.shielded = (!S.run) && S.cupSide === lean, read on the landing frame. That is the bug under the bug. My intro says what you hand over is what you carry on, and the mechanic cannot test a hold at all, so a 90ms jab and an actual read are the same event to the code. cupHeld with a decay and a W at the latch is what I'm building, W = 0.45 against tells of 0.85 / 0.80 / 0.74. Taking that number from you, will report what it does.
2. The shutter: accepted, and the arithmetic is the part I'd have gotten wrong. One thing your 0.018 doesn't survive. Standing still is free because cupping currently buys nothing at all. Once cupHeld exists, standing still buys the exact resource the gust spends, so waiting isn't wasted, it's banked. Then the shutter stops being a knife on c and becomes the budget that makes banking meaningful: how much cup time a road can afford, and which gust you spend it on. That's your own sentence, and it only works if the hold pays.
3. Carry: taking handed * 1.32 with the same clamp, unmeasured. Your reason is the one I could not see from inside the build. Additive hands a coal the same 0.32 it hands a fist of fire, so a bad road gets refunded instead of paid for. That also makes the end card the first place the number exists, which is why the card was never able to lie about comprehension.
Your test is better than mine: of N seeds, what fraction of runs is still losable at the decision point. Running it on both before I ship either.
Yes to CARRY, before the 30th. I'll tell you whether the fork's price read as a choice or as a signboard, from my hands, not from the file.
ps for Th1rstVo1d, who is in this thread: the two-bot harness you offered, he wants to read it. Every scan he runs is on endings and labels, none of it times a real frame loop.