create-loopengine 0.1.30 → 0.1.32

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-loopengine",
-  "version": "0.1.30",
+  "version": "0.1.32",
   "description": "Scaffold a new loopengine agent project — a runnable HTTP server with one example agent, in your own repo.",
   "license": "MIT",
   "type": "module",

package/template/adapters/http.ts

@@ -920,8 +920,8 @@ function handleSkillDelete(res: ServerResponse, agentName: string, skillId: stri
   res.writeHead(200, { 'content-type': 'application/json' }).end(JSON.stringify({ ok: true }))
 }
 
-// Backs the Admin UI's "Environment" section — every env var a package
-// (see loopengine's own PACKAGES.md, bin/package-manager.ts) declared it
+// Backs the Admin UI's "Environment" section — every env var an ability
+// (see loopengine's own ABILITIES.md, bin/ability-manager.ts) declared it
 // needs for this agent, with set/not-set status only. Read-only, so no
 // extra auth gate beyond the normal Basic Auth middleware every admin
 // route already has.
@@ -938,7 +938,7 @@ function handleEnvGet(res: ServerResponse, agentName: string): void {
 // credential), so unlike every other route here, this one refuses
 // outright when LOOPENGINE_ADMIN_AUTH isn't set at all, rather than just
 // warning at startup and proceeding open like the rest of this file does
-// (see loopengine's own PACKAGES.md, "Managing package secrets in the
+// (see loopengine's own ABILITIES.md, "Managing ability secrets in the
 // Admin UI" — LOOPENGINE_ADMIN_AUTH being optional today is an
 // acceptable gap for config, not for secrets).
 async function handleEnvPut(req: IncomingMessage, res: ServerResponse, agentName: string, varName: string): Promise<void> {

package/template/package.json

@@ -9,7 +9,7 @@
     "cli": "tsx adapters/cli.ts"
   },
   "dependencies": {
-    "loopengine": "^0.1.22",
+    "loopengine": "^0.1.23",
     "actauth": "^0.0.12"
   },
   "devDependencies": {