agents-inc 0.147.0

package/README.md

@@ -0,0 +1,24 @@
+# agents-inc
+
+Alias for [`@agents-inc/cli`](https://www.npmjs.com/package/@agents-inc/cli) so the short form works:
+
+```sh
+npx agents-inc init
+```
+
+Installing this package pulls in the real CLI; this package only forwards to it.
+The command this alias installs is `agents-inc`; the main package installs `agentsinc`.
+
+## Versioning
+
+This package is published **in lockstep with `@agents-inc/cli`, at the same version number**,
+even though its own three lines never change.
+
+That is not cosmetic. `npx` caches by package spec: it resolves `agents-inc` to the latest
+version, and if that version is already cached it reuses the whole cached install — including
+the `@agents-inc/cli` it resolved on first run. An alias whose version never moved would leave
+repeat `npx agents-inc` users pinned to whatever CLI version they happened to pull first, no
+matter how many releases followed. Bumping in lockstep is what busts that cache.
+
+So: **every `@agents-inc/cli` release must republish this package at the matching version.**
+It is step 8 of the release checklist in `.ai-docs/standards/commit-protocol.md`.

package/bin/run.js

@@ -0,0 +1,3 @@
+#!/usr/bin/env node
+// The CLI's entrypoint starts oclif at import time, so delegating is a bare import.
+import "@agents-inc/cli";

package/package.json

@@ -0,0 +1,26 @@
+{
+  "name": "agents-inc",
+  "version": "0.147.0",
+  "description": "Runs the Agents Inc. CLI — alias for @agents-inc/cli so `npx agents-inc init` works",
+  "type": "module",
+  "bin": {
+    "agents-inc": "./bin/run.js"
+  },
+  "files": [
+    "bin/"
+  ],
+  "dependencies": {
+    "@agents-inc/cli": "*"
+  },
+  "engines": {
+    "node": ">=18.0.0"
+  },
+  "license": "MIT",
+  "author": "Vincent Bollaert",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/agents-inc/cli.git",
+    "directory": "alias"
+  },
+  "homepage": "https://github.com/agents-inc/cli#readme"
+}