@smoothbricks/nx-plugin 0.6.2 → 0.6.3-0

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 (97) hide show
  1. package/README.md +281 -73
  2. package/dist/.build-inputs.json +20 -14
  3. package/dist/bin/smoo-nx-publish.d.ts +3 -0
  4. package/dist/bin/smoo-nx-publish.d.ts.map +1 -0
  5. package/dist/bin/smoo-nx-publish.js +3 -0
  6. package/dist/cargo-retention-hook.d.ts +6 -2
  7. package/dist/cargo-retention-hook.d.ts.map +1 -1
  8. package/dist/cargo-retention-hook.js +13 -7
  9. package/dist/eslint-file-set.d.ts +4 -1
  10. package/dist/eslint-file-set.d.ts.map +1 -1
  11. package/dist/eslint-sources.d.ts +25 -0
  12. package/dist/eslint-sources.d.ts.map +1 -0
  13. package/dist/eslint-sources.js +99 -0
  14. package/dist/executors/all-verdicts/executor.d.ts +2 -1
  15. package/dist/executors/all-verdicts/executor.d.ts.map +1 -1
  16. package/dist/executors/all-verdicts/executor.js +48 -2
  17. package/dist/executors/all-verdicts/schema.d.ts +13 -0
  18. package/dist/executors/all-verdicts/schema.d.ts.map +1 -1
  19. package/dist/executors/all-verdicts/schema.js +7 -0
  20. package/dist/executors/bounded-exec/bounds.d.ts +57 -8
  21. package/dist/executors/bounded-exec/bounds.d.ts.map +1 -1
  22. package/dist/executors/bounded-exec/bounds.js +100 -11
  23. package/dist/executors/bounded-exec/executor.d.ts +2 -1
  24. package/dist/executors/bounded-exec/executor.d.ts.map +1 -1
  25. package/dist/executors/bounded-exec/executor.js +270 -27
  26. package/dist/executors/bounded-exec/hang-diagnostics.d.ts +2 -0
  27. package/dist/executors/bounded-exec/hang-diagnostics.d.ts.map +1 -1
  28. package/dist/executors/bounded-exec/hang-diagnostics.js +2 -2
  29. package/dist/executors/bounded-exec/mbx-pool.d.ts +20 -3
  30. package/dist/executors/bounded-exec/mbx-pool.d.ts.map +1 -1
  31. package/dist/executors/bounded-exec/mbx-pool.js +84 -4
  32. package/dist/executors/bounded-exec/mbx-queue.d.ts +30 -0
  33. package/dist/executors/bounded-exec/mbx-queue.d.ts.map +1 -0
  34. package/dist/executors/bounded-exec/mbx-queue.js +229 -0
  35. package/dist/executors/bounded-exec/progress.d.ts +9 -2
  36. package/dist/executors/bounded-exec/progress.d.ts.map +1 -1
  37. package/dist/executors/bounded-exec/progress.js +148 -22
  38. package/dist/executors/bounded-exec/test-result-writer.d.ts +30 -0
  39. package/dist/executors/bounded-exec/test-result-writer.d.ts.map +1 -0
  40. package/dist/executors/bounded-exec/test-result-writer.js +126 -0
  41. package/dist/executors/bounded-exec/test-results.d.ts +33 -0
  42. package/dist/executors/bounded-exec/test-results.d.ts.map +1 -0
  43. package/dist/executors/bounded-exec/test-results.js +33 -0
  44. package/dist/executors/bounded-exec/verdict.d.ts +20 -2
  45. package/dist/executors/bounded-exec/verdict.d.ts.map +1 -1
  46. package/dist/executors/bounded-exec/verdict.js +102 -4
  47. package/dist/index.d.ts +3 -2
  48. package/dist/index.d.ts.map +1 -1
  49. package/dist/index.js +67 -65
  50. package/dist/nx-publish.d.ts +24 -0
  51. package/dist/nx-publish.d.ts.map +1 -0
  52. package/dist/nx-publish.js +150 -0
  53. package/dist/runtime-input-policy.d.ts +14 -0
  54. package/dist/runtime-input-policy.d.ts.map +1 -1
  55. package/dist/runtime-input-policy.js +1 -1
  56. package/dist/tool-bins.d.ts +6 -8
  57. package/dist/tool-bins.d.ts.map +1 -1
  58. package/dist/tool-bins.js +7 -5
  59. package/dist/workspace-index.d.ts +7 -0
  60. package/dist/workspace-index.d.ts.map +1 -1
  61. package/dist/workspace-index.js +11 -0
  62. package/executors.json +1 -1
  63. package/managed/raw/patches/ttsc@0.34.1.patch +75 -0
  64. package/managed/raw/tooling/devenv +1 -2
  65. package/managed/raw/tooling/direnv/developer-links.ts +3 -0
  66. package/managed/raw/tooling/direnv/devenv.smoo.nix +34 -15
  67. package/managed/raw/tooling/direnv/github-actions-bootstrap.sh +20 -10
  68. package/managed/raw/tooling/direnv/setup-environment.ts +35 -20
  69. package/managed/raw/tooling/direnv/ttsc-env.sh +8 -6
  70. package/managed/templates/github/actions/cache-node-modules/action.yml +1 -1
  71. package/managed/templates/github/actions/cache-ttsc-plugins/action.yml +12 -11
  72. package/package.json +223 -7
  73. package/runtime/nx-publish/cache_adapter.js +45 -0
  74. package/runtime/nx-publish/nx_publish.js +60 -0
  75. package/runtime-input.sh +12 -3
  76. package/src/bin/smoo-nx-publish.ts +4 -0
  77. package/src/cargo-retention-hook.ts +16 -10
  78. package/src/eslint-file-set.ts +4 -1
  79. package/src/eslint-sources.ts +134 -0
  80. package/src/executors/all-verdicts/executor.ts +58 -3
  81. package/src/executors/all-verdicts/schema.json +4 -0
  82. package/src/executors/all-verdicts/schema.ts +14 -0
  83. package/src/executors/bounded-exec/bounds.ts +132 -15
  84. package/src/executors/bounded-exec/executor.ts +303 -27
  85. package/src/executors/bounded-exec/hang-diagnostics.ts +3 -2
  86. package/src/executors/bounded-exec/mbx-pool.ts +82 -5
  87. package/src/executors/bounded-exec/mbx-queue.ts +170 -0
  88. package/src/executors/bounded-exec/progress.ts +168 -15
  89. package/src/executors/bounded-exec/test-result-writer.ts +152 -0
  90. package/src/executors/bounded-exec/test-results.ts +39 -0
  91. package/src/executors/bounded-exec/verdict.ts +108 -5
  92. package/src/index.ts +74 -70
  93. package/src/nx-publish.ts +157 -0
  94. package/src/runtime-input-policy.ts +1 -1
  95. package/src/tool-bins.ts +13 -9
  96. package/src/workspace-index.ts +12 -0
  97. package/test-timings.json +8 -3
package/README.md CHANGED
@@ -77,15 +77,28 @@ question, answered only by the deploy tags the CLI reads (`stage-deploy-target`
77
77
 
78
78
  Lint commands are inferred per project. A workspace Biome configuration enables the project-wide Biome check; an ESLint
79
79
  flat configuration enables ESLint for existing JavaScript/TypeScript files under that project's `src` and the files its
80
- `tsconfig.test.json` declares, wherever they live. TypeScript resolves inherited `include`, `files` and `exclude`; the
81
- same sources, the test declaration and its existing `extends` chain are explicit lint cache inputs. Both lists hold only
82
- files in Nx's workspace file index (.gitignore and .nxignore applied), so a gitignored generated module that a build
83
- left on disk is neither linted nor keyed, and the lint target is the same in every checkout of one tree. Rust-only
80
+ `tsconfig.test.json` declares, wherever they live. TypeScript resolves inherited `include`, `files` and `exclude`. Only
81
+ files in Nx's workspace file index (.gitignore and .nxignore applied) count, so a gitignored generated module that a
82
+ build left on disk is neither linted nor keyed, and the lint target is the same in every checkout of one tree. Rust-only
84
83
  source trees keep their Cargo validation and manifest checks without invoking ESLint on nonexistent JavaScript inputs.
85
84
  Test-config diagnostics retain TypeScript's parsed-command-line types through bootstrap emit; invalid declarations fail
86
- with their diagnostic code and message, while an empty test program (TS18003) contributes no test files. Adding
87
- JavaScript/TypeScript sources or changing the declared test program updates lint coverage automatically. The target's
88
- `metadata.eslintFileSet` retains that exact command and workspace-relative file list for cache inspectors.
85
+ with their diagnostic code and message, while an empty test program (TS18003) contributes no test files.
86
+
87
+ The ESLint command names no file. It is `eslint {eslintSources}`, and the target's `eslintProjectRoot` option names the
88
+ project whose sources the placeholder stands for. A graph holds the files of the moment it was computed, and the daemon
89
+ serves it past a deletion or an addition its watcher never reported: a list in the command made ESLint refuse a pattern
90
+ no file matches, and left a new file unlinted, until the graph recomputed. The `all-verdicts` executor replaces the
91
+ placeholder when the command runs, with the files the rules above select out of a fresh workspace file index: a new
92
+ native context over the filesystem, never the table of the process or of the daemon, which learn of a write only when a
93
+ watcher event reaches them. A project with none passes without starting ESLint. Adding JavaScript/TypeScript sources or
94
+ changing the declared test program changes what the next run lints, with no graph computation in between.
95
+
96
+ The lint inputs key the same program without naming each file: the test declaration and its existing `extends` chain,
97
+ one glob over the JavaScript and TypeScript kinds for each directory the declaration's include patterns walk (none for a
98
+ directory outside the workspace or inside a build output directory), and every other program file by name. A file the
99
+ program gains is keyed the moment it exists. A glob also covers what `exclude` removes from the program: keyed, never
100
+ linted. The target's `metadata.eslintFileSet` retains the command and the workspace-relative file list the graph
101
+ resolved, for cache inspectors: the list describes that graph, and what runs is read when it runs.
89
102
  `@smoothbricks/nx-plugin/eslint-file-set` owns its type and generated validator; an inspector can resolve each file's
90
103
  actual ESLint parser program instead of guessing from the project or target name.
91
104
 
@@ -95,8 +108,8 @@ errors would hide another's until a later run. `all-verdicts` starts every comma
95
108
  command's output prints as one block when it closes, then every command's verdict: `PASS`, `FAIL (exit n)`, or
96
109
  `UNJUDGED` with its cause when a signal ended it, it never started, or the run itself was signalled. A signal to the run
97
110
  ends each command's process group, and the run then ends by the same signal. The target passes only when every command
98
- passed; an empty command list is refused, since it could never fail. The options keep `commands` and `cwd`, so each
99
- tool's command, the inputs that key it and `metadata.eslintFileSet` are what they were.
111
+ passed; an empty command list is refused, since it could never fail. The options are `commands`, `cwd` and, for a
112
+ project with an ESLint command, `eslintProjectRoot`; a command's block and verdict name it as it ran.
100
113
 
101
114
  Lint inputs include dependency production inputs because type-aware ESLint reads dependencies' declarations. This uses
102
115
  `^production` unless the workspace opts into the versionless production input described below. Keep
@@ -231,61 +244,71 @@ The plugin discovers Cargo workspaces beside Nx project manifests at any depth:
231
244
  only grows. After each Nx run that executed a Cargo producer (an inferred target that builds, checks or tests into the
232
245
  target directory, marked by its `cargoProducer` metadata: `cargo-test-archive`, `cargo-test`, `cargo-lint`,
233
246
  `cargo-lint-cross`, mutation, bench, and the napi and wasm builds), the plugin's `postTasksExecution` runs its Cargo
234
- retention hook, which calls `@smoothbricks/cargo-retain` for each Cargo workspace that is due for maintenance. In an
235
- mbx project, whose canonical environment names `MBX_CACHE_DIR` beside `MBX_TARGET_VIEWS=1`, the targets are mbx's to
236
- collect and the hook does nothing. Automatic passes run at most once per 24 hours after a successful completed pass,
237
- one that reclaimed in every root; its existing receipt records completion time and configuration/workspace/target
238
- identity. A not-due hook reports that scheduling decision without locks, a fingerprint scan, cleanup or receipt
239
- replacement. It does not claim newer outputs were inspected or the graph is unchanged. Busy, refused, invalid, foreign
240
- or backward-clock receipt evidence never postpones the next attempt. The first executed producer after the interval
241
- runs a current pass; cache replays, fetch and noop tasks start none. Manual preview and apply always run fresh. Due
242
- passes reclaim superseded generations under `<profile>/build/<package>/<META>/`. They keep the newest generation, by
243
- last use, of each unit identity of a workspace member (identity is every fingerprint field but its edges, source state
244
- and toolchain, which is `rustc` and the `--sysroot` flag; integers read exactly, so a newer toolchain supersedes an
245
- older one), every unit used in the last 24 hours (`-Zmtime-on-use` stamps each use; cowshed exports
246
- `CARGO_UNSTABLE_MTIME_ON_USE=true` to every host shell and job of a Cargo project, and a repository outside cowshed
247
- sets `[unstable] mtime-on-use = true`), and the transitive dependency closure of those across every profile, host and
248
- cross alike. A root whose hash files show no stamp (none newer than its compile by more than 24 hours) reports
249
- `recency-unknown: mtime-on-use off`: its last use is then only its last compile. A profile that holds a legacy layout
250
- beside the current one is read for the current one, and its legacy entries are retained as `legacy-layout`. A pass
251
- holds every profile's Cargo locks without waiting: one held lock skips the pass as `busy`, and a profile it cannot
252
- read (unreadable fingerprint, missing `build/` or lock, or a legacy layout's records alone) refuses the whole pass, as
253
- does a lock it cannot attempt at all, with the reason named: under Node, macOS takes its `flock(2)`s in-process
254
- (`open(2)` with `O_EXLOCK | O_NONBLOCK`) and starts no helper, and other platforms hold them in a perl child, so a
255
- sandbox that refuses to exec perl, like a lock file that cannot be opened, refuses the pass instead of failing the
256
- run. The compiled CLI opens and locks through a small C wrapper (`native/flock.c`) that captures `errno` immediately.
257
- Each provider's canonical refusal retains the operation, exact lock path, actual host errno and OS cause: only
258
- contention is `busy`; any other failure refuses the pass. The hook only reports outcomes and never fails the run it
259
- follows: whatever escapes a pass is logged as a warning, and the next workspace is still tried. It moves each
260
- reclaimed generation into the profile's `.smoo-retention-trash/` under that hold, recording its inode first, and
261
- unlinks it after letting go. Each proven generation gets a synchronous, non-symlink-following inode census and one
262
- native recursive removal, not an awaited lstat/unlink for every artifact. The census counts internal hardlinks once;
263
- the pass ledger drops an inode only when its last link is removed, so bytes freed and bytes still linked outside the
264
- removed generations remain distinct. The manifest's root identity is rechecked immediately before removal. A failed
265
- removal is an I/O failure, not a successful reclaim or a new completed maintenance receipt. It writes its last report
266
- to `<target>/.smoo-cargo-retention.json`. Cargo's root-relative fingerprint paths distinguish cross profiles from
267
- nested target roots under the lock; mixed, foreign or unprovable cross-profile roots refuse the pass rather than
268
- silently dropping their dependency edges. That scan finds a nested target root (`target/cargo-lint`,
269
- `target/cargo-lint-cross`) by locking and reading its depth-two profile like the target's own, so a pass held or
270
- refused there reaches no nested root. Each nested root then gets the same pass over its own profiles, host and cross,
271
- under only their Cargo locks and the target's one retention lock, one root after another: units never depend across
272
- roots, so a nested root that is held (a lint running into it) or refused is skipped and reported in the receipt's
273
- `nestedRoots` without holding up the others, and the receipt schedules the next automatic pass only when every root
274
- reclaimed. Only generations are reclaimed, never a root or a profile, and a nested root holding no unit of a workspace
275
- member is retained whole as `foreign-root`. A pre-created target need not carry Cargo's optional backup tag; a present
276
- but invalid tag still refuses the pass. Every pass still reads the current fingerprint graph. The locked scan reuses
277
- directory-entry types and reads its small metadata files synchronously, avoiding duplicate stats and one asynchronous
278
- dispatch per tiny file; it does not walk retained artifact contents or reuse an earlier graph that could miss in-place
279
- recompiles. `cargo-retention` runs that package's native `smoo-nx-cargo-retain` executable to preview the same
280
- selection, nested roots included, without changing anything. Each profile's `incremental/<crate>-<id>/` directories go
281
- in the same pass: rustc keeps one per build variant and never removes the one a feature, profile or flag change
282
- superseded. One is kept while its newest finished session started inside the compile window (`invoked.timestamp` to
283
- the hash file's last write) of a kept unit of the same crate, while it started within the recent-use window, or while
284
- the directory holds an unfinished or unreadable session. The split-debuginfo objects rustc keeps inside current
285
- generations (rust-lang/rust#161824) are not reclaimed, so a target directory is not bounded by them. Empty fingerprint
286
- hashes are kept as unfinished compilations. The preservation proof covers Cargo's current unit and dependency records,
287
- not every debug reference in copied binaries or other checkouts. In particular, a binary copied up before a failed
288
- link can outlive the generation its debug map names; this pass does not establish that machine-wide debug closure.
247
+ retention hook, which starts a pass of `@smoothbricks/cargo-retain` for each Cargo workspace that is due for
248
+ maintenance, in a process of its own (below). In an mbx project, whose canonical environment names `MBX_CACHE_DIR`
249
+ beside `MBX_TARGET_VIEWS=1`, the targets are mbx's to collect and the hook does nothing. Automatic passes run at most
250
+ once per 24 hours after a successful completed pass, one that reclaimed in every root; its existing receipt records
251
+ completion time and configuration/workspace/target identity. A not-due hook reports that scheduling decision without
252
+ locks, a fingerprint scan, cleanup or receipt replacement. It does not claim newer outputs were inspected or the graph
253
+ is unchanged. Busy, refused, invalid, foreign or backward-clock receipt evidence never postpones the next attempt. The
254
+ first executed producer after the interval runs a current pass; cache replays, fetch and noop tasks start none. Manual
255
+ preview and apply always run fresh. Due passes reclaim superseded generations under
256
+ `<profile>/build/<package>/<META>/`. They keep the newest generation, by last use, of each unit identity of a
257
+ workspace member (identity is every fingerprint field but its edges, source state and toolchain, which is `rustc` and
258
+ the `--sysroot` flag; integers read exactly, so a newer toolchain supersedes an older one), every unit used in the
259
+ last 24 hours (`-Zmtime-on-use` stamps each use; cowshed exports `CARGO_UNSTABLE_MTIME_ON_USE=true` to every host
260
+ shell and job of a Cargo project, and a repository outside cowshed sets `[unstable] mtime-on-use = true`), and the
261
+ transitive dependency closure of those across every profile, host and cross alike. A root whose hash files show no
262
+ stamp (none newer than its compile by more than 24 hours) reports `recency-unknown: mtime-on-use off`: its last use is
263
+ then only its last compile. A profile that holds a legacy layout beside the current one is read for the current one,
264
+ and its legacy entries are retained as `legacy-layout`. A pass holds every profile's Cargo locks without waiting: one
265
+ held lock skips the pass as `busy`, and a profile it cannot read (unreadable fingerprint, missing `build/` or lock, or
266
+ a legacy layout's records alone) refuses the whole pass, as does a lock it cannot attempt at all, with the reason
267
+ named: under Node, macOS takes its `flock(2)`s in-process (`open(2)` with `O_EXLOCK | O_NONBLOCK`) and starts no
268
+ helper, and other platforms hold them in a perl child, so a sandbox that refuses to exec perl, like a lock file that
269
+ cannot be opened, refuses the pass instead of failing the run. The compiled CLI opens and locks through a small C
270
+ wrapper (`native/flock.c`) that captures `errno` immediately. Each provider's canonical refusal retains the operation,
271
+ exact lock path, actual host errno and OS cause: only contention is `busy`; any other failure refuses the pass. The
272
+ hook only reports outcomes and never fails the run it follows: whatever escapes a pass is logged as a warning, and the
273
+ next workspace is still tried. The pass itself never runs on Nx's thread: Nx awaits `postTasksExecution`, inside its
274
+ daemon when one serves the run, and a pass unlinks synchronously, so one freeing 80 trashed generations on a loaded
275
+ APFS volume held a land gate's daemon, and every client waiting on it, for more than thirty minutes. The hook answers
276
+ only the gate there (not due, the retention lock busy or unattemptable, each reported as above), lets go of the
277
+ retention lock and starts the due pass as the package's Node CLI, `smoo-nx-cargo-retain --apply --automatic`, detached
278
+ (`startRetentionPass`, `launch-node.ts`). Its standard streams are `/dev/null`, and it inherits no descriptor of the
279
+ run's, so neither the run's exit nor a reader of its output waits for it, and the daemon goes on serving. That process
280
+ goes through the gate again, takes every lock itself and records its outcome in the receipt; while it frees its trash
281
+ it holds the retention lock, so the next run's gate reports `busy` and starts no second pass. It moves each reclaimed
282
+ generation into the profile's `.smoo-retention-trash/` under that hold, recording its inode first, and unlinks it
283
+ after letting go. Each proven generation gets a synchronous, non-symlink-following inode census and one native
284
+ recursive removal, not an awaited lstat/unlink for every artifact. The census counts internal hardlinks once; the pass
285
+ ledger drops an inode only when its last link is removed, so bytes freed and bytes still linked outside the removed
286
+ generations remain distinct. The manifest's root identity is rechecked immediately before removal. A failed removal is
287
+ an I/O failure, not a successful reclaim or a new completed maintenance receipt: the receipt says `failed` with the
288
+ reason, as it does for anything else that fails an applied pass past its gate. It writes its last report to
289
+ `<target>/.smoo-cargo-retention.json`. Cargo's root-relative fingerprint paths distinguish cross profiles from nested
290
+ target roots under the lock; mixed, foreign or unprovable cross-profile roots refuse the pass rather than silently
291
+ dropping their dependency edges. That scan finds a nested target root (`target/cargo-lint`, `target/cargo-lint-cross`)
292
+ by locking and reading its depth-two profile like the target's own, so a pass held or refused there reaches no nested
293
+ root. Each nested root then gets the same pass over its own profiles, host and cross, under only their Cargo locks and
294
+ the target's one retention lock, one root after another: units never depend across roots, so a nested root that is
295
+ held (a lint running into it) or refused is skipped and reported in the receipt's `nestedRoots` without holding up the
296
+ others, and the receipt schedules the next automatic pass only when every root reclaimed. Only generations are
297
+ reclaimed, never a root or a profile, and a nested root holding no unit of a workspace member is retained whole as
298
+ `foreign-root`. A pre-created target need not carry Cargo's optional backup tag; a present but invalid tag still
299
+ refuses the pass. Every pass still reads the current fingerprint graph. The locked scan reuses directory-entry types
300
+ and reads its small metadata files synchronously, avoiding duplicate stats and one asynchronous dispatch per tiny
301
+ file; it does not walk retained artifact contents or reuse an earlier graph that could miss in-place recompiles.
302
+ `cargo-retention` runs that package's native `smoo-nx-cargo-retain` executable to preview the same selection, nested
303
+ roots included, without changing anything. Each profile's `incremental/<crate>-<id>/` directories go in the same pass:
304
+ rustc keeps one per build variant and never removes the one a feature, profile or flag change superseded. One is kept
305
+ while its newest finished session started inside the compile window (`invoked.timestamp` to the hash file's last
306
+ write) of a kept unit of the same crate, while it started within the recent-use window, or while the directory holds
307
+ an unfinished or unreadable session. The split-debuginfo objects rustc keeps inside current generations
308
+ (rust-lang/rust#161824) are not reclaimed, so a target directory is not bounded by them. Empty fingerprint hashes are
309
+ kept as unfinished compilations. The preservation proof covers Cargo's current unit and dependency records, not every
310
+ debug reference in copied binaries or other checkouts. In particular, a binary copied up before a failed link can
311
+ outlive the generation its debug map names; this pass does not establish that machine-wide debug closure.
289
312
  - **Scheduling:** inference never throttles Nx. It sets no `parallelism: false` or `parallel: false`, no cap, and no
290
313
  edge whose only purpose is keeping two cargo writers off one `target/`: Cargo owns that lock, and a second process
291
314
  waits inside cargo. An edge states a real consumer — fetch before frozen cargo, the archive before the runners,
@@ -401,10 +424,11 @@ build-script names) are not compared: a run that recorded one was started by a `
401
424
 
402
425
  A target whose inputs a repository DECLARES replaces the inferred list, toolchain identity included. Name
403
426
  `cargoToolchain` in that declaration, or in the named input it uses: inference defines it, in every project that has
404
- cargo targets, as the whole identity. A restated lock is not enough, because the identity also holds the runtime input
405
- no fileset can state, and `smoo monorepo check` refuses a cached cargo target that does not reach the name. The replaced
406
- list also held the target's `externalDependencies` entries described below; restate them (`[]` for a target that runs
407
- only cargo, and the lock-scope node of its crates), or every lockfile change re-keys the target.
427
+ inferred or declared cargo targets, as the whole identity. A restated lock is not enough, because the identity also
428
+ holds the runtime input no fileset can state, and `smoo monorepo check` refuses a cached cargo target that does not
429
+ reach the name. The replaced list also held the target's `externalDependencies` entries described below; restate them
430
+ (`[]` for a target that runs only cargo, and the lock-scope node of its crates), or every lockfile change re-keys the
431
+ target.
408
432
 
409
433
  Every cached cargo target names the npm packages its command runs as `externalDependencies`: none for cargo itself, and
410
434
  `@smoothbricks/nx-plugin` for a target that runs its executor or reads its installed files (the nextest tool config, the
@@ -538,11 +562,13 @@ command and its cause beside Nx's decoder error, which names neither.
538
562
  Each readable `report` names the command, its indexed arguments, working directory, exit status and original stderr.
539
563
  `argv` retains the exact NUL-delimited argument vector (including empty arguments), `stderr` retains the original bytes
540
564
  (including trailing newlines), and `exit-status` retains the decimal status. The wrapper also attempts a stderr summary
541
- naming the command and report path, and displays the report on `/dev/tty` when it can open a controlling terminal.
542
- Neither display is guaranteed through Nx's daemon or a headless harness: rely on the retained report, not on Nx
543
- forwarding stderr. A failed terminal write is retained in the record's `terminal-error`. Records can contain arguments
544
- or stderr with credentials; keep them private and inspect before sharing. Evidence-storage errors name the problem and
545
- the surviving stderr capture on stderr; they never remove the refusal byte or replace the command's status.
565
+ naming the command and report path, and displays the report on `/dev/tty` when it can open a controlling terminal. Nx's
566
+ daemon has none (`ENXIO`) and cowshed's sandbox denies it (`EPERM`); having no terminal is no failure of the input, so
567
+ the shell's refusal of the open joins the stderr summary and the record gains nothing. Neither display is guaranteed
568
+ through Nx's daemon or a headless harness: rely on the retained report, not on Nx forwarding stderr. A write that fails
569
+ on a terminal that did open is retained in the record's `terminal-error`. Records can contain arguments or stderr with
570
+ credentials; keep them private and inspect before sharing. Evidence-storage errors name the problem and the surviving
571
+ stderr capture on stderr; they never remove the refusal byte or replace the command's status.
546
572
 
547
573
  Successful commands still emit only their original stdout bytes, discard stderr and retain no failure record: no
548
574
  evidence path, timestamp or diagnostic enters a successful key. `runtime-input.test.ts` compares that byte stream and
@@ -879,6 +905,24 @@ installed. Every fallback costs cache hits and never trades away invalidation, b
879
905
  reporting a failing one — a fileset that excluded a manifest with no digest replacing it would serve stale results
880
906
  silently.
881
907
 
908
+ ## Accepted task cache publication
909
+
910
+ Declared gates use the emitted `smoo-nx-publish` executable from this package; they do not carry a publisher copy.
911
+ `hashes <run.json> <since-epoch-seconds>` prints the distinct succeeded task hashes as JSON, refusing a summary begun
912
+ before that invocation. Capture each list immediately, before another Nx call overwrites the summary.
913
+ `publish <absolute-checkout> <hashes.json>` sends existing local cache entries to that checkout's accepted-store route.
914
+ Call it only after every gate check passes. Red gates publish nothing, and ordinary shed clients stay read-only.
915
+ Publication prints stored/existing/skipped counts; an operational refusal exits nonzero with its cause. The gate reports
916
+ that cache finding distinctly without changing the checks' verdict (cowshed specs 03, "Nx accepted-task artifact
917
+ service", and 05, "Publication"). No task is rebuilt and no shell is evaluated by the publisher.
918
+
919
+ The canonical cache adapter and native publisher remain in
920
+ `packages/cowshed/crates/cowshed-core/src/build_volume/{cache_adapter.js,nx_publish.js}`. The cached
921
+ `copy-nx-publish-assets` target declares those source inputs and owns `runtime/nx-publish/`, disjoint from the entire
922
+ TypeScript `dist/` output. It copies their unchanged bytes; there is one implementation, not two maintained sources.
923
+ `build` depends on that producer and the emitted executable. `test-nx-publish` depends on the concrete JavaScript and
924
+ runtime-asset producers and loads their bytes; tests never build the publisher or its runtime assets inline.
925
+
882
926
  ## Build/Test Graph Boundary
883
927
 
884
928
  The final-graph `createMetadata` hook also calls `refuseBuildTestDependencies(graph, workspaceRoot)` from
@@ -1318,6 +1362,20 @@ A wildcard without a caret selects the current project instead. For example, a w
1318
1362
  this local relationship explicit for inferred `tsc-js` targets that also have inferred `cargo-wasm`. Package-managed
1319
1363
  JavaScript targets with another platform prerequisite must likewise declare that local edge themselves.
1320
1364
 
1365
+ A self-hosted workspace that owns the plugin's cowshed dependency builds its declared `napi-native` and independent
1366
+ `lineage-js` producers before **every bounded-exec task**, including declared Bun targets, inferred Cargo shards and
1367
+ root serial groups. Native tool discovery resolves that local owner from the linked package manifest, not a repository
1368
+ path or project-name alias; an installed consumer takes no local producer edge because its package ships the addon and
1369
+ lineage entry. The plugin's compile and typecheck targets require only `lineage-js`, never the addon or cowshed's full
1370
+ API build. Its runtime-only cowshed project dependency is excluded from ordinary caret build edges, avoiding the
1371
+ executor bootstrap cycle. Bounded targets key on the produced addon and lineage JavaScript bytes through their producer
1372
+ edges, not the workspace’s Rust sources. Declarations that replace `dependsOn` or `inputs` keep the inferred
1373
+ preconditions with Nx’s `"..."` token. When a declaration changes an inferred executor to bounded-exec, its compatible
1374
+ inferred base contains only these runtime prerequisites and output inputs; the incompatible executor’s command and
1375
+ inputs do not leak across the normal Nx override. The canonical dependency-free `release-check` is the exception: it
1376
+ judges already assembled shipping artifacts and verifies the addon is present, without compiling at runtime or disabling
1377
+ the observer (specs/cowshed/06_cli.md, `release-check`).
1378
+
1321
1379
  N-API binaries are not prerequisites of TypeScript declaration emission, so compiler targets do not pull them in by
1322
1380
  default. Aggregate `build` remains the package-completeness boundary and includes every published local output family.
1323
1381
 
@@ -1900,6 +1958,42 @@ waiting for, however long a loaded host makes the work take; one that never retu
1900
1958
  `idleTimeoutMs`. `timeoutMs`, an absolute ceiling, is for commands that report no tests; a target names at least one of
1901
1959
  the two.
1902
1960
 
1961
+ With mbx admission, a reserved leaf and a supported Cargo/nextest test leaf inherit a private grant pipe. mbx writes `g`
1962
+ on every admission and `r` on permit drop (`MBX_GRANT_FD=5` for Cargo, `mbx reserve --grant-fd 5` for reservations). The
1963
+ executor counts overlapping holds: while no hold exists it pauses the test idle budget, resuming the remaining budget on
1964
+ admission; a finished test still resets that budget. Total and fixture ceilings start at the first `g` and do not pause
1965
+ after it. EOF is not a grant or a release; a holder killed without `r` remains counted until command exit.
1966
+
1967
+ Independently of that spawn-time zero-hold rule, **any live task process explicitly queued for mbx admission pauses
1968
+ idle**, even while another task process holds capacity or the runner is otherwise unsupported. The executor polls public
1969
+ `mbx stats --scheduler --json --activity` activity, accepting only `kind: "waiter"`, `live: true` rows whose PID is
1970
+ corroborated by bounded, scoped per-PID lineage reads through cowshed's native `processLineages` owner (libproc on
1971
+ macOS, procfs on Linux), never a spawned ps or a process-table census. Names, private waiter files and decision logs
1972
+ prove nothing. Public `queue_position` is preserved, never recomputed by the consumer. A successful snapshot with no
1973
+ task waiters resumes the remaining budget when the lifecycle and hold count permit it; a finished test resets the paused
1974
+ budget. An idle callback drains any in-flight poll and takes a fresh bounded snapshot before expiring. The stats read
1975
+ and every native lineage batch share one five-second monotonic control-plane budget, independent of the idle clock; late
1976
+ or cancelled snapshots never become queue or empty-membership evidence. Snapshot failures are reported operational
1977
+ failures, never manufactured queue/admission evidence or an idle wedge; an unidentifiable foreign legacy row is
1978
+ diagnosed without claiming task membership. Live diagnostics say `queued for admission N s` with the mbx queue position.
1979
+ A command that fails or is cancelled before its first admission records a distinct `queued` verdict with observed wait
1980
+ duration and its last public PID/ticket/position rows. Queue observation adds no deadline and changes neither total nor
1981
+ fixture ceilings. Queue observations take effect at snapshot completion, never backdated across a finished test's budget
1982
+ reset. Observed wait duration freezes when the command settles or cancellation stops observation, before teardown or
1983
+ report reading. The observer requires the version-2 activity-only report; the full statistics document's cache, savings
1984
+ and memory histories are not polling input. The activity projection omits those walks and encodings instead of raising
1985
+ the observer's output or control-plane limits.
1986
+
1987
+ The decision to use zero-hold pausing is made before spawn, from the canonical scheduling switch and the supported
1988
+ command, never from silence on the pipe. The inferred extracted-archive
1989
+ `cargo --frozen nextest run --binaries-metadata …` is hold-gated, including chains joined by `&&`, `||`, or `;` when
1990
+ every leg is a supported scheduled Cargo test execution. Each leg is checked separately; a later unscheduled command,
1991
+ pipeline or background command retains conservative idle protection. Plain `cargo test` can also run unscheduled
1992
+ doctests, so it retains its lifecycle idle clock, as do unknown runners, direct binaries, test listings,
1993
+ configuration/toolchain/directory overrides, and `--archive-file` whose target is not known at spawn. Explicit non-doc
1994
+ Cargo target selections can be hold-gated. These conservative cases remain bounded even when they never hold an mbx
1995
+ permit (specs/cowshed/11_shell.md, "Cargo test-runner boundaries").
1996
+
1903
1997
  On POSIX hosts, direct Go and Cargo test commands (including chains joined by `&&`, `||`, or `;`) share one private
1904
1998
  runner lifecycle: `build`, `active`, and `terminal`. A per-command Node supervisor reports phases over an acknowledged
1905
1999
  descriptor that its actual tool child and nested fixtures do not inherit. Shell/supervisor startup is bounded; the tool
@@ -2348,6 +2442,100 @@ binary the target named. A script that spawns the runner itself passes
2348
2442
  `--reporter=junit --reporter-outfile="$BOUNDED_EXEC_JUNIT"` on; the variable is set for every task. A command with no
2349
2443
  runner, or with two (they would write one report), is judged by its exit alone.
2350
2444
 
2445
+ ### Live per-test closed results
2446
+
2447
+ A task also publishes live observations in `test-results.jsonl`, beside its `report.xml` and `verdict.json` in
2448
+ `.nx/workspace-data/bounded-exec/<encodeURIComponent(taskId)>/` (under Nx's configured workspace-data directory). The
2449
+ public `@smoothbricks/nx-plugin/test-results` entry is pure: it exports `ClosedTestResult`, its generated strict
2450
+ `isClosedTestResult` guard, `TEST_RESULTS_FILE`, `TEST_FAILURES_FILE`, and `parseTestSourceRef`, with no host IO
2451
+ imports. The separate `@smoothbricks/nx-plugin/test-results/host` entry owns the artifact writer and
2452
+ `taskDirectory(workspaceData, taskId)`. These observations let a consumer act on a closed failure while other tests
2453
+ still run. They never replace terminal JUnit or the verdict as gate evidence.
2454
+
2455
+ Both runtime entries always resolve to the declared `dist` products, with no raw-source development condition. A
2456
+ consumer's production bundler may also inherit a development condition from its TypeScript configuration; it must never
2457
+ embed an untransformed Typia macro. The cached `closed-results-runtime-bundle` test-setup producer builds a public-entry
2458
+ fixture under those production conditions after `tsc-js` and `typecheck-tests`. `test-results-runtime` executes only
2459
+ that prebuilt bundle under the standard no-progress bound, without a wall-clock ceiling. The producer is test setup, not
2460
+ a runner in the `test-*` namespace. The test compiles no toolchain or fixture inline, and package tests reach it through
2461
+ their aggregate.
2462
+
2463
+ Each record is one UTF-8 JSON object followed by LF:
2464
+
2465
+ ```json
2466
+ {
2467
+ "runId": "8b608ad0-fb8c-4d65-9a58-7dd140776235",
2468
+ "id": "case.test.ts::outer > test",
2469
+ "status": "fail",
2470
+ "source": "progress",
2471
+ "durationMs": 2.5,
2472
+ "sourceRef": null,
2473
+ "causeRef": { "path": "test-failures.log", "startByte": 0, "endByte": 123 },
2474
+ "cursor": 321
2475
+ }
2476
+ ```
2477
+
2478
+ The numbers above illustrate the fields, not an encoded record's actual byte lengths. `id` is `suite::name`: Bun uses
2479
+ its reported file and outer-to-inner describe/test chain; nextest uses the native name's suite prefix before `$` and its
2480
+ test name (a final retry's appended attempt count is removed); Go uses package and test name. Status is `pass`, `fail`,
2481
+ or `skip`. `durationMs` is the native duration in milliseconds, or `null` when none is reported. `sourceRef` is `null`
2482
+ without a native location; otherwise it is the test declaration's workspace-root-relative, forward-slash `file:line`,
2483
+ with a one-based line. It is not a diagnosis of the production failure. `parseTestSourceRef` projects that location to
2484
+ `{ path, line }`; paths outside the workspace retain `../` and must not qualify local ownership.
2485
+
2486
+ `causeRef` is `null` without failure output. Otherwise its task-directory-relative `path` is `test-failures.log` and
2487
+ `[startByte, endByte)` is the exact UTF-8 byte range of that observation's captured diagnostics. The evidence append
2488
+ completes before the referring JSONL append. Each append is unbuffered at the application boundary and visible before
2489
+ the next record; this is live visibility, not an fsync/crash-durability promise. `cursor` is the exclusive next byte
2490
+ offset in the JSONL file, including LF. Read complete lines only, validate each record, and resume at its cursor; keep
2491
+ an incomplete final line until its LF arrives. Cursor and cause offsets are nonnegative safe integers.
2492
+
2493
+ `runId` is a fresh UUID per invocation. Previous task artifacts are removed at admission; before the command starts, the
2494
+ writer prepares new empty files and atomically replaces the cause file, then the JSONL file, with new inodes. A consumer
2495
+ must detect replacement/truncation, reopen at byte zero and admit the new `runId`, not reuse a previous run's cursor.
2496
+ The producer pins its own append descriptors until terminal/refusal, so an older overlapping invocation cannot append
2497
+ into a replacement run's files. Pin the cause file descriptor for a run if its evidence must survive replacement. The
2498
+ stream is empty for an unsupported runner; no identity or result is guessed from arbitrary output.
2499
+
2500
+ Native channels and provenance: See the [nextest JSON channel](https://nexte.st/docs/machine-readable/libtest-json/) and
2501
+ [Bun reporter documentation](https://bun.com/docs/test/reporters); the Bun live-progress exception below is the owner's
2502
+ explicit contract, not a claim that its console output is a structured reporter API.
2503
+
2504
+ - nextest uses `--message-format=libtest-json-plus --message-format-version=0.1` and
2505
+ `NEXTEST_EXPERIMENTAL_LIBTEST_JSON=1` (pinned nextest 0.9.143). JSON-plus flushes each test terminal; plain
2506
+ `libtest-json` buffers a binary and is not a live channel. A terminal describes the final retry, with the final
2507
+ attempt's duration; suite summaries are not test results. Failure output is the native combined output or reason.
2508
+ These records have `source: "native"`. There is no native source location. No-capture/debugger/tracer commands are
2509
+ left unchanged because raw test output would destroy structured-channel attribution. Ignored-test delivery follows
2510
+ nextest's own channel: an ignored start is not evidence a test ran, and a binary with no executed test may omit its
2511
+ ignored terminals. The human progress display remains the owner of in-flight watchdog names.
2512
+ - Go reuses the existing `go test -json` decoder: only test-level pass/fail/skip terminals produce records, never
2513
+ package terminals or output heartbeats. Its native test output supplies failure evidence, and `Elapsed` supplies the
2514
+ duration when present. These records have `source: "native"`; the channel supplies no declaration location.
2515
+ - Bun reuses the watchdog's existing named result-line scan, not another console parser. Per the owner's ruling of
2516
+ 2026-10-29 these records have `source: "progress"`, explicitly provisional: publish immediately when a named result
2517
+ closes, never wait for later tests. Bun prints diagnostics before its `(fail)` line, so failure evidence is the
2518
+ captured stderr interval since the preceding named result through this failure line. It can include unrelated output
2519
+ and is not proof of root-cause ownership. The pinned Bun 1.4.3 inspector reporter loses events at exit and under
2520
+ parallel/isolate execution, while its JUnit reporter writes only at the end; neither is a reliable complete live
2521
+ channel. Dots and agent-mode output omit passing/skip names, so no identities are invented for dots. Terminal Bun
2522
+ JUnit supplies those missing named results as `source: "junit"`. If its status contradicts a provisional record of the
2523
+ same identity, a new `source: "junit"` record carries the authoritative status and `contradictsCursor` pointing to
2524
+ that earlier record's cursor; matching statuses produce no duplicate. Summary reprints are not new completions.
2525
+ Concurrent/parallel workers can interleave file headers and diagnostics, and names containing the describe separator
2526
+ or duplicate names are ambiguous in console output. Consumers must retain the progress provenance and defer uncertain
2527
+ attribution to terminal structured evidence; never infer a source path from the name.
2528
+
2529
+ This contract is covered by the pure native/progress mapping and artifact tests and the real Bun/nextest smoke in
2530
+ `src/executors/bounded-exec/test-results-run.test.ts`: an early failure is visible while later work is held by IPC,
2531
+ before either terminal report exists. Readiness comes from complete LF-terminated records checked by the public schema
2532
+ and the held test's IPC connection, never from console text, ANSI escapes or result symbols. The smoke runs with colored
2533
+ output, reads the referenced UTF-8 cause before releasing the held test, then checks the same run's terminal stream,
2534
+ JUnit and verdict. `nx-plugin:cargo-stream-archive` produces the smoke's nextest archive before any Bun shard starts;
2535
+ the smoke executes that archive and never compiles inside the test progress interval. The reporter smoke likewise
2536
+ executes the transformed `dist/bin/smoo-nx-bound-failures.js` supplied by the shards' `build` dependency, not raw
2537
+ TypeScript whose imports may require schema generation. Test ownership and readiness follow
2538
+ [`specs/cowshed/08_testing.md`](../../specs/cowshed/08_testing.md), “Unit tests” and “Fixtures”.
2351
2539
  `smoo-nx-bound-failures` reads the workspace's last Nx run (`run.json` in Nx's `cacheDir`, the directory
2352
2540
  `StoreRunInformationLifeCycle` writes: the checkout's own `.nx/cache` under smoo's workspace policy) against those
2353
2541
  records and prints one line per failed task. It exits 0 only when the run failed and every failed task's record, for
@@ -2541,12 +2729,32 @@ Files with a `# smoo-local` tail or `# smoo-local-begin` / `# smoo-local-end` bl
2541
2729
  source symlinks are preserved; conflicting local blocks and broken or external links are reported instead of
2542
2730
  overwritten. The generator does not remove a repository-owned file when a capability is disabled.
2543
2731
 
2732
+ `tooling/devenv` is an executable wrapper, whether copied into a consumer or symlinked to the packaged script. It
2733
+ selects `tooling/direnv` beside the invocation path in that checkout, not beside the symlink's resolved source. A
2734
+ missing configuration is refused by name before any devenv process starts.
2735
+
2736
+ The checkout root has no native devenv `allow --from` binding: `.envrc` owns activation and enters `tooling/direnv`
2737
+ before `use devenv`
2738
+ ([canonical activation](../../specs/cowshed/04_sandbox.md#evaluating-an-edited-devenvnix-inside-its-workspace)). Never
2739
+ pass `tooling/devenv` to `devenv --from`: it is a program, not a configuration directory. Native auto-activation
2740
+ canonicalizes that source symlink and attempts to import `<resolved-script>/devenv.nix`. If an old root binding causes
2741
+ that error, run the installed native `devenv revoke` from the checkout root to remove the binding, then enter through
2742
+ `.envrc` or invoke `tooling/devenv` directly. Do not repoint the binding or add another wrapper: a root-scoped native
2743
+ activation would also give the managed shell the wrong `DEVENV_ROOT`.
2744
+
2544
2745
  `tooling/direnv/repo-path` writes the `PATH` every managed shell entry and git hook uses. In a cowshed workspace whose
2545
2746
  `.cowshed/env` lacks `TMPDIR` or `COWSHED_RUNTIME_LINK`, a fork interrupted before its first supervisor start, it says
2546
2747
  so on stderr, runs `cowshed exec <ws> -- true` once through the installed cowshed, and continues on the file that start
2547
2748
  served. It refuses, naming the workspace and the start's exit status and error, only when that start fails or leaves the
2548
2749
  file unserved (cowshed `specs/cowshed/02_workspaces.md`, "Workspace environment").
2549
2750
 
2751
+ CI's shared `github-actions-bootstrap.sh build-shell` captures that activated shell once. It persists its complete
2752
+ `PATH` through `GITHUB_PATH` in the same search order, alongside the changed exported values in `GITHUB_ENV`; workflow
2753
+ steps do not enter a second shell or reconstruct a tool list. The combined profile is not sufficient: mbx excludes the
2754
+ profile directory containing its Cargo shim before launching real Cargo, so the shell's individual package bins must
2755
+ remain available for declared tools such as the macOS linker (`specs/cowshed/16_build_volumes.md`, "One Cargo
2756
+ environment on every path").
2757
+
2550
2758
  ### Workflow security and bounded execution
2551
2759
 
2552
2760
  Managed action references use full commit SHAs with their release tags in comments. Read-only jobs explicitly set
@@ -7,6 +7,7 @@
7
7
  "packages/nx-plugin/src/bin/smoo-nx-exec.ts": "42e699cf710b36f72565279f558076b4b08b9fdb4e02a09e851d29bd0d341029",
8
8
  "packages/nx-plugin/src/bin/smoo-nx-forbidden-spellings.ts": "f5e0e7f50a2cb60d34e7d4c95839c6b632e1b28d6b87fddb6ce437d4a5908886",
9
9
  "packages/nx-plugin/src/bin/smoo-nx-nextest-timings.ts": "706548efc89848cf90381fab2298d0b14224f0fdacc401115369dae8f0aced19",
10
+ "packages/nx-plugin/src/bin/smoo-nx-publish.ts": "b911f05d5a1a9170f49078804b7f9ae2a63468aa668501df7a3a38cdba91b07c",
10
11
  "packages/nx-plugin/src/bin/smoo-nx-test-clocks.ts": "e523ea4da694ae56c83b8601568df3a8723d9d42e56f08703389b9c8d1e2296d",
11
12
  "packages/nx-plugin/src/bin/smoo-nx-test-walks.ts": "94e8af452331d765e711aa2493efbff4ddb4e6e3088343873f78d9eaa840570b",
12
13
  "packages/nx-plugin/src/bounded-test-policy.ts": "f337c18bdbe913fcbd7dba8894737f98103214462b92d8e5986313380245bb30",
@@ -15,7 +16,7 @@
15
16
  "packages/nx-plugin/src/cargo-build-script-env.ts": "e5b45ccefc2255cd8a48121eb97132a08e136b4cbbc375d04c940d821a429b23",
16
17
  "packages/nx-plugin/src/cargo-closure-input.ts": "6f16430ec0b8949c33337353280372a7258a22d19c79ea3d3dd6bb47acb6fa0d",
17
18
  "packages/nx-plugin/src/cargo-dev-profile.ts": "34764ba4fc2aeebe75051c98c2eb64b6baeaa3d8cc0242803081ef935465368d",
18
- "packages/nx-plugin/src/cargo-retention-hook.ts": "8666d49b18227b9793d90f68bd5162d8071ed6b9f004be781852b1c74d5adbe1",
19
+ "packages/nx-plugin/src/cargo-retention-hook.ts": "5699506a32aff25be4adca91fff443bea2bfcd6fd7b2964dfa38296c50043ba1",
19
20
  "packages/nx-plugin/src/cargo-source-hash.ts": "1d72427cb2c7d9038c9452db958d14cbb5017d633f40590093654b474b71cb8e",
20
21
  "packages/nx-plugin/src/cargo-toolchain-paths.ts": "3f91da4c07394e47205093874b3d46e888c2e53ab735bbea2b64d660c2611469",
21
22
  "packages/nx-plugin/src/cargo-toolchain-policy.ts": "715a743a9922fa1f3be4301bbecee5ed5c1c00c7e9fa6eec0ce9ef9b384fad04",
@@ -27,22 +28,24 @@
27
28
  "packages/nx-plugin/src/ensure-built-witness.ts": "428b3bde289d4f10cdc2b2442a84ebc653f3da8955f9ea596dddf3c759029b1c",
28
29
  "packages/nx-plugin/src/ensure-built.ts": "cced1cdc9090c820320492c6bf40b853dd02e461651484193af89dc29173984f",
29
30
  "packages/nx-plugin/src/eslint-config-closure.ts": "0cd5a9da34df914c2d6033b7d3de49728cd71229065a2e1b43dba923001e0826",
30
- "packages/nx-plugin/src/eslint-file-set.ts": "d5d59b6ef25888e6036036b6a891273490e41b0fa2770640bf465410aca90ac8",
31
- "packages/nx-plugin/src/executors/all-verdicts/executor.ts": "e8abe81c29074b6517a6251cc1c1ee87ba126d6f0959e182a9dd46b5a977ce6d",
32
- "packages/nx-plugin/src/executors/all-verdicts/schema.ts": "9d2372b64ec77ae82b686df68a2843c11268920064909aa871edc538414ef13c",
33
- "packages/nx-plugin/src/executors/bounded-exec/bounds.ts": "bb192e95fe56659e958c200282b9248653ea350e61dcb1eb84065b6e1b746c2b",
31
+ "packages/nx-plugin/src/eslint-file-set.ts": "06d2b6c895c025bfc5269e119830f6fb2c21a6e35dd8e1484ecc8086aa13f753",
32
+ "packages/nx-plugin/src/eslint-sources.ts": "976a2b8e0520b5f6aaf397a272791817a4f385507bc0cbaad4b114fefa8decf5",
33
+ "packages/nx-plugin/src/executors/all-verdicts/executor.ts": "4d3aac65aa2e03a2d24d149c412aa18f2e66a6a36a4e88993122b10e9355c8f0",
34
+ "packages/nx-plugin/src/executors/all-verdicts/schema.ts": "2ca6bd8d2f19d851f291ab6a5227167399b9dc8ed0fda0248b69896d77e471f1",
35
+ "packages/nx-plugin/src/executors/bounded-exec/bounds.ts": "908d7146746d53f9558e7b7de08c498ec4352ecf054c1d2f67bedba9a973139b",
34
36
  "packages/nx-plugin/src/executors/bounded-exec/cpu-pool-thread.ts": "4b914385f7ab73cfb3afdc75c0e3c462e7c103c5061f7f7720d7b95f6655e32d",
35
37
  "packages/nx-plugin/src/executors/bounded-exec/cpu-pool.ts": "a4be1280a0ea4b5aa0f04170ce75ce4b813631264c50fab5cdd05d34926fc890",
36
38
  "packages/nx-plugin/src/executors/bounded-exec/disk-lease.ts": "1a3f6a6fa590d9a2550490bb6906dc91b6c05fbef235b025eaf257eb5310e92d",
37
- "packages/nx-plugin/src/executors/bounded-exec/executor.ts": "0d1284c1f3e9718a2b2ff5d7139b048cae7d9a7fe3db96d01110bf0937a7ecfc",
39
+ "packages/nx-plugin/src/executors/bounded-exec/executor.ts": "d0ab0cb5e619ccc8385c3d93931fd67927ae0c6c5eb36052d60857bbc5145fbb",
38
40
  "packages/nx-plugin/src/executors/bounded-exec/gateway-lease.ts": "f3f73bd92db30e4857f98fb8bd2b9a75b2a5a2a318f094e075ed803c1f9a0117",
39
- "packages/nx-plugin/src/executors/bounded-exec/hang-diagnostics.ts": "56a6997611b23eb5f603672e73b58f212558e5255f69b65332734516ad37fe9d",
41
+ "packages/nx-plugin/src/executors/bounded-exec/hang-diagnostics.ts": "bcaa9e52384f6c481a9cc2835ba6e8ffe167afa3cb51623fdf8dc3493876f335",
40
42
  "packages/nx-plugin/src/executors/bounded-exec/lease-wait.ts": "59d8ac94d0b8b75858971c5bb28ee421fca4f7685577274fe8bbaf0c01ba462a",
41
43
  "packages/nx-plugin/src/executors/bounded-exec/lock-wait.ts": "b14a23b49759a777f4b3338ced003adaf76837c2c38462458f76a7fef1b95d9e",
42
- "packages/nx-plugin/src/executors/bounded-exec/mbx-pool.ts": "ed35855d8c989358e78a8487b47658319d38efd52f4b1b9a3e95d74dee4002b8",
44
+ "packages/nx-plugin/src/executors/bounded-exec/mbx-pool.ts": "5b83e84eef1a0ec6c1293ba6c564654196855aef0e460cc482c141504722d359",
45
+ "packages/nx-plugin/src/executors/bounded-exec/mbx-queue.ts": "ac309e28e5ee78fa08d628edb00e33532514f7572166770799ae86d468c12b4e",
43
46
  "packages/nx-plugin/src/executors/bounded-exec/no-space.ts": "ec032968d89f9e853796012705a06c06cfc4da54bf6e6f10a526f98daca3d077",
44
47
  "packages/nx-plugin/src/executors/bounded-exec/owned-subtree.ts": "cb5edf2b5fe2c1b5b961f8c0ff16ec7bfae3c22ad75dfd671b74f1a4a865863f",
45
- "packages/nx-plugin/src/executors/bounded-exec/progress.ts": "353f415cc869fca65a75e5e89bd826292e1421ce1609002e4e47477cbb5ea6b4",
48
+ "packages/nx-plugin/src/executors/bounded-exec/progress.ts": "560a3ecd70e1cd430a0faf826092ecda1ce4cbdb99e1230a2410376ba28ac0a5",
46
49
  "packages/nx-plugin/src/executors/bounded-exec/ram-attach.ts": "865eb5c277d9ab4b258013030938aeee762b731a7298fa8ad3c5eba3026df77a",
47
50
  "packages/nx-plugin/src/executors/bounded-exec/ram-detach.ts": "535d26114d14d0d94db76227ea7ba52b1ae0b590d7dbac22993b6796d255e666",
48
51
  "packages/nx-plugin/src/executors/bounded-exec/ram-temp-fixtures.ts": "075da4ecfd1cf7dd98fc8c894599dcf2720faba07ac30b8e5592964178849359",
@@ -54,7 +57,9 @@
54
57
  "packages/nx-plugin/src/executors/bounded-exec/runner-sizing.ts": "bb8ecbc6acad99e077885ef096f61bf04fe017aa4184c34c98a578c3d3ef5a93",
55
58
  "packages/nx-plugin/src/executors/bounded-exec/runtime-pin.ts": "8e7fecaf6dd01ce6e065020f8c87edfcdc04e995934e018ab3b69b36acdc5e4f",
56
59
  "packages/nx-plugin/src/executors/bounded-exec/schema.ts": "18c2b0b6e8c5377f3cd520798da26a0fe2d04ebc35e16035af6432b85d038a2c",
57
- "packages/nx-plugin/src/executors/bounded-exec/verdict.ts": "c9b6746839602f14d92c48b9013e86d1fa4c3dd5446384146c7c22d1fd7b712c",
60
+ "packages/nx-plugin/src/executors/bounded-exec/test-result-writer.ts": "df7668a11d105a1f88d2187ef8b0edff9db7ba56d8176b5bc35daf1359667637",
61
+ "packages/nx-plugin/src/executors/bounded-exec/test-results.ts": "4f83dc3accd7892f45385796522267adad9401326d0cd9ce4d4e1145b9023577",
62
+ "packages/nx-plugin/src/executors/bounded-exec/verdict.ts": "bf68a9d464ecbeed5d2cbaba93b4f557e47b00b8eeb2c121a2096b779c93097f",
58
63
  "packages/nx-plugin/src/executors/cargo-zigbuild/executor.ts": "d20b73cc90ae1a9c3f96996cdde4d97347395ca875c4801ab67842ec89f9acd7",
59
64
  "packages/nx-plugin/src/executors/cargo-zigbuild/schema.ts": "e5cf3b0cc91a2d003a63ca0c9a93f1ec08263469b8a19dbe338b2dc0c0810747",
60
65
  "packages/nx-plugin/src/executors/clean-outputs/executor.ts": "acf82d9560451d76d9357217f5f57645135a393a6deadf8f217b57b481022c46",
@@ -77,7 +82,7 @@
77
82
  "packages/nx-plugin/src/generators/make-public/generator.ts": "2963006e663ff5b1dab37b188f96e40d8c55e0014cadf5c0c755b93c9d479a0f",
78
83
  "packages/nx-plugin/src/generators/make-public/schema.d.ts": "5e7bd2f1ce16795df4c919d6d53588ea85b574c84400940b6322275f96f60357",
79
84
  "packages/nx-plugin/src/graph-input-contract.ts": "8a1aec1294960ae80bcff55a0370c95004a911bf1afe6caa47e666da3baeac43",
80
- "packages/nx-plugin/src/index.ts": "d4535f91e1314d9f8230029ad9620d9abca15ec3740a269f851a9a028bbfa34d",
85
+ "packages/nx-plugin/src/index.ts": "9cd62f29ebedff002298f32a55b247bdd1f6b107c15ad5398358a917b51b6116",
81
86
  "packages/nx-plugin/src/managed-assets.ts": "9cea959c09f3163992e666eecc5a65ec1f1b63c81fc56c5e99088507d02c5e3b",
82
87
  "packages/nx-plugin/src/managed-files/ci-workflow.ts": "2d64d689e999af20d65cc21b4803659a835a6eb5340e8d3f896cb0c74e6a0878",
83
88
  "packages/nx-plugin/src/managed-files/context.ts": "5b83c000322382cb781df4f415f3759388e69686b76779599572a62a5c4dd28c",
@@ -95,6 +100,7 @@
95
100
  "packages/nx-plugin/src/manifest-hash.ts": "26cb2598853801cf70785386e1847feba7f04780b43809597004b7fb7ecbc2b6",
96
101
  "packages/nx-plugin/src/nextest-code-bound.ts": "e1036934a35f1b65e0f43bddbea259e01a1100e553cdeaefc2db8823a4517340",
97
102
  "packages/nx-plugin/src/nextest-timings.ts": "3d3c87e8a6e701e5e87073754257a442b9e2045665de31a9571b8c38dc8bfd0b",
103
+ "packages/nx-plugin/src/nx-publish.ts": "0e660129843e7656d8d68b4f6df967739df66aa99264f709124d5ea25c62f7a2",
98
104
  "packages/nx-plugin/src/owned-installation.ts": "6d4c0eac0c9b9fef1c27dbedd008722b702136a177b39567d623234632de5470",
99
105
  "packages/nx-plugin/src/package-target-policy.ts": "32b88c9e6ae54e2ae5492086ff7f4d1147e9f53f014a0614f48953a649bb8cc7",
100
106
  "packages/nx-plugin/src/platform-targets.ts": "a2a1aa3a7fae87931e6387275983435c7f76ce8a91808a9c47eb111bd83cad8f",
@@ -105,7 +111,7 @@
105
111
  "packages/nx-plugin/src/process-listing.ts": "70e7b75d1dda4e813d6fd43800f38ea890cd816fd9b652dfb2eae4b598ff9e46",
106
112
  "packages/nx-plugin/src/producer-receipts.ts": "7b3bc6ad60333015e35861da1d85443cc7954cd08cde8488e863aa856f120490",
107
113
  "packages/nx-plugin/src/release-config-policy.ts": "850fefcddefff6a76c596abea4d9e569f932fd3f94782b26ac6c8e29e3ac4c98",
108
- "packages/nx-plugin/src/runtime-input-policy.ts": "a16545693909fa9b8271af51f73570b392c5c99a864bfd1eae4db40775e1d53f",
114
+ "packages/nx-plugin/src/runtime-input-policy.ts": "cc6c9a3f016b72281207beea153f4abdb0ec94958caca0a33b040a2cbfaab5da",
109
115
  "packages/nx-plugin/src/runtime-input.ts": "56e748e0b7835d65efbb3be109c201bb4f10dc601a7ac5c8a8a51521501329a7",
110
116
  "packages/nx-plugin/src/rust-tokens.ts": "cbaf7552192b4f82f04518fbcc48c235b4974de5348bc3c175cabcaffffdc32b",
111
117
  "packages/nx-plugin/src/source-directories.ts": "453de3d8be798e6e69eebf7d3ed1842fb13e7d1476b6a088f032ecdfa39a2a72",
@@ -117,13 +123,13 @@
117
123
  "packages/nx-plugin/src/test-timings.ts": "ffde798346afb092d4ecf34b0a6f886fe5a8a8dfc32fee6ebc2f8592c491f2e1",
118
124
  "packages/nx-plugin/src/test-walk-policy.ts": "f1c92f1a2ba0c3282abb1706bb637d4b5dc74109edb27f7e41edc14e475bfc91",
119
125
  "packages/nx-plugin/src/testing.ts": "2f14ec40b51dd5a1314e5873708ae30c0cd3f0b5bd85042e9a38d7e68ad5a422",
120
- "packages/nx-plugin/src/tool-bins.ts": "ce90414f9fc09bc972322ea5960acf9c3b36889863a0cd31a8ceea5af3180486",
126
+ "packages/nx-plugin/src/tool-bins.ts": "8e5b194d76ce854fd33ad464017c021af401a2d92383f5c31168652b73656601",
121
127
  "packages/nx-plugin/src/type-guards.ts": "87d87a9bb83f0f4614b9f615d8cc7347772cb1418dc1946978987147c0d6ef0c",
122
128
  "packages/nx-plugin/src/typecheck-test-policy.ts": "5f6b1ff0dbf4bcac84721e60452790fb5e4ce41ee35ca2f1d033d51575ed53d7",
123
129
  "packages/nx-plugin/src/version-actions.cts": "cd77da78b1a80171104c3db0bea586e513f0ce0d66c80f9a38a73533de2a1bbe",
124
130
  "packages/nx-plugin/src/wait-why-policy.ts": "f10a5370665c0c38dc778d7532b2cd2b008221efea097b788aeaba8ee63745ea",
125
131
  "packages/nx-plugin/src/workspace-config-policy.ts": "410debddb0280489f54ab8173fa11890334e19efba69c19d85b92981d2d40688",
126
- "packages/nx-plugin/src/workspace-index.ts": "ba806bf1ab701831868e52efd2e284fb7a4929099b6b8c99e2008e7eae171690",
132
+ "packages/nx-plugin/src/workspace-index.ts": "b2036b48bae92d618027bcc1f876eb9312627ed035d4753eead70b23aa482cc5",
127
133
  "packages/nx-plugin/src/workspace-manifest.ts": "3dd8da8dd96f6005282df18d13c15ea4a2d9db78c2bd472cddb3ee18b6ffc50c",
128
134
  "packages/nx-plugin/src/workspace-package-policy.ts": "f569ce4e5d27168ea83aa41893573cb869d6f062d37133e95911fdd1d709fa8c",
129
135
  "packages/nx-plugin/tsconfig.lib.json": "553a96cc72e10c187d5e7d3da767270d8184ae07929139e417345c770b8d84d1"
@@ -0,0 +1,3 @@
1
+ #!/usr/bin/env node
2
+ export {};
3
+ //# sourceMappingURL=smoo-nx-publish.d.ts.map
@@ -0,0 +1 @@
1
+ {"version":3,"file":"smoo-nx-publish.d.ts","sourceRoot":"","sources":["../../src/bin/smoo-nx-publish.ts"],"names":[],"mappings":""}
@@ -0,0 +1,3 @@
1
+ #!/usr/bin/env node
2
+ import { runNxPublish } from '../nx-publish.js';
3
+ process.exitCode = await runNxPublish(process.argv.slice(2));