Skip to content

Autonomous development for real products. Governed agents build from specs you approve, follow the rules you set, and nothing merges until another agent proves it. Your decisions, judgement and taste are the bar that work must clear. Declare your vision and let agents build it.

docs(gate): the pool's header describes call-bound loans [C7]

Corey Olson5c59069b2e77
diff --git a/src/test-file-pool.js b/src/test-file-pool.js
index 8faf6159..206ae7ed 100644
--- a/src/test-file-pool.js
+++ b/src/test-file-pool.js
@@ -5,11 +5,10 @@
* Measured 22 Oct: 28 runs at --test-concurrency=10 kept 54 file processes live on 14 cores, and passing files
* ran 18.5 times slower in landings than alone. A per-run limit cannot see the other runs; this pool can.
*
- * A test file that starts its own run-tests with a synchronous call (so it is blocked until the run exits) lends its
- * token to that nested run: while the nested run lives, its parent counts as waiting, not running, so the nested
- * files take the parent's place and never a second core. The parent's place stays reserved while none of its nested
- * files holds one, so it resumes into it. A run started asynchronously gets no loan, since its parent may compute.
- * Two nested runs of one parent share its one place; neither can wait forever on the token its own parent holds.
+ * A test file that starts a nested run with a synchronous call is blocked until that call returns, so it lends its
+ * place for the call: the call's files fill that place one at a time and never take a second core, and the call
+ * returns only after the last of them exits, so the file resumes into its own place. Nothing it starts can wait
+ * forever on the token it holds. A run started asynchronously, or left behind by the call, borrows nothing.
*/
import { randomUUID } from 'node:crypto';
import { mkdirSync } from 'node:fs';