openmates 0.11.0-alpha.32 → 0.11.0-alpha.33

package/dist/{chunk-NI7XPZBV.js → chunk-HHYM6RA6.js}

@@ -5254,6 +5254,9 @@ function printLogo() {
 
 // src/cli.ts
 import { createInterface as createInterface3 } from "readline/promises";
+import { realpathSync } from "fs";
+import { fileURLToPath } from "url";
+import { basename as basename3, dirname } from "path";
 import WebSocket2 from "ws";
 
 // ../secret-scanner/src/registry.ts
@@ -31042,7 +31045,7 @@ Taking control of a small, self-directed project is often the best antidote to t
         text: "Use my saved coding setup memory to suggest how I should structure a debugging session tonight."
       },
       message_2: {
-        text: 'Based on your [coding setup preferences](/#settings/app_store/code/settings_memories/coding_setup) for a keyboard-first, **terminal-based** workflow with **low AI intervention**, here is a structured approach for your debugging session tonight. \n\nSince you prefer **explicit commands** and **small diffs** you can review manually, this workflow focuses on local isolation and CLI-native tools.\n\n### 1. State Isolation & Clean Slate\nBefore changing any code, ensure you are working in a clean environment to make those "small diffs" meaningful.\n*   **Create a dedicated branch:** `git checkout -b debug/session-name`\n*   **Clear artifacts:** Run your project\'s clean command (e.g., `make clean`, `npm cache clean`, or `cargo clean`) to ensure you aren\'t chasing ghosts in compiled binaries.\n\n### 2. The "Single-Command" Reproduction\nIn line with your shell-first preference, your first goal is to reduce the bug to a single [shell](wiki:Shell_(computing)) command or a minimal script.\n*   **Draft a reproduction script:** Create a `repro.sh` that sets up the environment and triggers the failure.\n*   **Automate the test:** Use `watch` or a simple loop to run this command as you make changes:\n    ```json\n{"type": "code", "embed_id": "2ff43224-0546-4f2f-ba70-3b305c2ed9f8"}\n```\n\n\n\n### 3. Explicit Trace & Observation\nSince you prefer a **low AI level**, rely on explicit [debugging](wiki:Debugging) and tracing tools rather than speculative fixes:\n*   **CLI Debuggers:** Use `gdb`, `lldb`, `pdb`, or `node inspect` depending on your language.\n*   **System Tracing:** If the bug involves file I/O or networking, use `strace` (Linux) or `dtrace` (macOS) to see exactly what the process is doing at the kernel level.\n*   **Grep-driven search:** Use `rg` (ripgrep) to explicitly trace data flow through your codebase from the terminal.\n\n### 4. Incremental Patching & Diff Review\nTo honor your preference for **small, reviewable diffs**:\n*   **Atomic Changes:** Make exactly one change at a time.\n*   **Review before Commit:** Use `git diff --color-words` to see exactly what changed in the terminal.\n*   **The "Check-in" Loop:**\n    1.  Modify code in your [text editor](wiki:Text_editor) (likely Vim/Emacs/Nano given your keyboard-first preference).\n    2.  Run `./repro.sh`.\n    3.  If successful, commit the focused change. If it fails, inspect `git diff`, revert only the specific hunks you decide to abandon, and try a different hypothesis.\n\n### 5. Final Verification\nOnce the bug is squashed, convert your `repro.sh` into a permanent [unit test](wiki:Unit_testing) to prevent [regression](wiki:Software_regression).\n\n***\n\nTo help me give you more specific commands or tool suggestions, tell me what kind of issue you are tackling tonight: logic error, crash, environment/dependency issue, or performance bottleneck.\n\n```json\n{"type": "code", "embed_id": "7d40d5c4-1ee4-4aec-ba2a-d55734f769bc"}\n```'
+        text: 'Based on your [coding setup preferences](/#settings/app_store/code/settings_memories/coding_setup) for a keyboard-first, **terminal-based** workflow with **low AI intervention**, here is a structured approach for your debugging session tonight. \n\nSince you prefer **explicit commands** and **small diffs** you can review manually, this workflow focuses on local isolation and CLI-native tools.\n\n### 1. State Isolation & Clean Slate\nBefore changing any code, ensure you are working in a clean environment to make those "small diffs" meaningful.\n*   **Create a dedicated branch:** `git checkout -b debug/session-name`\n*   **Clear artifacts:** Run your project\'s clean command (e.g., `make clean`, `npm cache clean`, or `cargo clean`) to ensure you aren\'t chasing ghosts in compiled binaries.\n\n### 2. The "Single-Command" Reproduction\nIn line with your shell-first preference, your first goal is to reduce the bug to a single [shell](wiki:Shell_(computing)) command or a minimal script.\n*   **Draft a reproduction script:** Create a `repro.sh` that sets up the environment and triggers the failure.\n*   **Automate the test:** Use `watch` or a simple loop to run this command as you make changes:\n    ```json\n{"type": "code", "embed_id": "2ff43224-0546-4f2f-ba70-3b305c2ed9f8"}\n```\n\n\n\n### 3. Explicit Trace & Observation\nSince you prefer a **low AI level**, rely on explicit [debugging](wiki:Debugging) and tracing tools rather than speculative fixes:\n*   **CLI Debuggers:** Use `gdb`, `lldb`, `pdb`, or `node inspect` depending on your language.\n*   **System Tracing:** If the bug involves file I/O or networking, use `strace` (Linux) or `dtrace` (macOS) to see exactly what the process is doing at the kernel level.\n*   **Grep-driven search:** Use `rg` (ripgrep) to explicitly trace data flow through your codebase from the terminal.\n\n### 4. Incremental Patching & Diff Review\nTo honor your preference for **small, reviewable diffs**:\n*   **Atomic Changes:** Make exactly one change at a time.\n*   **Review before Commit:** Use `git diff --color-words` to see exactly what changed in the terminal.\n*   **The "Check-in" Loop:**\n    1.  Modify code in your [text editor](wiki:Text_editor) (likely Vim/Emacs/Nano given your keyboard-first preference).\n    2.  Run `./repro.sh`.\n    3.  If successful, commit the focused change. If it fails, inspect `git diff`, revert only the specific hunks you decide to abandon, and try a different hypothesis.\n\n### 5. Final Verification\nOnce the bug is squashed, convert your `repro.sh` into a permanent [unit test](wiki:Unit_testing) to prevent [regression](wiki:Software_regression).\n\n***\n\nTo help me give you more specific commands or tool suggestions, tell me what kind of issue you are tackling tonight: logic error, crash, environment/dependency issue, or performance bottleneck.'
       }
     },
     memory_code_preferred_tech: {
@@ -42632,11 +42635,11 @@ function parseYamlScalar(value) {
 }
 async function saveDownloadedDocument(document, output) {
   const { mkdir, writeFile } = await import("fs/promises");
-  const { join: join4, basename: basename3, dirname } = await import("path");
+  const { join: join4, basename: basename4, dirname: dirname2 } = await import("path");
   const target = typeof output === "string" ? output : ".";
-  const filename = basename3(document.filename || "document.pdf");
+  const filename = basename4(document.filename || "document.pdf");
   const filePath = target.endsWith(".pdf") ? target : join4(target, filename);
-  await mkdir(dirname(filePath), { recursive: true });
+  await mkdir(dirname2(filePath), { recursive: true });
   await writeFile(filePath, document.data);
   return filePath;
 }
@@ -42715,7 +42718,7 @@ async function promptSecret(question) {
 }
 async function writeSecretFile(filePath, content, force = false) {
   const { mkdir, writeFile, stat: stat2 } = await import("fs/promises");
-  const { dirname } = await import("path");
+  const { dirname: dirname2 } = await import("path");
   try {
     await stat2(filePath);
     if (!force) throw new Error(`${filePath} already exists. Use --force to overwrite.`);
@@ -42725,7 +42728,7 @@ async function writeSecretFile(filePath, content, force = false) {
     }
     if (error instanceof Error && !("code" in error)) throw error;
   }
-  await mkdir(dirname(filePath), { recursive: true });
+  await mkdir(dirname2(filePath), { recursive: true });
   await writeFile(filePath, content, { mode: 384 });
   return filePath;
 }
@@ -45487,7 +45490,7 @@ async function handleDocs(client, subcommand, rest, flags) {
   }
   if (subcommand === "download") {
     const { writeFile, mkdir } = await import("fs/promises");
-    const { join: join4, dirname } = await import("path");
+    const { join: join4, dirname: dirname2 } = await import("path");
     if (flags.all === true) {
       const outputDir = typeof flags.output === "string" ? flags.output : "./openmates-docs";
       const tree = await client.listDocs();
@@ -45497,7 +45500,7 @@ async function handleDocs(client, subcommand, rest, flags) {
       for (const slug2 of slugs) {
         const content2 = await client.getDoc(slug2);
         const filePath = join4(outputDir, `${slug2}.md`);
-        await mkdir(dirname(filePath), { recursive: true });
+        await mkdir(dirname2(filePath), { recursive: true });
         await writeFile(filePath, content2, "utf-8");
         count++;
         process.stderr.write(`\r  Downloaded ${count}/${slugs.length}`);
@@ -45564,11 +45567,24 @@ Examples:
   openmates docs download architecture/core/security
   openmates docs download --all --output ./docs`);
 }
-main().catch((error) => {
-  const message = error instanceof Error ? error.message : String(error);
-  console.error(`Error: ${message}`);
-  process.exit(1);
-});
+function isCliEntrypoint() {
+  const entrypoint = process.argv[1];
+  if (!entrypoint) return false;
+  try {
+    const invokedPath = realpathSync(entrypoint);
+    const modulePath = realpathSync(fileURLToPath(import.meta.url));
+    return invokedPath === modulePath || basename3(invokedPath) === "cli.js" && dirname(invokedPath) === dirname(modulePath);
+  } catch {
+    return false;
+  }
+}
+if (isCliEntrypoint()) {
+  main().catch((error) => {
+    const message = error instanceof Error ? error.message : String(error);
+    console.error(`Error: ${message}`);
+    process.exit(1);
+  });
+}
 
 export {
   MEMORY_TYPE_REGISTRY,

package/dist/cli.js

@@ -2,7 +2,7 @@
 import {
   getExtForLang,
   serializeToYaml
-} from "./chunk-NI7XPZBV.js";
+} from "./chunk-HHYM6RA6.js";
 import "./chunk-AXNRPVLE.js";
 export {
   getExtForLang,

package/dist/index.js

@@ -7,7 +7,7 @@ import {
   getExtForLang,
   parseNewChatSuggestionText,
   serializeToYaml
-} from "./chunk-NI7XPZBV.js";
+} from "./chunk-HHYM6RA6.js";
 import "./chunk-AXNRPVLE.js";
 export {
   MATE_NAMES,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "openmates",
-  "version": "0.11.0-alpha.32",
+  "version": "0.11.0-alpha.33",
   "description": "OpenMates CLI and SDK",
   "type": "module",
   "main": "dist/index.js",