create-mono-agent 0.6.2 → 0.9.0

package/README.md

@@ -10,6 +10,12 @@ Three equivalent entry points, one behaviour:
 - `npx create-mono-agent` — the same, spelled explicitly.
 - `npm i -g create-mono-agent` — a global install that puts the natural `mono-agent` command on your `PATH`.
 
+On macOS, a one-off `npm create`/npx wizard may start the finished agent in the
+background. Before it does, `@mono-agent/agent-app` copies the exact executing
+package through npm into a private, verified runtime under
+`~/.mono-agent/runtimes/agent-app/`; launchd never keeps a disposable npm-cache
+path. This does not install a global command or mutate `PATH`.
+
 The bare `mono-agent` npm name is unavailable — npm rejects it as too similar to
 an unrelated `monoagent` package — so this installer follows the `create-*`
 convention while still exposing the ergonomic `mono-agent` bin.

package/dist/resolve-agent-app-cli.d.ts

@@ -6,8 +6,8 @@
  * means this survives any install layout — npm/npx global, pnpm-linked — and any
  * future change to agent-app's bin location. We resolve it through CJS
  * `require.resolve` of `@mono-agent/agent-app/package.json` (which agent-app
- * exports), so this works on every Node ≥20 without depending on the newer
- * synchronous `import.meta.resolve` (Node 20.6+).
+ * exports), so this works throughout the supported Node range without depending on
+ * synchronous `import.meta.resolve` (available throughout the supported Node 22.19.0+ range).
  */
 export declare function resolveAgentAppCliEntry(from?: string | URL): string;
 //# sourceMappingURL=resolve-agent-app-cli.d.ts.map

package/dist/resolve-agent-app-cli.js

@@ -8,8 +8,8 @@ import { dirname, resolve } from "node:path";
  * means this survives any install layout — npm/npx global, pnpm-linked — and any
  * future change to agent-app's bin location. We resolve it through CJS
  * `require.resolve` of `@mono-agent/agent-app/package.json` (which agent-app
- * exports), so this works on every Node ≥20 without depending on the newer
- * synchronous `import.meta.resolve` (Node 20.6+).
+ * exports), so this works throughout the supported Node range without depending on
+ * synchronous `import.meta.resolve` (available throughout the supported Node 22.19.0+ range).
  */
 export function resolveAgentAppCliEntry(from = import.meta.url) {
     const require = createRequire(from);

package/package.json

@@ -1,10 +1,13 @@
 {
   "name": "create-mono-agent",
-  "version": "0.6.2",
+  "version": "0.9.0",
   "description": "npm-init style installer for the mono-agent CLI: `npm create mono-agent`. Ships both a `create-mono-agent` and a `mono-agent` bin, each delegating to the @mono-agent/agent-app CLI.",
   "type": "module",
   "license": "UNLICENSED",
   "private": false,
+  "engines": {
+    "node": ">=22.19.0"
+  },
   "bin": {
     "create-mono-agent": "./dist/bin/mono-agent.js",
     "mono-agent": "./dist/bin/mono-agent.js"
@@ -14,7 +17,7 @@
     "README.md"
   ],
   "dependencies": {
-    "@mono-agent/agent-app": "0.6.2"
+    "@mono-agent/agent-app": "0.9.0"
   },
   "publishConfig": {
     "access": "public"