@todoforai/cli 0.1.26 → 0.1.27

package/dist/todoai.js

@@ -43180,7 +43180,7 @@ import { parseArgs } from "util";
 // package.json
 var package_default = {
   name: "@todoforai/cli",
-  version: "0.1.24",
+  version: "0.1.27",
   type: "module",
   bin: {
     "todoforai-cli": "bin/todoforai-cli.js",
@@ -43194,8 +43194,7 @@ var package_default = {
     build: "bun build src/index.ts --target=bun --outfile dist/todoai.js --external ws",
     prepublishOnly: "bun run build",
     start: "bun run src/index.ts",
-    dev: "bun run src/index.ts",
-    postinstall: "rm -rf node_modules/@todoforai/edge && ln -s ../../../edge/bun node_modules/@todoforai/edge"
+    dev: "bun run src/index.ts"
   },
   dependencies: {
     "@shared/credentials": "file:../packages/shared-credentials",
@@ -43205,7 +43204,7 @@ var package_default = {
     ws: "^8.18.0"
   },
   peerDependencies: {
-    "@todoforai/edge": "file:../edge/bun"
+    "@todoforai/edge": ">=0.12.0"
   },
   peerDependenciesMeta: {
     "@todoforai/edge": {
@@ -43214,7 +43213,6 @@ var package_default = {
   },
   devDependencies: {
     "@types/ws": "^8.5.13",
-    "@todoforai/edge": "file:../edge/bun",
     typescript: "^5.7.0"
   }
 };
@@ -43927,10 +43925,9 @@ When the user asks you to recommend how to grow (e.g. "recommend growth TODOs",
 Recommending actionable TODOs from your recommendations:
 To materialize growth recommendations, create recommendation cards in the project's Recommendations column. You NEVER create running todos \u2014 you only recommend templates by reference. Two tools, strict roles:
 
-1. GET A TEMPLATE (todoregistry-cli) \u2014 generate-first, reuse only on a close fit:
-   - Default: CREATE a template tailored to THIS business, right there (auth is inherited from your shell):
-     \`todoregistry-cli create --name "<name>" --description "<one line>" --body @<prompt-file>\` (or \`--body -\` for stdin). It prints the new template id on stdout.
-   - Before creating, you MAY \`todoregistry-cli search <query>\` / \`list -c <category>\` / \`get <id>\`; reuse an existing template ONLY when it already fits this business closely with no meaningful edits. If it needs tailoring, create a new one instead \u2014 do not recommend a generic playbook that ignores this company's specifics.
+1. GET A TEMPLATE (api_create_template) \u2014 generate-first, reuse only on a close fit:
+   - Default: CREATE a template tailored to THIS business with the \`api_create_template\` tool. It returns the new template id.
+   - Reuse an existing registry template ONLY when it already fits this business closely with no meaningful edits \u2014 pass its id straight to \`api_recommend_template\`. If it needs tailoring, create a new one instead \u2014 do not recommend a generic playbook that ignores this company's specifics.
 
    Write every generated body to be unmistakably about THIS company \u2014 bake the specifics from the business context into the task itself: the company name, its actual competitors, the target segment, the specific channel/platform, and the concrete metric to move. A reader should never mistake it for a generic template.
 
@@ -43939,9 +43936,10 @@ To materialize growth recommendations, create recommendation cards in the projec
    - Then the request, using these exact standalone heading lines (letters only, each on its own line, ending with a colon): \`Your task:\`, \`Steps:\`, \`Data needed:\`. Everything under these headings becomes the first user turn.
    - Headings must match exactly (e.g. \`Your task:\`, not \`Your task (SEO):\`) or the split breaks. Put the business-specific detail in the body text under each heading, never in the heading itself.
 
-2. RECOMMEND (todoforai-cli \u2014 references a template id onto the project; never creates a running todo):
-   \`todoforai-cli recommend --template <id> --project <projectId> --business-context <businessContextId> --note "<why>" --priority high|medium|low\`
-   Take <projectId> and <businessContextId> from your current session context and pass them explicitly. Put the one-line WHY for THIS business in --note (the card's tooltip). The card appears in the Recommendations column for the user to review before any credits are spent.
+2. RECOMMEND (api_recommend_template \u2014 references a template id onto the project; never creates a running todo):
+   Call \`api_recommend_template\` with the template id, a one-line \`note\` (the WHY for THIS business \u2014 it becomes the card's tooltip) and a \`priority\` of high, medium or low. Project and business context default to the current session, so pass them only when targeting a different one. The card appears in the Recommendations column for the user to review before any credits are spent.
+
+   Both tools run in-process and need no machine or shell \u2014 never shell out to \`todoregistry-cli\` / \`todoforai-cli\` for this.
 
 3. Recommend 3-6 cards (highest priority first). Then reply with a one-line summary per card and tell the user they're waiting in the Recommendations column for review.`,
   mcpConfigs: {},
@@ -43953,8 +43951,6 @@ To materialize growth recommendations, create recommendation cards in the projec
       "cloud:google_rag",
       "builtin:todoforai_api",
       "builtin:question",
-      "cloud:BASH(cmd: todoregistry-cli *)",
-      "cloud:BASH(cmd: todoforai-cli *)",
       "cloud:BASH(cmd: curl *)"
     ],
     ask: [],

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@todoforai/cli",
-  "version": "0.1.26",
+  "version": "0.1.27",
   "type": "module",
   "bin": {
     "todoforai-cli": "bin/todoforai-cli.js",