@vibe-agent-toolkit/cli 0.2.0-rc.4 → 0.2.0-rc.6

package/dist/utils/vat-bin-path.js

@@ -0,0 +1,49 @@
+/**
+ * Where the built vat CLI entry is, for the commands that re-invoke it as a
+ * child process.
+ *
+ * ## 🪤 `dist/bin.js`, deliberately NOT `dist/bin/vat.js`
+ *
+ * `packages/lab/src/harness/instrument.ts` documents `dist/bin/vat.js` as a
+ * re-resolving WRAPPER: it looks the CLI up again at run time, so spawning it
+ * can execute a different build than the one the caller is running from. A
+ * supervisor that thinks it is bounding its own code, and a corpus runner that
+ * thinks it is auditing with its own validators, both need the entry point that
+ * cannot be redirected.
+ *
+ * ## Why the two branches
+ *
+ * `node` cannot execute `.ts`, so a caller running from SOURCE under vitest
+ * still has to reach the COMPILED entry — which is why the source-tree branch
+ * walks across to `packages/cli/dist/bin.js` rather than to a sibling. A build
+ * is therefore a precondition for every test that spawns the CLI, and a system
+ * test that skipped it would prove things about a stale `dist`.
+ *
+ * 🪤 Shared rather than copied. This resolution lived inline in
+ * `commands/corpus/runner.ts` and a second caller wanted it; a second copy is a
+ * duplication-gate failure under this repo's zero-tolerance policy, and — worse
+ * — two copies drift, so one caller would keep spawning the wrapper long after
+ * the other stopped. The `__dirname`-relative hops below are correct for THIS
+ * module's location and nothing else, which is precisely why it is not a snippet
+ * to paste.
+ */
+import { existsSync } from 'node:fs';
+import { dirname } from 'node:path';
+import { fileURLToPath } from 'node:url';
+import { safePath } from '@vibe-agent-toolkit/utils';
+const HERE = dirname(fileURLToPath(import.meta.url));
+/**
+ * Resolve the path to the built vat CLI entry.
+ *
+ * @returns An absolute path to `dist/bin.js`
+ */
+export function resolveVatBinPath() {
+    // Compiled tree: packages/cli/dist/utils/vat-bin-path.js → packages/cli/dist/bin.js
+    const compiled = safePath.resolve(HERE, '../bin.js');
+    // eslint-disable-next-line security/detect-non-literal-fs-filename -- internal path
+    if (existsSync(compiled))
+        return compiled;
+    // Source tree (vitest): packages/cli/src/utils/vat-bin-path.ts → packages/cli/dist/bin.js
+    return safePath.resolve(HERE, '../../dist/bin.js');
+}
+//# sourceMappingURL=vat-bin-path.js.map

package/dist/utils/vat-bin-path.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"vat-bin-path.js","sourceRoot":"","sources":["../../src/utils/vat-bin-path.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG;AAEH,OAAO,EAAE,UAAU,EAAE,MAAM,SAAS,CAAC;AACrC,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AACpC,OAAO,EAAE,aAAa,EAAE,MAAM,UAAU,CAAC;AAEzC,OAAO,EAAE,QAAQ,EAAE,MAAM,2BAA2B,CAAC;AAErD,MAAM,IAAI,GAAG,OAAO,CAAC,aAAa,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC;AAErD;;;;GAIG;AACH,MAAM,UAAU,iBAAiB;IAC/B,oFAAoF;IACpF,MAAM,QAAQ,GAAG,QAAQ,CAAC,OAAO,CAAC,IAAI,EAAE,WAAW,CAAC,CAAC;IACrD,oFAAoF;IACpF,IAAI,UAAU,CAAC,QAAQ,CAAC;QAAE,OAAO,QAAQ,CAAC;IAC1C,0FAA0F;IAC1F,OAAO,QAAQ,CAAC,OAAO,CAAC,IAAI,EAAE,mBAAmB,CAAC,CAAC;AACrD,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vibe-agent-toolkit/cli",
-  "version": "0.2.0-rc.4",
+  "version": "0.2.0-rc.6",
   "description": "Command-line interface for vibe-agent-toolkit",
   "type": "module",
   "bin": {
@@ -46,14 +46,15 @@
   "//dependencies-note": "DO NOT add example agent packages or adopter packages here. Adopter packages (like vat-development-agents) depend on the CLI binary at build time — declaring them as deps creates a circular build dependency. They are built in a second turbo pass via package#task overrides in turbo.json.",
   "dependencies": {
     "@anthropic-ai/sdk": "^0.71.2",
-    "@vibe-agent-toolkit/agent-config": "0.2.0-rc.4",
-    "@vibe-agent-toolkit/schema": "0.2.0-rc.4",
-    "@vibe-agent-toolkit/agent-skills": "0.2.0-rc.4",
-    "@vibe-agent-toolkit/claude-marketplace": "0.2.0-rc.4",
-    "@vibe-agent-toolkit/discovery": "0.2.0-rc.4",
-    "@vibe-agent-toolkit/gateway-mcp": "0.2.0-rc.4",
-    "@vibe-agent-toolkit/resources": "0.2.0-rc.4",
-    "@vibe-agent-toolkit/utils": "0.2.0-rc.4",
+    "@vibe-agent-toolkit/agent-config": "0.2.0-rc.6",
+    "@vibe-agent-toolkit/agent-skills": "0.2.0-rc.6",
+    "@vibe-agent-toolkit/claude-marketplace": "0.2.0-rc.6",
+    "@vibe-agent-toolkit/discovery": "0.2.0-rc.6",
+    "@vibe-agent-toolkit/gateway-mcp": "0.2.0-rc.6",
+    "@vibe-agent-toolkit/projection-sqlite": "0.2.0-rc.6",
+    "@vibe-agent-toolkit/resources": "0.2.0-rc.6",
+    "@vibe-agent-toolkit/schema": "0.2.0-rc.6",
+    "@vibe-agent-toolkit/utils": "0.2.0-rc.6",
     "adm-zip": "^0.6.0",
     "commander": "^12.1.0",
     "picomatch": "^4.0.3",
@@ -68,7 +69,9 @@
     "@types/picomatch": "^4.0.2",
     "@types/semver": "^7.7.1",
     "@types/tar": "^6.1.13",
-    "@vibe-agent-toolkit/dev-tools": "0.2.0-rc.4",
+    "@vibe-agent-toolkit/dev-tools": "0.2.0-rc.6",
+    "@vibe-agent-toolkit/rag": "0.2.0-rc.6",
+    "@vibe-agent-toolkit/rag-lancedb": "0.2.0-rc.6",
     "rimraf": "^6.0.1",
     "typescript": "^5.7.3",
     "vitest": "^3.2.4"
@@ -80,9 +83,17 @@
     "type": "git",
     "url": "https://github.com/jdutton/vibe-agent-toolkit.git"
   },
-  "optionalDependencies": {
-    "@vibe-agent-toolkit/projection-sqlite": "0.2.0-rc.4",
-    "@vibe-agent-toolkit/rag": "0.2.0-rc.4",
-    "@vibe-agent-toolkit/rag-lancedb": "0.2.0-rc.4"
+  "//peerDependencies-note": "The RAG backends are OPTIONAL PEERS, never optionalDependencies. `optionalDependencies` are INSTALLED BY DEFAULT by npm and pnpm alike - 'optional' there means the install may fail without failing the build, not that it is skipped - so declaring them that way shipped ~240 MB (onnxruntime-web 136 MB, a LanceDB platform binary 93 MB, a third apache-arrow, protobufjs) to every adopter, contradicting the seam in src/utils/optional-backend.ts that exists precisely to keep them out. Optional peers are NOT auto-installed, so the manifest now says what that module already says: these ship separately, and an absent one is a legible error naming the package to install. projection-sqlite is deliberately NOT in this group: it has zero third-party dependencies (only node:sqlite, which is built into Node) and a 152 KB dist, so the platform-binary argument that justifies the seam is simply false for it. It is also what `vat resources query` builds its ephemeral in-memory store from, and a query surface that works only where a backend was separately installed is the capability gate the projection design forbids.",
+  "peerDependencies": {
+    "@vibe-agent-toolkit/rag": "0.2.0-rc.6",
+    "@vibe-agent-toolkit/rag-lancedb": "0.2.0-rc.6"
+  },
+  "peerDependenciesMeta": {
+    "@vibe-agent-toolkit/rag": {
+      "optional": true
+    },
+    "@vibe-agent-toolkit/rag-lancedb": {
+      "optional": true
+    }
   }
 }