Skip to content

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

test(cli): the registry merge test names its source input first

Corey Olsonc83ca04dc555
diff --git a/test/cli-help.test.js b/test/cli-help.test.js
index 4260e50f..81d0f6de 100644
--- a/test/cli-help.test.js
+++ b/test/cli-help.test.js
@@ -1,5 +1,5 @@
/** @pullboard-test-input source-tree */
-/** @pullboard-test-loads src/cli.js */
+/** @pullboard-test-loads src/cli.js src/commands/*.js */
/** The layered CLI help stays short, command-specific, and in parity with its declaration [N37,I1]. */
import assert from 'node:assert/strict';
import { chmodSync, mkdirSync, mkdtempSync, readdirSync, readFileSync, rmSync, writeFileSync } from 'node:fs';
diff --git a/test/registry-merge.test.js b/test/registry-merge.test.js
index f0175b94..6da15a7d 100644
--- a/test/registry-merge.test.js
+++ b/test/registry-merge.test.js
@@ -1,4 +1,5 @@
/** @pullboard-test-input source-tree */
+/** @pullboard-test-loads src/machine.js */
/** Two items adding different commands, or different engines, merge without conflict even at the same sorted spot [C7,V4]. */
import assert from 'node:assert/strict';
import { cpSync, mkdirSync, mkdtempSync, readFileSync, readdirSync, rmSync, writeFileSync } from 'node:fs';