acamilo a3c1c125cd session: negative fixtures for the allocation, and honest resolution bounds ... Two review notes. The launcher allocation became a required field of HelloResult.limits with no negative fixture behind it. Three rows now cover it: missing, above maxWorkerThreads, and zero. Both readers reject all three, and no derived fixture moved, because invalid.json is not one of them. The resolution's two bounds disagreed. 512 attempts at a 2 ms pause give up near 1.5 s, so the attempt count silently pre-empted the 8 s budget the doc comment advertised. The budget is now the working limit and says so: the guard is 8192 attempts, over sixteen seconds of pauses against an eight-second budget, so at the default values the budget is always what fires. Which one did is no longer arithmetic either -- ResolutionEnd records it, the failure message names the bound and its size, and the code, the doc comment and the README all state the same numbers. a_resolution_says_which_of_its_two_bounds_ended_it drives each bound to the end in every execution mode.		2026-09-22 16:00:13 +00:00
..
common	session: parallel processes, a launcher and the fault behaviour	2026-09-22 14:33:25 +00:00
failures.rs	session: resolve uncertain calls, and measure each mode in its own process	2026-09-22 15:41:42 +00:00
processes.rs	session: negative fixtures for the allocation, and honest resolution bounds	2026-09-22 16:00:13 +00:00
session.rs	session: resolve uncertain calls, and measure each mode in its own process	2026-09-22 15:41:42 +00:00