@smoothbricks/nx-plugin 0.7.18 → 0.7.19

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (143) hide show
  1. package/README.md +160 -99
  2. package/dist/.build-inputs.json +35 -29
  3. package/dist/built-output-packages.js +1 -1
  4. package/dist/cargo-closure-input.js +1 -1
  5. package/dist/cargo-source-hash.d.ts +3 -21
  6. package/dist/cargo-source-hash.d.ts.map +1 -1
  7. package/dist/cargo-source-hash.js +4 -91
  8. package/dist/cargo-toolchain-paths.d.ts +2 -2
  9. package/dist/cargo-toolchain-paths.js +2 -2
  10. package/dist/cargo-workspace.d.ts.map +1 -1
  11. package/dist/cargo-workspace.js +2 -1
  12. package/dist/executors/bounded-exec/admission-queue.d.ts +3 -1
  13. package/dist/executors/bounded-exec/admission-queue.d.ts.map +1 -1
  14. package/dist/executors/bounded-exec/admission-queue.js +9 -10
  15. package/dist/executors/bounded-exec/awake-clock.d.ts +5 -0
  16. package/dist/executors/bounded-exec/awake-clock.d.ts.map +1 -0
  17. package/dist/executors/bounded-exec/awake-clock.js +22 -0
  18. package/dist/executors/bounded-exec/bounds.d.ts +7 -5
  19. package/dist/executors/bounded-exec/bounds.d.ts.map +1 -1
  20. package/dist/executors/bounded-exec/bounds.js +14 -11
  21. package/dist/executors/bounded-exec/case-gate.d.ts +114 -0
  22. package/dist/executors/bounded-exec/case-gate.d.ts.map +1 -0
  23. package/dist/executors/bounded-exec/case-gate.js +342 -0
  24. package/dist/executors/bounded-exec/cpu-pool-thread.d.ts +1 -0
  25. package/dist/executors/bounded-exec/cpu-pool-thread.d.ts.map +1 -1
  26. package/dist/executors/bounded-exec/cpu-pool-thread.js +2 -2
  27. package/dist/executors/bounded-exec/cpu-pool.d.ts +28 -1
  28. package/dist/executors/bounded-exec/cpu-pool.d.ts.map +1 -1
  29. package/dist/executors/bounded-exec/cpu-pool.js +102 -16
  30. package/dist/executors/bounded-exec/endpoint-life.d.ts +146 -0
  31. package/dist/executors/bounded-exec/endpoint-life.d.ts.map +1 -0
  32. package/dist/executors/bounded-exec/endpoint-life.js +228 -0
  33. package/dist/executors/bounded-exec/executor.d.ts.map +1 -1
  34. package/dist/executors/bounded-exec/executor.js +207 -69
  35. package/dist/executors/bounded-exec/gateway-lease.d.ts +1 -1
  36. package/dist/executors/bounded-exec/gateway-lease.d.ts.map +1 -1
  37. package/dist/executors/bounded-exec/gateway-lease.js +8 -1
  38. package/dist/executors/bounded-exec/go-run-summary.d.ts +51 -0
  39. package/dist/executors/bounded-exec/go-run-summary.d.ts.map +1 -0
  40. package/dist/executors/bounded-exec/go-run-summary.js +98 -0
  41. package/dist/executors/bounded-exec/hang-diagnostics.d.ts +3 -3
  42. package/dist/executors/bounded-exec/hang-diagnostics.d.ts.map +1 -1
  43. package/dist/executors/bounded-exec/hang-diagnostics.js +66 -48
  44. package/dist/executors/bounded-exec/lease-wait.d.ts +1 -0
  45. package/dist/executors/bounded-exec/lease-wait.d.ts.map +1 -1
  46. package/dist/executors/bounded-exec/lease-wait.js +1 -0
  47. package/dist/executors/bounded-exec/mbx-pool.d.ts +28 -7
  48. package/dist/executors/bounded-exec/mbx-pool.d.ts.map +1 -1
  49. package/dist/executors/bounded-exec/mbx-pool.js +30 -9
  50. package/dist/executors/bounded-exec/mbx-reservations.d.ts +8 -5
  51. package/dist/executors/bounded-exec/mbx-reservations.d.ts.map +1 -1
  52. package/dist/executors/bounded-exec/mbx-reservations.js +187 -283
  53. package/dist/executors/bounded-exec/parent-grant.d.ts +2 -0
  54. package/dist/executors/bounded-exec/parent-grant.d.ts.map +1 -1
  55. package/dist/executors/bounded-exec/parent-grant.js +1 -0
  56. package/dist/executors/bounded-exec/pool-admission.d.ts +29 -3
  57. package/dist/executors/bounded-exec/pool-admission.d.ts.map +1 -1
  58. package/dist/executors/bounded-exec/pool-admission.js +47 -1
  59. package/dist/executors/bounded-exec/progress.d.ts +3 -0
  60. package/dist/executors/bounded-exec/progress.d.ts.map +1 -1
  61. package/dist/executors/bounded-exec/progress.js +31 -1
  62. package/dist/executors/bounded-exec/reservation-connection.d.ts +90 -0
  63. package/dist/executors/bounded-exec/reservation-connection.d.ts.map +1 -0
  64. package/dist/executors/bounded-exec/reservation-connection.js +248 -0
  65. package/dist/executors/bounded-exec/run-cpu-pool.d.ts.map +1 -1
  66. package/dist/executors/bounded-exec/run-cpu-pool.js +3 -0
  67. package/dist/executors/bounded-exec/runner-sizing.d.ts +9 -5
  68. package/dist/executors/bounded-exec/runner-sizing.d.ts.map +1 -1
  69. package/dist/executors/bounded-exec/runner-sizing.js +13 -9
  70. package/dist/executors/bounded-exec/schema.d.ts +2 -2
  71. package/dist/executors/bounded-exec/suite-minimum.d.ts +21 -0
  72. package/dist/executors/bounded-exec/suite-minimum.d.ts.map +1 -0
  73. package/dist/executors/bounded-exec/suite-minimum.js +85 -0
  74. package/dist/executors/bounded-exec/test-result-writer.d.ts +2 -0
  75. package/dist/executors/bounded-exec/test-result-writer.d.ts.map +1 -1
  76. package/dist/executors/bounded-exec/test-result-writer.js +1 -0
  77. package/dist/executors/bounded-exec/test-results.d.ts +5 -0
  78. package/dist/executors/bounded-exec/test-results.d.ts.map +1 -1
  79. package/dist/executors/bounded-exec/test-results.js +2 -2
  80. package/dist/executors/bounded-exec/verdict.d.ts +26 -4
  81. package/dist/executors/bounded-exec/verdict.d.ts.map +1 -1
  82. package/dist/executors/bounded-exec/verdict.js +26 -5
  83. package/dist/executors/cargo-zigbuild/executor.d.ts +10 -8
  84. package/dist/executors/cargo-zigbuild/executor.d.ts.map +1 -1
  85. package/dist/executors/cargo-zigbuild/executor.js +32 -19
  86. package/dist/index.d.ts.map +1 -1
  87. package/dist/index.js +105 -73
  88. package/dist/managed-files/ci-workflow.d.ts +4 -1
  89. package/dist/managed-files/ci-workflow.d.ts.map +1 -1
  90. package/dist/managed-files/ci-workflow.js +9 -14
  91. package/dist/managed-files/files.d.ts +3 -3
  92. package/dist/managed-files/files.js +3 -3
  93. package/dist/task-results.js +2 -1
  94. package/dist/workspace-config-policy.d.ts.map +1 -1
  95. package/dist/workspace-config-policy.js +135 -42
  96. package/executors.json +2 -0
  97. package/managed/raw/envrc +24 -0
  98. package/managed/raw/patches/nx@24.0.3.patch +1179 -133
  99. package/managed/raw/patches/ttsc@0.37.1.patch +1055 -0
  100. package/managed/raw/tooling/direnv/developer-links.ts +105 -11
  101. package/managed/raw/tooling/direnv/devenv.smoo.nix +20 -19
  102. package/package.json +67 -11
  103. package/runtime/nx-publish/.build-inputs.json +2 -2
  104. package/runtime/nx-publish/cache_adapter.js +293 -3
  105. package/runtime/nx-publish/nx_publish.js +36 -14
  106. package/src/built-output-packages.ts +1 -1
  107. package/src/cargo-closure-input.ts +1 -1
  108. package/src/cargo-source-hash.ts +16 -132
  109. package/src/cargo-toolchain-paths.ts +2 -2
  110. package/src/cargo-workspace.ts +1 -2
  111. package/src/executors/bounded-exec/admission-queue.ts +11 -10
  112. package/src/executors/bounded-exec/awake-clock.ts +20 -0
  113. package/src/executors/bounded-exec/bounds.ts +28 -15
  114. package/src/executors/bounded-exec/case-gate.ts +365 -0
  115. package/src/executors/bounded-exec/cpu-pool-thread.ts +3 -3
  116. package/src/executors/bounded-exec/cpu-pool.ts +139 -12
  117. package/src/executors/bounded-exec/endpoint-life.ts +279 -0
  118. package/src/executors/bounded-exec/executor.ts +280 -106
  119. package/src/executors/bounded-exec/gateway-lease.ts +6 -0
  120. package/src/executors/bounded-exec/go-run-summary.ts +137 -0
  121. package/src/executors/bounded-exec/hang-diagnostics.ts +70 -52
  122. package/src/executors/bounded-exec/lease-wait.ts +1 -0
  123. package/src/executors/bounded-exec/mbx-pool.ts +36 -9
  124. package/src/executors/bounded-exec/mbx-reservations.ts +213 -182
  125. package/src/executors/bounded-exec/parent-grant.ts +3 -0
  126. package/src/executors/bounded-exec/pool-admission.ts +59 -2
  127. package/src/executors/bounded-exec/progress.ts +37 -2
  128. package/src/executors/bounded-exec/reservation-connection.ts +221 -0
  129. package/src/executors/bounded-exec/run-cpu-pool.ts +2 -0
  130. package/src/executors/bounded-exec/runner-sizing.ts +13 -8
  131. package/src/executors/bounded-exec/schema.json +1 -1
  132. package/src/executors/bounded-exec/schema.ts +2 -2
  133. package/src/executors/bounded-exec/suite-minimum.ts +81 -0
  134. package/src/executors/bounded-exec/test-result-writer.ts +3 -0
  135. package/src/executors/bounded-exec/test-results.ts +5 -0
  136. package/src/executors/bounded-exec/verdict.ts +39 -6
  137. package/src/executors/cargo-zigbuild/executor.ts +30 -19
  138. package/src/index.ts +112 -78
  139. package/src/managed-files/ci-workflow.ts +13 -17
  140. package/src/managed-files/files.ts +3 -3
  141. package/src/workspace-config-policy.ts +161 -43
  142. package/test-timings.json +157 -147
  143. package/managed/raw/patches/ttsc@0.36.3.patch +0 -1660
package/README.md CHANGED
@@ -419,14 +419,14 @@ all three. The object moves when the toolchain moves, once, and nothing else in
419
419
  sources are not hashed instead: the managed module alone changed 43 times in the 30 days to 2026-10-26, and each edit
420
420
  would have rekeyed every cargo verdict; evaluated at those commits on Linux x86_64, the observed store objects did not
421
421
  change. rustc and cargo are not in the list on purpose. Cargo keys units on the output of rustc's version command, which
422
- is hashed beside this input, never on rustc's path. On a non-Linux host the default shell and its linux-cross profile
423
- carry different rust-std sets, so that path would split one target's key between the two shells. Only a path in the Nix
424
- store counts; a path elsewhere is ignored. A linker named only by Cargo configuration is outside this environment probe:
425
- a target that runs one must name the script itself as an input. Workspace test runners additionally hash the manifest of
426
- every package the workspace build compiles inside the Nx workspace (a member's, and a path package's that reaches the
427
- build only as some crate's dev-dependency), because those affect unified features, and the nextest
428
- executable/configuration. While the build compiles a path package outside the Nx workspace, every runner also names
429
- externalRustCrates, which then must be declared: a runner's key does not follow the test build's outputs.
422
+ is hashed beside this input, never on rustc's path. The shells of one host may carry different rust-std sets, so that
423
+ path would split one target's key between them. Only a path in the Nix store counts; a path elsewhere is ignored. A
424
+ linker named only by Cargo configuration is outside this environment probe: a target that runs one must name the script
425
+ itself as an input. Workspace test runners additionally hash the manifest of every package the workspace build compiles
426
+ inside the Nx workspace (a member's, and a path package's that reaches the build only as some crate's dev-dependency),
427
+ because those affect unified features, and the nextest executable/configuration. While the build compiles a path package
428
+ outside the Nx workspace, every runner also names externalRustCrates, which then must be declared: a runner's key does
429
+ not follow the test build's outputs.
430
430
 
431
431
  Nothing machine-local takes part. The ambient cargo environment as a whole and the global `$CARGO_HOME/config.toml` are
432
432
  deliberately not hashed: their values carry per-checkout state directories (`CARGO_INSTALL_ROOT` moves under the active
@@ -470,10 +470,13 @@ the directory it runs in). An entry naming only `cargo-lock:` nodes does not cou
470
470
  No input declaration removes a task's own target from its key. Nx 24.0.3 adds a `ProjectConfiguration` node to every
471
471
  task for its own project and for each project its `^` inputs reach (`hash_planner.rs` `gather_self_inputs`). The
472
472
  project-configuration hunk of `nx@24.0.3.patch` (`patches/README.md`) hashes that node for the task's own project from
473
- the project's root, tags and named inputs and the task's own target: its executor, outputs, options, configurations and
474
- parallelism (not `inputs`, `dependsOn`, `cache` or `//`). For a project the task's `^` inputs reach, the node hashes
475
- that project's root, tags and named inputs. An edit to one target's command re-keys that target's tasks. Its sibling
476
- targets, each inferred `cargo-test-*` runner among them, keep their keys unless they read the edited file.
473
+ the project's root, tags and the named inputs its `inputs` reach (a name, `^name` or `{ input }` entry, and the names
474
+ those named inputs name in turn, in `nx.json` and in any project) and the task's own target: its executor, outputs,
475
+ options, configurations and parallelism (not `inputs`, `dependsOn`, `cache` or `//`). For a project the task's `^`
476
+ inputs reach, the node hashes that project's root, tags and the same named inputs. A named input no input of the task
477
+ reaches moves none of its keys, so a project's inferred `cargoClosure` re-keys the tasks that name it and no other. An
478
+ edit to one target's command re-keys that target's tasks. Its sibling targets, each inferred `cargo-test-*` runner among
479
+ them, keep their keys unless they read the edited file.
477
480
 
478
481
  That keying is sound only while no executor reads another target's configuration at run time. An executor that does must
479
482
  have that target named in the project-configuration hunk, which then hashes it beside the reading task's own target, for
@@ -921,6 +924,12 @@ change re-keys the tasks that can load what changed and no other.
921
924
  each with what its dependencies resolved to). `cargoClosure` names its project's node; each `cargo-test-*` runner
922
925
  names its crates' nodes; workspace-wide cargo targets name the workspace root's.
923
926
 
927
+ A Cargo build's input record (`.build-inputs.json`) states the same closure, from the same resolve by the same
928
+ `buildClosure` (`@smoothbricks/build-inputs/cargo-closure`, which this plugin imports), spelled as the lockfile's own
929
+ entries so a link check can verify it without Cargo. A lockfile change therefore moves a Cargo task's key and makes
930
+ its restored output's record stale together, or does neither; a record of the whole file would refuse every output Nx
931
+ rightly restored after another crate's dependency changed.
932
+
924
933
  A hand-written target names the same nodes in its `externalDependencies`:
925
934
 
926
935
  ```json
@@ -969,10 +978,13 @@ integrity. Nx merges its default plugin's lockfile nodes after every configured
969
978
  on they would replace these: the plugin refuses the option then, and refuses a name the lockfile installs nowhere
970
979
  (`src/built-output-packages.ts`, `src/built-output-packages.test.ts`).
971
980
 
972
- The option covers the lockfile only. A member manifest that declares a named package's version is still an input
973
- wherever its project's files are; a workspace keeps the version out of member manifests by declaring it once, in the
974
- root manifest's `catalog`, and `catalog:` in each member. Inferred validation inputs omit the root's install-only pins
975
- as described below; targets producing shipped artifacts retain the raw manifests.
981
+ For a Bun text lockfile the pinned parser also keys each installed node on the selected patch bytes. The plugin
982
+ refreshes that projection even when the lock text is unchanged. A named built-output package still uses its
983
+ `built-output:<name>` identity: its actual output bytes are the task's input. Its dependencies keep their own keys,
984
+ including any patches they use. The option covers the lockfile only. A member manifest that declares a named package's
985
+ version is still an input wherever its project's files are; a workspace keeps the version out of member manifests by
986
+ declaring it once, in the root manifest's `catalog`, and `catalog:` in each member. Inferred validation inputs omit the
987
+ root's install-only pins as described below; targets producing shipped artifacts retain the raw manifests.
976
988
 
977
989
  ### Manifest versions and validation inputs
978
990
 
@@ -1035,10 +1047,12 @@ Declared gates use the emitted `smoo-nx-publish` executable from this package; t
1035
1047
  `hashes <run.json> <since-epoch-seconds>` prints the distinct succeeded task hashes as JSON, refusing a summary begun
1036
1048
  before that invocation. Capture each list immediately, before another Nx call overwrites the summary.
1037
1049
  `publish <absolute-checkout> <hashes.json>` sends existing local cache entries to that checkout's accepted-store route.
1038
- Call it only after every gate check passes. Red gates publish nothing, and ordinary shed clients stay read-only.
1039
- Publication prints stored/existing/skipped counts; an operational refusal exits nonzero with its cause. The gate reports
1040
- that cache finding distinctly without changing the checks' verdict (cowshed specs 03, "Nx accepted-task artifact
1041
- service", and 05, "Publication"). No task is rebuilt and no shell is evaluated by the publisher.
1050
+ It asks the store for each key first and never archives a stored one; a missing one it archives itself, in Nx's native
1051
+ layout at gzip level 1, and sends in one `PUT`. Call it only after every gate check passes. Red gates publish nothing,
1052
+ and ordinary shed clients stay read-only. Publication prints stored/existing/skipped counts; an operational refusal
1053
+ exits nonzero with its cause. The gate reports that cache finding distinctly without changing the checks' verdict
1054
+ (cowshed specs 03, "Nx accepted-task artifact service", and 05, "Publication"). No task is rebuilt and no shell is
1055
+ evaluated by the publisher.
1042
1056
 
1043
1057
  The canonical cache adapter and native publisher remain in
1044
1058
  `packages/cowshed/crates/cowshed-core/src/build_volume/{cache_adapter.js,nx_publish.js}`. The cached
@@ -1274,14 +1288,15 @@ Concrete targets come from concrete files:
1274
1288
  `outDir`, only when the record changed: the SHA-256 of every file the config's `include` matches less its `exclude`,
1275
1289
  taken before the emit, and those globs as Git pathspecs. Native targets write the same record from rustc's dep-info
1276
1290
  through `@smoothbricks/build-inputs`: macOS uses its `smoo-nx-build-inputs` CLI and Linux's `cargo-zigbuild` executor
1277
- calls that same collector. A record produced under Nx also carries its producer's project, target and optional
1278
- configuration, taken from the actual task environment. Shell entry uses that identity to judge the selected
1279
- development receipts, including inferred targets absent from package manifests, and name their actual cached rebuild.
1280
- It constructs no Nx graph, shadow output registry or second interpolation policy. The record is inside the target's
1281
- outputs, so a cache hit restores it with them; a live developer link (`@smoothbricks/cli`, "Declared Links") checks it
1282
- to tell a current build from a stale one by content. The shell entry that bootstraps the plugin
1283
- (`tooling/direnv/enter-shell.ts`) keeps its build marker under `node_modules/.cache`, not under `outDir`, where the
1284
- executor would remove it as a file its emit did not write.
1291
+ calls that same collector. Such a record states its lockfile input as `cargoLock`, the closure a `cargo-lock:` node
1292
+ digests (Lockfile scope), and never lists `Cargo.lock` as a file. A record produced under Nx also carries its
1293
+ producer's project, target and optional configuration, taken from the actual task environment. Shell entry uses that
1294
+ identity to judge the selected development receipts, including inferred targets absent from package manifests, and
1295
+ name their actual cached rebuild. It constructs no Nx graph, shadow output registry or second interpolation policy.
1296
+ The record is inside the target's outputs, so a cache hit restores it with them; a live developer link
1297
+ (`@smoothbricks/cli`, "Declared Links") checks it to tell a current build from a stale one by content. The shell entry
1298
+ that bootstraps the plugin (`tooling/direnv/enter-shell.ts`) keeps its build marker under `node_modules/.cache`, not
1299
+ under `outDir`, where the executor would remove it as a file its emit did not write.
1285
1300
  - `scriptc-<arch>-<family>` (`scriptc-arm64-macos`, `scriptc-x64-macos`, `scriptc-arm64-linux`, `scriptc-x64-linux`) are
1286
1301
  inferred for a package that lists `scriptc` in `devDependencies` (that pin is the compiler the targets run; the
1287
1302
  workspace root lists `scriptc` in `trustedDependencies` so its install links the platform compiler) together with each
@@ -1334,13 +1349,25 @@ Concrete targets come from concrete files:
1334
1349
  `ttsc -p tsconfig.lib.json --noEmit` instead. A dialect is a construct the stock checker refuses and the package's
1335
1350
  ttsc plugin lowers before emit; its refusal is withdrawn through the driver's `DiagnosticPlugin` seam (the managed
1336
1351
  ttsc patch: `LoweredDiagnostics` names the checker diagnostics whose cause the plugin's `ProgramPlugin` removes, and
1337
- every lane that gates on the program's diagnostics drops exactly those). The pinned compiler cannot judge such a
1338
- project. The declaring package says so in its manifest,
1352
+ every lane that gates on the program's diagnostics drops exactly those). When a transform host fails, stock ttsc
1353
+ checks the project again with the stock compiler, which loads no plugin and reads each referenced project's
1354
+ declaration outputs where the host read its sources, and appends whatever the host had not printed. The managed patch
1355
+ limits that pass in two ways. A host that printed an error diagnostic of its own has reported its program, so ttsc
1356
+ skips the pass (`PluginFailureDiagnostics.transformHostReported`): no withdrawn refusal and no error of a reference
1357
+ that is not built yet comes back after the real error. A host that printed none (a panic, or a hook or write error
1358
+ after a program that came out clean once its refusals were withdrawn) still gets the pass, and there the host's record
1359
+ of what it withdrew, in the file `TTSC_WITHDRAWN_DIAGNOSTICS_PATH` names, keeps the refusal out of it. The pinned
1360
+ compiler cannot judge such a project. The declaring package says so in its manifest,
1339
1361
  `"smoo": { "typecheck": { "compiler": "ttsc", "dependsOn": ["<project>:<target>"] } }`, where `dependsOn` names the
1340
1362
  targets that prepare the plugin binaries ttsc loads. The routed typecheck depends on them, so it loads built plugins
1341
1363
  and never compiles one, and the inference guesses no workspace target. A declaration of another shape refuses the
1342
1364
  inference by its manifest path. Its compiler is the installed ttsc, which `bun.lock` and the patches in the check
1343
1365
  inputs already key. A project that depends only on typia stays on the pinned compiler.
1366
+ - A project whose inferred `typecheck` runs the native compiler defines the named input `typecheckCompiler` as
1367
+ `[{ "env": "SMOO_TYPECHECK_TSC" }]`; a ttsc-routed project, and one whose declared `typecheck` runs another command
1368
+ (another executor, a top-level `command`, or `options.command`/`options.commands`), defines none. A workspace whose
1369
+ `targetDefaults.typecheck` replaces the inferred inputs names it to key the compiler the command runs, and defines the
1370
+ fallback in `nx.json` empty, for the projects that define none: `{ "namedInputs": { "typecheckCompiler": [] } }`.
1344
1371
  - A direct dependency whose ttsc plugin lowers by environment variables declares them in its manifest,
1345
1372
  `"smoo": { "compileEnv": ["NODE_ENV"] }` (`@smoothbricks/lmao-ttsc` does: it compiles trace statements away unless
1346
1373
  `NODE_ENV` is `test`). The transformed JavaScript is then a function of those variables, so `tsc-js` and every scriptc
@@ -1505,8 +1532,7 @@ Concrete targets come from concrete files:
1505
1532
  executor with `bin` set; a static CLI targets `<arch>-unknown-linux-musl`. The executor runs `cargo-zigbuild`
1506
1533
  directly, removes any compiler or linker the shell names for its triple (a Linux shell pins its host compiler for
1507
1534
  `x86_64-unknown-linux-gnu`), and reads the artifact path from cargo's JSON messages. zig and cargo-zigbuild come from
1508
- the managed devenv module, in every shell; the Linux rust-std set beyond `x86_64-unknown-linux-gnu` comes with a Linux
1509
- shell, and on macOS only inside the `linux-cross` profile (`tooling/devenv -P linux-cross shell -- …`).
1535
+ the managed devenv module, and so does the whole Linux rust-std set, in every shell on every host.
1510
1536
  - `build` is inferred only when the project has at least one concrete build target to run, such as inferred `tsc-js`, a
1511
1537
  package-local target like `tsdown-js`, or `cargo-wasm` from this plugin. It depends on output-family wildcard targets:
1512
1538
  `*-js`, `*-web`, `*-html`, `*-css`, `*-ios`, `*-android`, `*-native`, `*-napi`, `*-bun`, and `*-wasm`.
@@ -1532,31 +1558,34 @@ A wildcard without a caret selects the current project instead. For example, a w
1532
1558
  this local relationship explicit for inferred `tsc-js` targets that also have inferred `cargo-wasm`. Package-managed
1533
1559
  JavaScript targets with another platform prerequisite must likewise declare that local edge themselves.
1534
1560
 
1535
- A self-hosted workspace that owns the plugin's cowshed dependency builds its declared `napi-native` and independent
1536
- `lineage-js` producers before **every bounded-exec task that runs as an mbx Cargo leaf**: a command whose runner Cargo
1537
- builds (`cargo test`, `cargo nextest run` without `--binaries-metadata` or `--archive-file`, `cargo mutants`), as the
1538
- executor classifies it (`runsAsCargoLeaf`, from the command line `boundedCommand` composes, in the declaration's or the
1539
- inference's options or any configuration's). Only such a leaf's admission wait is read from mbx's activity report and
1540
- its waiters' native lineage, the one load of cowshed's `process-lineage` entry and its addon (specs/cowshed/11_shell.md,
1541
- "Cargo test-runner boundaries"); a Bun suite, a script or a nextest run of prebuilt binaries is reserved instead and
1542
- never loads them, so it takes no edge. What the observer reads decides only whether that wait is credited against the
1543
- idle bound (Bounded exec key, below), so no bounded target keys the addon or lineage bytes for it: a command that itself
1544
- reads a producer's output depends on that producer and keys its output, as cowshed's Cargo runners do for the `dist/ts`
1545
- entry and host addon their Node embedder loads (`nx.json` `targetDefaults`). Native tool discovery resolves the local
1546
- owner from the linked package manifest, not a repository path or project-name alias; an installed consumer takes no
1547
- local producer edge because its package ships the addon and lineage entry. The plugin's compile and typecheck targets
1548
- require only `lineage-js`, never the addon or cowshed's full API build. Its runtime-only cowshed project dependency is
1549
- excluded from ordinary caret build edges, avoiding the executor bootstrap cycle. Declarations that replace `dependsOn`
1550
- keep the inferred preconditions with Nx’s `"..."` token. When a declaration changes an inferred executor to
1551
- bounded-exec, its compatible inferred base contains only these runtime prerequisites; the incompatible executor’s
1552
- command and inputs do not leak across the normal Nx override. The canonical dependency-free `release-check` is the
1553
- exception: it judges already assembled shipping artifacts and verifies the addon is present, without compiling at
1554
- runtime or disabling the observer (specs/cowshed/06_cli.md, `release-check`).
1561
+ A self-hosted workspace that owns the plugin's cowshed dependency builds its `napi-native` and independent `lineage-js`
1562
+ producers before every Darwin `bounded-exec` task with an idle bound, to supply Node's awake clock
1563
+ (specs/cowshed/08_testing.md, "Integration tests (real substrate)"). On both Darwin and Linux it also builds them before
1564
+ a bounded task that runs as an mbx Cargo leaf: `cargo test`, `cargo nextest run` without `--binaries-metadata` or
1565
+ `--archive-file`, or `cargo mutants`, as the executor classifies the command in the declaration, inference, or any
1566
+ configuration. Only those leaves read mbx's activity report and its waiters' native lineage (specs/cowshed/11_shell.md,
1567
+ "Cargo test-runner boundaries"). Neither reading changes a passing run, so no bounded target keys these bytes for those
1568
+ reads (Bounded exec key, below); a command that itself reads a producer's output depends on that producer and keys its
1569
+ output, as cowshed's Cargo runners do for the `dist/ts` entry and host addon their Node embedder loads (`nx.json`
1570
+ `targetDefaults`). Native tool discovery resolves the local owner from the linked package manifest, not a repository
1571
+ path or project-name alias; an installed consumer takes no local producer edge because its package ships the addon and
1572
+ both runtime entries. The plugin's compile and typecheck targets require only `lineage-js`, never the addon or cowshed's
1573
+ full API build. Its runtime-only cowshed project dependency is excluded from ordinary caret build edges, avoiding the
1574
+ executor bootstrap cycle. Declarations that replace `dependsOn` keep the inferred preconditions with Nx’s `"..."` token.
1575
+ When a declaration changes an inferred executor to bounded-exec, its compatible inferred base contains only these
1576
+ runtime prerequisites; the incompatible executor’s command and inputs do not leak across the normal Nx override. The
1577
+ canonical dependency-free `release-check` is the exception: it judges already assembled shipping artifacts and verifies
1578
+ the addon is present, without compiling at runtime or disabling the observer (specs/cowshed/06_cli.md, `release-check`).
1555
1579
 
1556
1580
  A target of a napi package whose run sets `NAPI_DEBUG_ADDON=1`, in its declaration or inference, loads the package's
1557
1581
  dev-profile addon from `napi-debug`'s `.cache/native-debug`: it depends on `napi-debug` and keys
1558
1582
  `{dependentTasksOutputFiles: "**/*.node", transitive: false}`.
1559
1583
 
1584
+ <a id="smoo/nx-plugin!n/debug-addon-staging"></a>When the package declares this host's platform addon, `napi-debug`
1585
+ copies that producer's development `.node` to `.cache/native-debug` as a separate file. It keys only on the selected
1586
+ producer's addon bytes, never on its receipt, declarations or Cargo sources, and never depends on a release build.
1587
+ Without a declared host platform addon, `napi-debug` builds its own addon as before.
1588
+
1560
1589
  <a id="smoo/nx-plugin!n/executor-build-edge"></a>A self-hosted workspace that owns this plugin's package also orders
1561
1590
  **every target that runs one of the plugin's executors**, in every project but the plugin, after the plugin's own
1562
1591
  `build`. An executor is a file that build writes (`dist/executors/<name>/executor.js`), so a task that starts before it
@@ -2120,24 +2149,28 @@ line or dot, or a Vitest default-reporter file/test result. Timed Vitest `✓` a
2120
2149
  duration for skipped files. Reporter headers, failure stack locations and final summary counts do not count. Output that
2121
2150
  finishes no test is not progress: the nextest `SLOW` warning, repeated every slow-timeout period for a test still
2122
2151
  running, and a hung test heartbeat both keep printing. A suite that keeps finishing tests therefore runs as long as it
2123
- needs, however slow the host, and a test that never returns ends the run 180 s after the last test that finished.
2124
-
2125
- A running test may also report its own progress. Each run with an idle bound is served a progress channel, a Unix socket
2126
- in a fresh 0700 directory named in the command's environment as `BOUNDED_EXEC_PROGRESS_SOCKET` (`progress-channel.ts`).
2127
- Each line a client writes there is one record and must be `moved`; the record restarts the bound exactly as a finished
2128
- test does, and anything else fails the run as a broken reporter. The executor ends its side of a connection when the
2129
- client ends its own, after reading every record on it, so a client that waits for that end knows its records counted. An
2130
- agent harness that enforces its own no-progress bound over what its run does reports each movement that check sees, so a
2131
- long test that keeps moving is not ended for being the last one running. The run's CPU is never a record: a compile
2132
- inside a test reports nothing and still ends at the bound, where the snapshot names it. bun prints nothing per passing
2133
- test when it believes an agent runs it, so the executor asks a lone `bun test` for `--dots`, one dot per finished test.
2134
- Without a recognised execution lifecycle, the clock starts at command spawn; a command that reports no tests makes
2135
- progress only by exiting. nextest's slow-timeout and the serial groups' code-time classes only warn; no per-test bound
2136
- kills a test or fails one that passed. Bun has a per-test deadline of its own, 5000 ms unless the command sets one, and
2137
- it reads no bunfig for it, so every bun leg deletes it with `bun test --timeout=0` (`BUN_TEST_TIMEOUT_FLAG`; `0` means
2138
- no deadline, measured on the pinned Bun 1.4.2). A test waits for the event it is waiting for, however long a loaded host
2139
- makes the work take; one that never returns still ends the run through `idleTimeoutMs`. `timeoutMs`, an absolute
2140
- ceiling, is for commands that report no tests; a target names at least one of the two.
2152
+ needs, however slow the host, and a test that never returns ends the run after 180 s of awake idle time following the
2153
+ last test that finished.
2154
+
2155
+ On macOS and Linux the idle clock excludes host suspension, including for its final ten-second diagnostic window. An
2156
+ early timer notification is not an expiry: the executor arms the remaining awake budget. Wall timestamps and the
2157
+ explicit fixture and total ceilings still use wall time. A running test may also report its own progress. Each run with
2158
+ an idle bound is served a progress channel, a Unix socket in a fresh 0700 directory named in the command's environment
2159
+ as `BOUNDED_EXEC_PROGRESS_SOCKET` (`progress-channel.ts`). Each line a client writes there is one record and must be
2160
+ `moved`; the record restarts the bound exactly as a finished test does, and anything else fails the run as a broken
2161
+ reporter. The executor ends its side of a connection when the client ends its own, after reading every record on it, so
2162
+ a client that waits for that end knows its records counted. An agent harness that enforces its own no-progress bound
2163
+ over what its run does reports each movement that check sees, so a long test that keeps moving is not ended for being
2164
+ the last one running. The run's CPU is never a record: a compile inside a test reports nothing and still ends at the
2165
+ bound, where the snapshot names it. bun prints nothing per passing test when it believes an agent runs it, so the
2166
+ executor asks a lone `bun test` for `--dots`, one dot per finished test. Without a recognised execution lifecycle, the
2167
+ clock starts at command spawn; a command that reports no tests makes progress only by exiting. nextest's slow-timeout
2168
+ and the serial groups' code-time classes only warn; no per-test bound kills a test or fails one that passed. Bun has a
2169
+ per-test deadline of its own, 5000 ms unless the command sets one, and it reads no bunfig for it, so every bun leg
2170
+ deletes it with `bun test --timeout=0` (`BUN_TEST_TIMEOUT_FLAG`; `0` means no deadline, measured on the pinned Bun
2171
+ 1.4.2). A test waits for the event it is waiting for, however long a loaded host makes the work take; one that never
2172
+ returns still ends the run through `idleTimeoutMs`. `timeoutMs`, an absolute ceiling, is for commands that report no
2173
+ tests; a target names at least one of the two.
2141
2174
 
2142
2175
  With mbx admission, a supported Cargo/nextest test leaf inherits a private grant pipe: mbx writes `g` on every admission
2143
2176
  and `r` on permit drop (`MBX_GRANT_FD=5`). The executor counts overlapping holds: while no hold exists it pauses the
@@ -2150,9 +2183,10 @@ own (specs/cowshed/05_gateway.md, "An Nx run serves its leaves one reservation e
2150
2183
  `preTasksExecution` starts `mbx reservations <socket>` once for a run with mbx's pool and publishes the socket in
2151
2184
  `MBX_RESERVATIONS_SOCKET`; its `postTasksExecution` ends it. The leaf's shell writes the count it asks for on descriptor
2152
2185
  5 and reads back the cores granted. The executor asks the endpoint over its process's one connection, says
2153
- `cowshed: mbx reserve wait start cpus=<asked> priority=<p>` and then
2154
- `cowshed: mbx reserve granted elapsed=<ms> priority=<p>`, and gives the grant back once the leaf's subtree is retired;
2155
- the grant starts the leaf's total and fixture ceilings as a first `g` does. The shell runs the command with
2186
+ `cowshed: mbx reserve wait start cpus=<asked> priority=<p>` (with ` min=<m>` after the count when the leaf names a
2187
+ minimum: the fewest threads at which the walls its last run recorded keep a test finishing within its `idleTimeoutMs`)
2188
+ and then `cowshed: mbx reserve granted elapsed=<ms> priority=<p>`, and gives the grant back once the leaf's subtree is
2189
+ retired; the grant starts the leaf's total and fixture ceilings as a first `g` does. The shell runs the command with
2156
2190
  `MBX_RESERVE_CPUS`, `MBX_SCHED_DISABLE=1` and an empty `MBX_SCHED_DIR`. A refusal fails the leaf, naming mbx's error,
2157
2191
  and a run with no endpoint refuses its reserved leaves.
2158
2192
 
@@ -2230,24 +2264,24 @@ so a package pattern that matched no tests cannot pass. It exits 1 when any bina
2230
2264
  be run.
2231
2265
 
2232
2266
  A target may name a `fixtureCommand` with its `fixtureTimeoutMs`: a compiler-fixture producer the executor runs first,
2233
- in the same cwd, environment and CPU grant (under mbx inside the leaf's reservation, or before it when its units are
2234
- counted, below; a build's compilers are admitted one by one), as segment 0 of the same lifecycle — a build interval for
2235
- its whole life, under its own supervisor and acknowledged like a runner's phases. The command follows under `&&` (a
2236
- direct Go/Cargo chain keeps its phases behind a brace group; any other command runs as one segment active from its
2237
- spawn), so a fixture failure ends the run before a test starts, and fixture output earns no progress. `fixtureTimeoutMs`
2238
- is the segment's own wall-clock ceiling, a build budget; the segment's terminal retires it, and expiring it records a
2239
- `fixture` bound, since no test was running. The pair is refused unpaired, and a run that names it names no shadow record
2240
- of warmth. This exists for warmth that lives outside Nx outputs — a compiler plugin cache, a Cargo `target/`: it cannot
2241
- be a cacheable output, and as a `cache: false` prerequisite it executed even when every consumer then restored its
2242
- verdict from cache, because Nx runs an uncached dependency before reaching its cached consumer. Inside the consumer's
2243
- own task the cache decides: a hit restores the verdict and warms nothing; an execution warms first. Without the
2244
- lifecycle channel (Windows) the fixture is plain shell text ahead of the command, bounded from spawn like any wrapper,
2245
- and its ceiling does not apply.
2267
+ in the same cwd, environment and CPU grant (under mbx's pool before the leaf's reservation, never inside it: a build's
2268
+ compilers are admitted one by one, and a build waiting on Cargo's build-directory lock holds no core), as segment 0 of
2269
+ the same lifecycle — a build interval for its whole life, under its own supervisor and acknowledged like a runner's
2270
+ phases. The command follows under `&&` (a direct Go/Cargo chain keeps its phases behind a brace group; any other command
2271
+ runs as one segment active from its spawn), so a fixture failure ends the run before a test starts, and fixture output
2272
+ earns no progress. `fixtureTimeoutMs` is the segment's own wall-clock ceiling, a build budget; the segment's terminal
2273
+ retires it, and expiring it records a `fixture` bound, since no test was running. The pair is refused unpaired, and a
2274
+ run that names it names no shadow record of warmth. This exists for warmth that lives outside Nx outputs — a compiler
2275
+ plugin cache, a Cargo `target/`: it cannot be a cacheable output, and as a `cache: false` prerequisite it executed even
2276
+ when every consumer then restored its verdict from cache, because Nx runs an uncached dependency before reaching its
2277
+ cached consumer. Inside the consumer's own task the cache decides: a hit restores the verdict and warms nothing; an
2278
+ execution warms first. Without the lifecycle channel (Windows) the fixture is plain shell text ahead of the command,
2279
+ bounded from spawn like any wrapper, and its ceiling does not apply.
2246
2280
 
2247
2281
  Under mbx, a reserved leaf whose target names a `unitsCommand` (a shell command printing one line per unit `command`
2248
2282
  runs; the plugin's nextest pieces name the same `nextest list -T oneline` of their selection and partition) runs that
2249
- command at the end of its fixture segment, under the fixture's ceiling, which then starts at spawn, with the fixture's
2250
- own output on stderr; the fixture runs before the reservation, not inside it. The leaf then asks its run's endpoint for
2283
+ command at the end of its fixture segment, under the fixture's ceiling, which under mbx starts at spawn for every
2284
+ reserved leaf, with the fixture's own output on stderr. The leaf then asks its run's endpoint for
2251
2285
  `min(units, its runner's count)` cores, at least one, and its reservation says
2252
2286
  `cowshed: mbx reserve running cpus=<granted> asked=<asked>`. A count that fails fails the run before anything is
2253
2287
  reserved, named as the fixture segment. `unitsCommand` is refused without `fixtureCommand`.
@@ -2684,21 +2718,32 @@ task id and the hash it ran at:
2684
2718
  exceed it too. Its `tests` name those the runner reported running (nextest's `SLOW`, libtest's
2685
2719
  `has been running for over`) and never finished, and those the JUnit report says it aborted when the bound stopped it.
2686
2720
  Its `lockWaits` lists only regular files the run holds on numbered descriptors that processes outside the run also
2687
- hold open, naming those holders' pids and commands. This is open-handle evidence, not kernel lock-owner proof. The
2688
- open-file census runs only on macOS, so on every other platform `lockWaits` is always empty. An incomplete or raced
2689
- capture records none. Its `cpuRising` lists each process of the run's tree whose CPU time rose between the snapshot's
2690
- two process censuses by at least the larger of 0.5 s and twice the coarser resolution of its two readings (2 s at
2691
- whole seconds, 0.5 s at centiseconds), with its pid, command and gain: a build inside the test, which is a defect and
2692
- not a hang. It is empty when no process rose or the closing census did not complete, and a record written before it
2693
- carries none.
2721
+ hold open, naming those holders' pids and commands. This is open-handle evidence, not kernel lock-owner proof; the
2722
+ snapshot also stack-samples each named waiter its leaf samples left out, so its text shows the call that waiter blocks
2723
+ in. The open-file census runs only on macOS, so on every other platform `lockWaits` is always empty. An incomplete or
2724
+ raced capture records none. Its `cpuRising` lists each process of the run's tree whose CPU time rose between the
2725
+ snapshot's two process censuses by at least the larger of 0.5 s and twice the coarser resolution of its two readings
2726
+ (2 s at whole seconds, 0.5 s at centiseconds), with its pid, command and gain: a build inside the test, which is a
2727
+ defect and not a hang. It is empty when no process rose or the closing census did not complete, and a record written
2728
+ before it carries none.
2694
2729
  - `no-space`: the command failed after its output said a write found no space (`ENOSPC` or `No space left on device`).
2695
2730
  Its tests failed on the disk, not on their own, whatever bound or hang followed: it records that line and, when the
2696
2731
  task held a RAM lease, the lease, the volume and its free bytes when the line arrived, or why none were read: the
2697
2732
  lease was no longer on its volume (`lost`) or the volume could not be read (`unread`). A passing run that printed such
2698
2733
  a line passed.
2734
+ - `operational`: bounded-exec itself ended or refused the run, whatever its command did, and `cause` says why. A
2735
+ `reservation-refused` cause names the run's mbx reservation endpoint the leaf asked, the connect error's code
2736
+ (`ENOENT` when the endpoint's socket is gone) and mbx's message; an `executor` cause names the executor's own failure
2737
+ (a refused or lost CPU pool, a broken progress channel or runner lifecycle, leftovers it could not retire, a refusal
2738
+ before the command started). The output's last line then says `Command was ended by bounded-exec because <cause>`,
2739
+ never a signal as if it came from outside. Its `tests` are the report's failures, never bounds.
2699
2740
  - `failed`: a test failed on its own, or the command exited non-zero with no report naming a timeout.
2700
2741
  - `passed`.
2701
2742
 
2743
+ A consumer reads a task's record through `@smoothbricks/nx-plugin/bounded-exec-verdict` (`readRecord` over
2744
+ `taskDirectory(<workspace data>, <task id>)`, the `BoundedExecRecord` and `BoundedExecVerdict` types), never by parsing
2745
+ the command's output: an Nx worker that judges a test task from it tells an `operational` refusal from a red.
2746
+
2702
2747
  The record also holds `peakBytes`, the command's memory peak: the exited command's rusage `ru_maxrss`, the largest
2703
2748
  resident set any one process of its tree reached, in bytes. Node reaps a child without its rusage, so the command runs
2704
2749
  under a Bun waiter (`peak-waiter.ts`, on the executor's Bun or the first `bun` on its PATH) that reads it, passes the
@@ -2809,8 +2854,17 @@ output, reads the referenced UTF-8 cause before releasing the held test, then ch
2809
2854
  JUnit and verdict. `nx-plugin:cargo-stream-archive` produces the smoke's nextest archive before any Bun shard starts;
2810
2855
  the smoke executes that archive and never compiles inside the test progress interval. The reporter smoke likewise
2811
2856
  executes the transformed `dist/bin/smoo-nx-bound-failures.js` supplied by the shards' `build` dependency, not raw
2812
- TypeScript whose imports may require schema generation. Test ownership and readiness follow
2813
- [`specs/cowshed/08_testing.md`](../../specs/cowshed/08_testing.md), “Unit tests” and “Fixtures”.
2857
+ TypeScript whose imports may require schema generation. `nx-plugin:ttsc-plugin-hosts` builds, through `ttsc prepare`,
2858
+ every ttsc plugin host the Bun shards load: this package's own (`tsconfig.test.json` and `tsconfig.lib.json`, which the
2859
+ Bun preload transforms the suite through) and those of the TypeScript emit executor's fixtures (`PLUGIN_HOST_FIXTURES`
2860
+ in `src/__tests__/typescript-emit-fixtures.ts`: typia alone, `@smoothbricks/lmao-ttsc` on the utility host, and the
2861
+ side-output and dialect fixture plugins on the utility and typia hosts). It builds them into its own `TTSC_CACHE_DIR`,
2862
+ `.cache/ttsc-plugin-hosts`, whose host binaries (`plugins/*/plugin`) are its Nx output. The shards depend on it and name
2863
+ the same directory, which the `src/__tests__/ttsc-cache-dir.ts` preload resolves against the package before any ttsc the
2864
+ suite runs in a fixture reads it, so those tests load built hosts and never compile one inside the progress interval.
2865
+ The checkout's shared `.cache/ttsc-plugins` cannot be that output: it is cowshed build state, which no Nx output may
2866
+ cover (`src/build-state-output-policy.ts`), and every plugin build of the checkout writes into it. Test ownership and
2867
+ readiness follow [`specs/cowshed/08_testing.md`](../../specs/cowshed/08_testing.md), “Unit tests” and “Fixtures”.
2814
2868
  `smoo-nx-bound-failures` reads the workspace's last Nx run (`run.json` in Nx's `cacheDir`, the directory
2815
2869
  `StoreRunInformationLifeCycle` writes: the checkout's own `.nx/cache` under smoo's workspace policy) against those
2816
2870
  records and prints one line per failed task. It exits 0 only when the run failed and every failed task's record, for
@@ -2876,6 +2930,12 @@ to the command, which the keyed modules decide. Each entry, and what the executo
2876
2930
  - `parent-grant.js`: what a run asks its parent's pool for and says of the answer, `peak-charge.js` and `cpu-grant.js`:
2877
2931
  the charge the task's last record names and the grant a record states. A grant reaches the command as a token count
2878
2932
  and nothing else, through `runner-sizing.js`; a record that cannot be read refuses the run.
2933
+ - `case-gate.js`: the gate a reserved nextest leaf's cases each take a core at, one of its grant or one reserved for the
2934
+ case. It decides when a case starts and on which core; the leaf's thread count still reaches the command through
2935
+ `runner-sizing.js`.
2936
+ - `suite-minimum.js`: the minimum a reserved test leaf names on its reservation, from the walls its last run recorded.
2937
+ It decides how many cores the leaf waits for before it starts; the grant still reaches the command as a token count
2938
+ through `runner-sizing.js`, and a leaf with no recorded wall names none.
2879
2939
  - `memory-retry.js`: whether a command the kernel killed for memory (a SIGKILL this executor did not send, to a command
2880
2940
  no bound of it ended) runs once more, alone in its run's pool, and how the two runs' output joins. The second run is
2881
2941
  the same command; only the pool it is lent from differs, and a pass after it is a pass of that command.
@@ -2895,8 +2955,9 @@ decides what a token count does to the command's parallelism flags and test-thre
2895
2955
  writes the pool endpoint, its count and the jobserver flags into `MAKEFLAGS` and `CARGO_MAKEFLAGS` (`cpu-pool.js` serves
2896
2956
  the pool and writes none of them), and `withProgressReport` adds `--dots` to `bun test` and `-json` to `go test`. They
2897
2957
  stay keyed until those functions move into modules of their own. A module that comes to decide what a value does to the
2898
- command, its environment or a passing verdict leaves `outputNeutral` in the same commit; `executor-key.test.ts` names
2899
- the keyed modules and refuses a neutral one that writes those variables.
2958
+ command, its environment or a passing verdict leaves `outputNeutral` in the same commit. The
2959
+ [executor-key law](../../specs/cowshed/laws/executor_key.bend) shows when a module is keyed: a neutral boundary stops
2960
+ its path, not a separate path that reaches the same module without crossing it.
2900
2961
 
2901
2962
  ## Test Fixtures That Run Nx
2902
2963
 
@@ -14,16 +14,16 @@
14
14
  "packages/nx-plugin/src/bin/smoo-nx-test-walks.ts": "94e8af452331d765e711aa2493efbff4ddb4e6e3088343873f78d9eaa840570b",
15
15
  "packages/nx-plugin/src/bounded-test-policy.ts": "b52a8858543d25e173aad4f49002a7cdc7f70b098f6046fc56acb747065acd8a",
16
16
  "packages/nx-plugin/src/build-state-output-policy.ts": "031a75cb96a2fed0ab2ce80a98588482595f7550d5259e33edabd6e676ad3a3c",
17
- "packages/nx-plugin/src/built-output-packages.ts": "e593f08d42298c9881d381bb8afbae858108941387f67927d6cc1f49e504e4e2",
17
+ "packages/nx-plugin/src/built-output-packages.ts": "48670b65204537738b1a65a5b133d959a51aaecefc32dc03366f614cb6fa57ec",
18
18
  "packages/nx-plugin/src/bun-lock-scope.ts": "b7534de8bfb54d9f25773678b63a5fd72fce1795b92fdb65868982e13bda6305",
19
19
  "packages/nx-plugin/src/cargo-build-script-env.ts": "e5b45ccefc2255cd8a48121eb97132a08e136b4cbbc375d04c940d821a429b23",
20
- "packages/nx-plugin/src/cargo-closure-input.ts": "0985e176d9f50df6c65d292754b7ad349f7d6c1cc82680b8dc4a3102f851a992",
20
+ "packages/nx-plugin/src/cargo-closure-input.ts": "fb0dcc6a708d21193a165dc705b5731d498a77b6deb3cdcd5e9335f291f28247",
21
21
  "packages/nx-plugin/src/cargo-dev-profile.ts": "34764ba4fc2aeebe75051c98c2eb64b6baeaa3d8cc0242803081ef935465368d",
22
22
  "packages/nx-plugin/src/cargo-retention-hook.ts": "5699506a32aff25be4adca91fff443bea2bfcd6fd7b2964dfa38296c50043ba1",
23
- "packages/nx-plugin/src/cargo-source-hash.ts": "c44944cfa42927961fe56abc3de1c4db0e9924d52e11fecc48be7b78b89347bb",
24
- "packages/nx-plugin/src/cargo-toolchain-paths.ts": "3c622c19ed7a43166e81f9a92e8ab0e3b607690add5408cd96e95912ecf4c4c1",
23
+ "packages/nx-plugin/src/cargo-source-hash.ts": "7f122602ea89ad7e3bbfd0b33f663b586f511816e444e60c254f1b13512a9180",
24
+ "packages/nx-plugin/src/cargo-toolchain-paths.ts": "fa67bac0d7d8f63b8b1630310d231ff67d951a09d0df811800d0b6632a9547c6",
25
25
  "packages/nx-plugin/src/cargo-toolchain-policy.ts": "9c7bae572b57046dcc1e3d577b4abb25e877cf551efcca1b837c4bb5a8c62203",
26
- "packages/nx-plugin/src/cargo-workspace.ts": "10399b2a285cfa1ec61c3c33cf22e4747506a7d6a8adfe75fc9b45676493ae25",
26
+ "packages/nx-plugin/src/cargo-workspace.ts": "9990b34c194512a71c28e3a7a37794e2718d625efedc69bb32f6599f36fef20d",
27
27
  "packages/nx-plugin/src/compile-environment.ts": "8085b28e695f60306eefb91f3eca3e1bb908d7ea1676d028c7c85a6adda1a95c",
28
28
  "packages/nx-plugin/src/cross-check-policy.ts": "3a22f798805dca09f6452d929d86c0d76621bdd32d5d1f21fe02c75cf7335e2f",
29
29
  "packages/nx-plugin/src/dependency-manifests.ts": "2acc8497dbf07e432a1a093c7c2fd8765bc4c3e089be7b332ea7d239e280d0b0",
@@ -37,51 +37,57 @@
37
37
  "packages/nx-plugin/src/eslint-sources.ts": "976a2b8e0520b5f6aaf397a272791817a4f385507bc0cbaad4b114fefa8decf5",
38
38
  "packages/nx-plugin/src/executors/all-verdicts/executor.ts": "4d3aac65aa2e03a2d24d149c412aa18f2e66a6a36a4e88993122b10e9355c8f0",
39
39
  "packages/nx-plugin/src/executors/all-verdicts/schema.ts": "2ca6bd8d2f19d851f291ab6a5227167399b9dc8ed0fda0248b69896d77e471f1",
40
- "packages/nx-plugin/src/executors/bounded-exec/admission-queue.ts": "86664180f8296032f7c96022a790285799e666d92360a10b7a5cc6f3facd58eb",
41
- "packages/nx-plugin/src/executors/bounded-exec/bounds.ts": "bd59a97f88851619f64af7adb9f787afee90174c780964200c714eaa81363259",
40
+ "packages/nx-plugin/src/executors/bounded-exec/admission-queue.ts": "f54620dff7d0591885da0d0e666cff256ba113922fe4f0dc08d960775b6f9d61",
41
+ "packages/nx-plugin/src/executors/bounded-exec/awake-clock.ts": "56f0720ab1064c5c973d28a4c76fb826385e1aec920f06747bc95c5b1b998412",
42
+ "packages/nx-plugin/src/executors/bounded-exec/bounds.ts": "7beb78afc60efd7d8529823b09125e40888320b397b23492e71c0095aeab8e97",
43
+ "packages/nx-plugin/src/executors/bounded-exec/case-gate.ts": "d9d664f55f2fb52b64352fb91c9a6c4f3428ab5dde1e5b0860b19b4716cb674e",
42
44
  "packages/nx-plugin/src/executors/bounded-exec/child-exit-diagnostics.ts": "fdcd4e074577814d9b7b9d014d2c39297e9c763bd570d9fab0db172349e039b2",
43
45
  "packages/nx-plugin/src/executors/bounded-exec/cpu-grant.ts": "c5217349c23be537d9b6a0a52445f3ee442402fdbd08f1d33a3095c52051616d",
44
- "packages/nx-plugin/src/executors/bounded-exec/cpu-pool-thread.ts": "47697a9531df5fd6fcdf4e706fc7e5874bca1717c838496673bf148c691f1e9e",
45
- "packages/nx-plugin/src/executors/bounded-exec/cpu-pool.ts": "bc122174ccf628b769c73197b7a78987d033b5e7ea6cb5ddbeac384310fdd22a",
46
+ "packages/nx-plugin/src/executors/bounded-exec/cpu-pool-thread.ts": "229b5cdbfb3fc2c7530ce54306e822347cc540c1daf298b60c2b5790a79b181d",
47
+ "packages/nx-plugin/src/executors/bounded-exec/cpu-pool.ts": "73186b3f4251d705b09d71ebf472ee5d2ebcfbc064e92bbbf9872e394b54bc44",
46
48
  "packages/nx-plugin/src/executors/bounded-exec/cpu-rise.ts": "90b345ad3687813d59e150dd14f91c0adf8da1b8963a3f59f56355ce1f651713",
47
49
  "packages/nx-plugin/src/executors/bounded-exec/disk-lease.ts": "1a3f6a6fa590d9a2550490bb6906dc91b6c05fbef235b025eaf257eb5310e92d",
48
- "packages/nx-plugin/src/executors/bounded-exec/executor.ts": "ba7ef3630a49e2ca2b4ce689eb29d6804210833af6927043cce281a7bbef3b1c",
49
- "packages/nx-plugin/src/executors/bounded-exec/gateway-lease.ts": "f3f73bd92db30e4857f98fb8bd2b9a75b2a5a2a318f094e075ed803c1f9a0117",
50
- "packages/nx-plugin/src/executors/bounded-exec/hang-diagnostics.ts": "ddbfd116357e991000c9a5ae4fad4200e3fb3b88212b0d925d06a9b63455f44e",
50
+ "packages/nx-plugin/src/executors/bounded-exec/endpoint-life.ts": "7a32f63324edb5208f92db6a9582e73fe65b8fc440bca998244fdf1163109ccc",
51
+ "packages/nx-plugin/src/executors/bounded-exec/executor.ts": "0ed947f4d4dfa17faddd717194c1b51acf5c97712bede68a8f94afee039c680c",
52
+ "packages/nx-plugin/src/executors/bounded-exec/gateway-lease.ts": "e2b150677aec8482a6916eac38f114ecd60c787a1baed36822d1d99a2d1f1b02",
53
+ "packages/nx-plugin/src/executors/bounded-exec/go-run-summary.ts": "e7be137c647ae0889bbc825feb8c8ca14a5118bfff90ca87a8dda4c34dff8d53",
54
+ "packages/nx-plugin/src/executors/bounded-exec/hang-diagnostics.ts": "c056754715dd88106275e0ef2d620d0751d2a209e1f5c794aea0640426f2ebe2",
51
55
  "packages/nx-plugin/src/executors/bounded-exec/host-memory.darwin.ts": "fe89fc99f85f48caec7c614cfd976c362253b9707797c2c849a3aa9664e65dbe",
52
56
  "packages/nx-plugin/src/executors/bounded-exec/host-memory.linux.ts": "752519893ed6fc3b9d7d17b0b0801d7103129f7a838743d129057debf043f0c1",
53
57
  "packages/nx-plugin/src/executors/bounded-exec/host-memory.ts": "d3eef7fb06bf259f0f7f7dc67fc7f246a39adf5e4e80850fd4565e91626b1ec5",
54
58
  "packages/nx-plugin/src/executors/bounded-exec/leaf-peak.ts": "0b1b94992b2cbb9e3759785424ceb202667053c5571edf3a79cdd0b206e54a1d",
55
- "packages/nx-plugin/src/executors/bounded-exec/lease-wait.ts": "59d8ac94d0b8b75858971c5bb28ee421fca4f7685577274fe8bbaf0c01ba462a",
59
+ "packages/nx-plugin/src/executors/bounded-exec/lease-wait.ts": "e9eeda9a8336e24359c0280ce32a12d3d17846eb02973570d391dce8ff8d7fbd",
56
60
  "packages/nx-plugin/src/executors/bounded-exec/lock-wait.ts": "b14a23b49759a777f4b3338ced003adaf76837c2c38462458f76a7fef1b95d9e",
57
- "packages/nx-plugin/src/executors/bounded-exec/mbx-pool.ts": "4181c50a212e649e70b38ff25077aecbdddab0b92c0eb91cc14d873ef0dca4e6",
61
+ "packages/nx-plugin/src/executors/bounded-exec/mbx-pool.ts": "2437ef83cd37a4fb307d0435cb60c489b29197ccac96625d5f7e742615683472",
58
62
  "packages/nx-plugin/src/executors/bounded-exec/mbx-queue.ts": "ac309e28e5ee78fa08d628edb00e33532514f7572166770799ae86d468c12b4e",
59
- "packages/nx-plugin/src/executors/bounded-exec/mbx-reservations.ts": "d5650230f8f240ec6709a351503eeb6c5f8e576bbd75873eb5209cad918ea867",
63
+ "packages/nx-plugin/src/executors/bounded-exec/mbx-reservations.ts": "616a03e5b7c2ca8636623e76eebf3f65439c927689a5db55c14eee2c6d084bfe",
60
64
  "packages/nx-plugin/src/executors/bounded-exec/memory-retry.ts": "e56fd04f8a8ad03247099a1d005fcbcda6def6aa7656e9515309f6f2438fe88d",
61
65
  "packages/nx-plugin/src/executors/bounded-exec/no-space.ts": "ec032968d89f9e853796012705a06c06cfc4da54bf6e6f10a526f98daca3d077",
62
66
  "packages/nx-plugin/src/executors/bounded-exec/owned-subtree.ts": "cb5edf2b5fe2c1b5b961f8c0ff16ec7bfae3c22ad75dfd671b74f1a4a865863f",
63
- "packages/nx-plugin/src/executors/bounded-exec/parent-grant.ts": "9e3826a336220c2453725a07516dfb9a89c84f5febe2b0620ea4be91ae437b3b",
67
+ "packages/nx-plugin/src/executors/bounded-exec/parent-grant.ts": "c634d3c57aa7859b5ee6cfd78f59889285faf72fb66ec2261d7481103c0a41fc",
64
68
  "packages/nx-plugin/src/executors/bounded-exec/peak-charge.ts": "6721d2d4968550d99a6d10b47483d5e1685cea0ad694ea71abeef3d1adc48d77",
65
69
  "packages/nx-plugin/src/executors/bounded-exec/peak-waiter.ts": "3d9a60f8e61d160cf4151746c160f836954f57aca896127a5ef9df4d09c26180",
66
- "packages/nx-plugin/src/executors/bounded-exec/pool-admission.ts": "0cc84dbda8d2cf472a0ee9ec14ab136a219ab2ed223e9769ef45590efbb4b793",
70
+ "packages/nx-plugin/src/executors/bounded-exec/pool-admission.ts": "f83e113493937a356209f75893bd50c46a9ba6eeb53567bc19e972cfd4e918bd",
67
71
  "packages/nx-plugin/src/executors/bounded-exec/pool-environment.ts": "00046e682376dfabedba3f1743b04656bd6a031b0ac4e594ae47e8f7beb2b68a",
68
72
  "packages/nx-plugin/src/executors/bounded-exec/progress-channel.ts": "68f51041c095ea334cbe9137cf99884d9a758484491cc4dc3506bfe37c3d327a",
69
- "packages/nx-plugin/src/executors/bounded-exec/progress.ts": "777c41cafb9ae87db49f588b0378b3bba459080e53c85d8747cae4f2e3cef078",
73
+ "packages/nx-plugin/src/executors/bounded-exec/progress.ts": "23615918ba678ff464a1a076e705c4c32f0c9663072a55870dff6c312e5ebdad",
70
74
  "packages/nx-plugin/src/executors/bounded-exec/ram-attach.ts": "865eb5c277d9ab4b258013030938aeee762b731a7298fa8ad3c5eba3026df77a",
71
75
  "packages/nx-plugin/src/executors/bounded-exec/ram-detach.ts": "535d26114d14d0d94db76227ea7ba52b1ae0b590d7dbac22993b6796d255e666",
72
76
  "packages/nx-plugin/src/executors/bounded-exec/ram-temp-fixtures.ts": "075da4ecfd1cf7dd98fc8c894599dcf2720faba07ac30b8e5592964178849359",
73
77
  "packages/nx-plugin/src/executors/bounded-exec/ram-temp-held.ts": "7c32555bc6dab3f767925b55b68684d33a69393050342d06f055fb81e8e5332b",
74
78
  "packages/nx-plugin/src/executors/bounded-exec/ram-temp.ts": "04d337d46ea375f1947016a21564284e3fa7bbc982b5b4842744fa943d5327fe",
75
- "packages/nx-plugin/src/executors/bounded-exec/run-cpu-pool.ts": "17148ca7a51aff54d9cbb01db558a828804b158f46e4d3d85d39449d2b644861",
79
+ "packages/nx-plugin/src/executors/bounded-exec/reservation-connection.ts": "49a5357b477e01f8d571590c1e9e239f2d9b346b3397692e963dddf86a3cd869",
80
+ "packages/nx-plugin/src/executors/bounded-exec/run-cpu-pool.ts": "9ad71786b869bc7325a562f61a412062ae28a5bfbdf4d54e8ca3a2664bcb1de9",
76
81
  "packages/nx-plugin/src/executors/bounded-exec/runner-hook.ts": "606eab5db826e571eb15df618315e01cc773d09fd647beb1c00f6434df58ffad",
77
82
  "packages/nx-plugin/src/executors/bounded-exec/runner-lifecycle.ts": "b2a7c901296bb6c139909297bbdbab5bd00e94319c022307d006b0e1293f6454",
78
- "packages/nx-plugin/src/executors/bounded-exec/runner-sizing.ts": "bffd2ba0f80758944ca682838832bdbe20ae12eb9a4f75084a3df82ae7786145",
83
+ "packages/nx-plugin/src/executors/bounded-exec/runner-sizing.ts": "cb10681f90d703240b71ac134be7407d40b3656bfa4777df33810371bb605eb5",
79
84
  "packages/nx-plugin/src/executors/bounded-exec/runtime-pin.ts": "3eb9a8b794da51ffa01723509935f48bfb497fba883518046e74a53209f0eb10",
80
- "packages/nx-plugin/src/executors/bounded-exec/schema.ts": "a35b5fbb55a57c01b45d6245421bc1ee330c4adc48ee770e952cb9e9d05bff56",
81
- "packages/nx-plugin/src/executors/bounded-exec/test-result-writer.ts": "df7668a11d105a1f88d2187ef8b0edff9db7ba56d8176b5bc35daf1359667637",
82
- "packages/nx-plugin/src/executors/bounded-exec/test-results.ts": "4f83dc3accd7892f45385796522267adad9401326d0cd9ce4d4e1145b9023577",
83
- "packages/nx-plugin/src/executors/bounded-exec/verdict.ts": "765bc326882102bf9ca1a74f26946d1b153511c9450d92c869190160624ba764",
84
- "packages/nx-plugin/src/executors/cargo-zigbuild/executor.ts": "622a5f36897d9eb1f7465654e88f4291aedee9767603028d20c1e819b91d72f4",
85
+ "packages/nx-plugin/src/executors/bounded-exec/schema.ts": "c96d0aeb175401ae50c73baa45c2c44fefa8b530c29adfda22e281746811b946",
86
+ "packages/nx-plugin/src/executors/bounded-exec/suite-minimum.ts": "9d76c4658b554786b3fec620d08e7dd0c43316f10ae041b7bbe0e60a2d973ce2",
87
+ "packages/nx-plugin/src/executors/bounded-exec/test-result-writer.ts": "713cf3198221a72dd4916d0a429002f6dc60f902050bb70a17d76b05f7011d8f",
88
+ "packages/nx-plugin/src/executors/bounded-exec/test-results.ts": "1cc94eba11bbac1a27a60ce6e086335b91634066a9cf49d8b48c639930cb70ea",
89
+ "packages/nx-plugin/src/executors/bounded-exec/verdict.ts": "238968d9af11050bee431f63cad1f5cd3e3b6fdc32bd16f5add121a787da2449",
90
+ "packages/nx-plugin/src/executors/cargo-zigbuild/executor.ts": "e39872a433d4744ab82b2ee8063f8942991dabcf72a69eaaef1206315c0d13d2",
85
91
  "packages/nx-plugin/src/executors/cargo-zigbuild/schema.ts": "e5cf3b0cc91a2d003a63ca0c9a93f1ec08263469b8a19dbe338b2dc0c0810747",
86
92
  "packages/nx-plugin/src/executors/scriptc-native/executor.ts": "4db61da4444d3a30acd3995b6cf53a4bc403a40fe856d88b2c30ce467badbea8",
87
93
  "packages/nx-plugin/src/executors/scriptc-native/ffi-paths.ts": "a73ed6800f69992cad6b954f14c0adb4f0ded45900bf84582df4755a3775104c",
@@ -106,11 +112,11 @@
106
112
  "packages/nx-plugin/src/generators/make-public/schema.d.ts": "5e7bd2f1ce16795df4c919d6d53588ea85b574c84400940b6322275f96f60357",
107
113
  "packages/nx-plugin/src/go-tests.ts": "8e356b6ee276e6e836c404353b0ffb5ccec5beb261126f167f730e6e01e9c2b6",
108
114
  "packages/nx-plugin/src/graph-input-contract.ts": "8a1aec1294960ae80bcff55a0370c95004a911bf1afe6caa47e666da3baeac43",
109
- "packages/nx-plugin/src/index.ts": "fb859bfeea798d9251a9fdcb89a9a91304f5dee678595bcddfc00bbe8b47085d",
115
+ "packages/nx-plugin/src/index.ts": "0865195373e9a53d9aadddbaa005c712e7bbb83c645f5bb900f56278b0384a66",
110
116
  "packages/nx-plugin/src/managed-assets.ts": "9cea959c09f3163992e666eecc5a65ec1f1b63c81fc56c5e99088507d02c5e3b",
111
- "packages/nx-plugin/src/managed-files/ci-workflow.ts": "c48f80cf3b215a8b41fdeb220e653a3a26ee288e833b1bb215f8f15de006e5ae",
117
+ "packages/nx-plugin/src/managed-files/ci-workflow.ts": "bec80c782d39df9e8e451c81bbf52bd5b35ac56a01d0437d5bb15c95cb74a64c",
112
118
  "packages/nx-plugin/src/managed-files/context.ts": "472553c8e15f5bb72f7167ca3f3c5ce5171f479a3cdf2fb4b9f86d1f1addf4bd",
113
- "packages/nx-plugin/src/managed-files/files.ts": "0e4010a194cc3ae89cc05ba1d3482d607fd3e39dd776edf0eaa8e38804e5d897",
119
+ "packages/nx-plugin/src/managed-files/files.ts": "0bcb76d5749327c25faa7f98ded390d06ff21a94258d4c90dc450dfea0ff75cf",
114
120
  "packages/nx-plugin/src/managed-files/generator.ts": "b3d3bdf6f4c665c649472159595ee094a1b73d729495bbae3695817147487e0c",
115
121
  "packages/nx-plugin/src/managed-files/github-runs-on.ts": "a049ca60a79dec57f77e5d18090569a9b8b78818219f236fe352e7705500f531",
116
122
  "packages/nx-plugin/src/managed-files/json-edit.ts": "81bc6dd10fffff583cc9f2269f0c2fd2f76b1c5aedbc7d068cf29878371497c2",
@@ -154,7 +160,7 @@
154
160
  "packages/nx-plugin/src/typecheck-test-policy.ts": "7d945c6b1e23556154c7585d9e20e14010607a9e456f45c30f72b8812b411e1d",
155
161
  "packages/nx-plugin/src/version-actions.cts": "c579ed33d5641bd487024429758582fe1f7bde376cfbd4a4a4325aa70fb71883",
156
162
  "packages/nx-plugin/src/wait-why-policy.ts": "f10a5370665c0c38dc778d7532b2cd2b008221efea097b788aeaba8ee63745ea",
157
- "packages/nx-plugin/src/workspace-config-policy.ts": "6cd57431636ecc08eb550aa6771192fe3800159351d21dbb1057df51f8c3955b",
163
+ "packages/nx-plugin/src/workspace-config-policy.ts": "913b7de46078196fca05d9f2175d2f8ea73781391b32f4925d1657b8ccdc945e",
158
164
  "packages/nx-plugin/src/workspace-index.ts": "176a3ebd62dd2a928d38c2d91e5faa08625b4acb1c1a095718b5aaf1222deabc",
159
165
  "packages/nx-plugin/src/workspace-manifest.ts": "44d20244ff5fac9b6397e6c0ce6d9eac25d16f95c6a0c21a8cc70ca17067ce26",
160
166
  "packages/nx-plugin/src/workspace-package-policy.ts": "f569ce4e5d27168ea83aa41893573cb869d6f062d37133e95911fdd1d709fa8c",