@iaforged/context-code 1.2.12 → 1.3.6

package/dist/src/utils/ndjsonSafeStringify.js

@@ -0,0 +1,10 @@
+import { jsonStringify } from './slowOperations.js';
+// JSON.stringify emits U+2028/U+2029 raw. In NDJSON transports, receivers
+// that split with JS line terminator rules may split a message mid-string.
+const JS_LINE_TERMINATORS = /\u2028|\u2029/g;
+function escapeJsLineTerminators(json) {
+    return json.replace(JS_LINE_TERMINATORS, c => c === '\u2028' ? '\\u2028' : '\\u2029');
+}
+export function ndjsonSafeStringify(value) {
+    return escapeJsLineTerminators(jsonStringify(value));
+}

package/dist/src/utils/permissions/permissionExplainer.js

@@ -117,12 +117,12 @@ export async function generatePermissionExplanation({ toolName, toolInput, toolD
         const conversationContext = messages?.length
             ? extractConversationContext(messages)
             : '';
-        const userPrompt = `Tool: ${toolName}
-${toolDescription ? `Description: ${toolDescription}\n` : ''}
-Input:
-${formattedInput}
-${conversationContext ? `\nRecent conversation context:\n${conversationContext}` : ''}
-
+        const userPrompt = `Tool: ${toolName}
+${toolDescription ? `Description: ${toolDescription}\n` : ''}
+Input:
+${formattedInput}
+${conversationContext ? `\nRecent conversation context:\n${conversationContext}` : ''}
+
 Explain this command in context.`;
         const model = getMainLoopModel();
         // Use sideQuery with forced tool choice for guaranteed structured output

package/dist/src/utils/secureStorage/sqliteStorage.js

@@ -78,10 +78,10 @@ function decryptPayload(payload) {
     return decrypted.toString('utf8');
 }
 function savePayload(db, plainText) {
-    db.prepare(`
-    INSERT INTO secure_storage (key, value)
-    VALUES (?, ?)
-    ON CONFLICT(key) DO UPDATE SET value = excluded.value
+    db.prepare(`
+    INSERT INTO secure_storage (key, value)
+    VALUES (?, ?)
+    ON CONFLICT(key) DO UPDATE SET value = excluded.value
   `).run('main_storage', encryptPayload(plainText));
 }
 function getStoredPayload() {
@@ -113,14 +113,14 @@ function getDb() {
         }
         const sqlite = require('node:sqlite');
         _db = new sqlite.DatabaseSync(path);
-        _db.exec(`
-      PRAGMA journal_mode = WAL;
-      PRAGMA synchronous = NORMAL;
-
-      CREATE TABLE IF NOT EXISTS secure_storage (
-        key TEXT PRIMARY KEY,
-        value TEXT NOT NULL
-      );
+        _db.exec(`
+      PRAGMA journal_mode = WAL;
+      PRAGMA synchronous = NORMAL;
+
+      CREATE TABLE IF NOT EXISTS secure_storage (
+        key TEXT PRIMARY KEY,
+        value TEXT NOT NULL
+      );
     `);
         return _db;
     }

package/dist/src/utils/sessionTitle.js

@@ -52,18 +52,18 @@ export function extractConversationText(messages) {
         ? text.slice(-MAX_CONVERSATION_TEXT)
         : text;
 }
-const SESSION_TITLE_PROMPT = `Generate a concise, sentence-case title (3-7 words) that captures the main topic or goal of this coding session. The title should be clear enough that the user recognizes the session in a list. Use sentence case: capitalize only the first word and proper nouns.
-
-Return JSON with a single "title" field.
-
-Good examples:
-{"title": "Fix login button on mobile"}
-{"title": "Add OAuth authentication"}
-{"title": "Debug failing CI tests"}
-{"title": "Refactor API client error handling"}
-
-Bad (too vague): {"title": "Code changes"}
-Bad (too long): {"title": "Investigate and fix the issue where the login button does not respond on mobile devices"}
+const SESSION_TITLE_PROMPT = `Generate a concise, sentence-case title (3-7 words) that captures the main topic or goal of this coding session. The title should be clear enough that the user recognizes the session in a list. Use sentence case: capitalize only the first word and proper nouns.
+
+Return JSON with a single "title" field.
+
+Good examples:
+{"title": "Fix login button on mobile"}
+{"title": "Add OAuth authentication"}
+{"title": "Debug failing CI tests"}
+{"title": "Refactor API client error handling"}
+
+Bad (too vague): {"title": "Code changes"}
+Bad (too long): {"title": "Investigate and fix the issue where the login button does not respond on mobile devices"}
 Bad (wrong case): {"title": "Fix Login Button On Mobile"}`;
 const titleSchema = lazySchema(() => z.object({ title: z.string() }));
 /**

package/dist/src/utils/sideQuestion.js

@@ -35,23 +35,23 @@ export function findBtwTriggerPositions(text) {
  */
 export async function runSideQuestion({ question, cacheSafeParams, }) {
     // Wrap the question with instructions to answer without tools
-    const wrappedQuestion = `<system-reminder>This is a side question from the user. You must answer this question directly in a single response.
-
-IMPORTANT CONTEXT:
-- You are a separate, lightweight agent spawned to answer this one question
-- The main agent is NOT interrupted - it continues working independently in the background
-- You share the conversation context but are a completely separate instance
-- Do NOT reference being interrupted or what you were "previously doing" - that framing is incorrect
-
-CRITICAL CONSTRAINTS:
-- You have NO tools available - you cannot read files, run commands, search, or take any actions
-- This is a one-off response - there will be no follow-up turns
-- You can ONLY provide information based on what you already know from the conversation context
-- NEVER say things like "Let me try...", "I'll now...", "Let me check...", or promise to take any action
-- If you don't know the answer, say so - do not offer to look it up or investigate
-
-Simply answer the question with the information you have.</system-reminder>
-
+    const wrappedQuestion = `<system-reminder>This is a side question from the user. You must answer this question directly in a single response.
+
+IMPORTANT CONTEXT:
+- You are a separate, lightweight agent spawned to answer this one question
+- The main agent is NOT interrupted - it continues working independently in the background
+- You share the conversation context but are a completely separate instance
+- Do NOT reference being interrupted or what you were "previously doing" - that framing is incorrect
+
+CRITICAL CONSTRAINTS:
+- You have NO tools available - you cannot read files, run commands, search, or take any actions
+- This is a one-off response - there will be no follow-up turns
+- You can ONLY provide information based on what you already know from the conversation context
+- NEVER say things like "Let me try...", "I'll now...", "Let me check...", or promise to take any action
+- If you don't know the answer, say so - do not offer to look it up or investigate
+
+Simply answer the question with the information you have.</system-reminder>
+
 ${question}`;
     const agentResult = await runForkedAgent({
         promptMessages: [createUserMessage({ content: wrappedQuestion })],

package/dist/src/utils/swarm/backends/registry.js

@@ -192,22 +192,22 @@ function getTmuxInstallInstructions() {
     const platform = getPlatform();
     switch (platform) {
         case 'macos':
-            return `To use agent swarms, install tmux:
-  brew install tmux
+            return `To use agent swarms, install tmux:
+  brew install tmux
 Then start a tmux session with: tmux new-session -s claude`;
         case 'linux':
         case 'wsl':
-            return `To use agent swarms, install tmux:
-  sudo apt install tmux    # Ubuntu/Debian
-  sudo dnf install tmux    # Fedora/RHEL
+            return `To use agent swarms, install tmux:
+  sudo apt install tmux    # Ubuntu/Debian
+  sudo dnf install tmux    # Fedora/RHEL
 Then start a tmux session with: tmux new-session -s claude`;
         case 'windows':
-            return `To use agent swarms, you need tmux which requires WSL (Windows Subsystem for Linux).
-Install WSL first, then inside WSL run:
-  sudo apt install tmux
+            return `To use agent swarms, you need tmux which requires WSL (Windows Subsystem for Linux).
+Install WSL first, then inside WSL run:
+  sudo apt install tmux
 Then start a tmux session with: tmux new-session -s claude`;
         default:
-            return `To use agent swarms, install tmux using your system's package manager.
+            return `To use agent swarms, install tmux using your system's package manager.
 Then start a tmux session with: tmux new-session -s claude`;
     }
 }

package/dist/src/utils/task/framework.js

@@ -208,12 +208,12 @@ function enqueueTaskNotification(attachment) {
     const toolUseIdLine = attachment.toolUseId
         ? `\n<${TOOL_USE_ID_TAG}>${attachment.toolUseId}</${TOOL_USE_ID_TAG}>`
         : '';
-    const message = `<${TASK_NOTIFICATION_TAG}>
-<${TASK_ID_TAG}>${attachment.taskId}</${TASK_ID_TAG}>${toolUseIdLine}
-<${TASK_TYPE_TAG}>${attachment.taskType}</${TASK_TYPE_TAG}>
-<${OUTPUT_FILE_TAG}>${outputPath}</${OUTPUT_FILE_TAG}>
-<${STATUS_TAG}>${attachment.status}</${STATUS_TAG}>
-<${SUMMARY_TAG}>Task "${attachment.description}" ${statusText}</${SUMMARY_TAG}>
+    const message = `<${TASK_NOTIFICATION_TAG}>
+<${TASK_ID_TAG}>${attachment.taskId}</${TASK_ID_TAG}>${toolUseIdLine}
+<${TASK_TYPE_TAG}>${attachment.taskType}</${TASK_TYPE_TAG}>
+<${OUTPUT_FILE_TAG}>${outputPath}</${OUTPUT_FILE_TAG}>
+<${STATUS_TAG}>${attachment.status}</${STATUS_TAG}>
+<${SUMMARY_TAG}>Task "${attachment.description}" ${statusText}</${SUMMARY_TAG}>
 </${TASK_NOTIFICATION_TAG}>`;
     enqueuePendingNotification({ value: message, mode: 'task-notification' });
 }

package/dist/src/utils/teleport.js

@@ -57,21 +57,21 @@ function createTeleportResumeUserMessage() {
         isMeta: true
     });
 }
-const SESSION_TITLE_AND_BRANCH_PROMPT = `You are coming up with a succinct title and git branch name for a coding session based on the provided description. The title should be clear, concise, and accurately reflect the content of the coding task.
-You should keep it short and simple, ideally no more than 6 words. Avoid using jargon or overly technical terms unless absolutely necessary. The title should be easy to understand for anyone reading it.
-Use sentence case for the title (capitalize only the first word and proper nouns), not Title Case.
-
-The branch name should be clear, concise, and accurately reflect the content of the coding task.
-You should keep it short and simple, ideally no more than 4 words. The branch should always start with "context/" and should be all lower case, with words separated by dashes.
-
-Return a JSON object with "title" and "branch" fields.
-
-Example 1: {"title": "Fix login button not working on mobile", "branch": "context/fix-mobile-login-button"}
-Example 2: {"title": "Update README with installation instructions", "branch": "context/update-readme"}
-Example 3: {"title": "Improve performance of data processing script", "branch": "context/improve-data-processing"}
-
-Here is the session description:
-<description>{description}</description>
+const SESSION_TITLE_AND_BRANCH_PROMPT = `You are coming up with a succinct title and git branch name for a coding session based on the provided description. The title should be clear, concise, and accurately reflect the content of the coding task.
+You should keep it short and simple, ideally no more than 6 words. Avoid using jargon or overly technical terms unless absolutely necessary. The title should be easy to understand for anyone reading it.
+Use sentence case for the title (capitalize only the first word and proper nouns), not Title Case.
+
+The branch name should be clear, concise, and accurately reflect the content of the coding task.
+You should keep it short and simple, ideally no more than 4 words. The branch should always start with "context/" and should be all lower case, with words separated by dashes.
+
+Return a JSON object with "title" and "branch" fields.
+
+Example 1: {"title": "Fix login button not working on mobile", "branch": "context/fix-mobile-login-button"}
+Example 2: {"title": "Update README with installation instructions", "branch": "context/update-readme"}
+Example 3: {"title": "Improve performance of data processing script", "branch": "context/improve-data-processing"}
+
+Here is the session description:
+<description>{description}</description>
 Please generate a title and branch name for this session.`;
 /**
  * Generates a title and branch name for a coding session using Claude Haiku

package/docs/Contex.md

@@ -35,24 +35,24 @@ src/
 ## Comandos de Desarrollo
 
 ```bash
-npm run typecheck          # Verificar tipos TypeScript
-npm run build              # Compilar el proyecto
-npm run dev:build          # Alias de build
-npm run dev:watch          # Compilar en modo watch
-npm run dev:run            # Ejecutar versión de desarrollo
-npm run start              # Ejecutar la versión compilada
-```
-
-## Sistema de Proveedores
-
-El proyecto ya no debe asumirse como proveedor-unico. La capa actual distingue entre proveedor activo y perfil activo:
-
-- `provider profiles` guardan base URL, ultimo modelo y credenciales cuando aplica.
-- `agentName` queda reservado como nombre operativo para futuros subagentes.
-- los proveedores visibles ya resuelven perfiles de forma compatible; `ollama` y `zai` fueron la primera migracion completa y el resto usa fallback a la configuracion anterior.
-- La configuracion anterior sigue sirviendo como fallback para no romper instalaciones existentes.
-
-## Convenciones de Código
+pnpm typecheck             # Verificar tipos TypeScript
+pnpm build                 # Compilar el proyecto
+pnpm dev:build             # Alias de build
+pnpm dev:watch             # Compilar en modo watch
+pnpm dev:run               # Ejecutar versión de desarrollo
+pnpm start                 # Ejecutar la versión compilada
+```
+
+## Sistema de Proveedores
+
+El proyecto ya no debe asumirse como proveedor-unico. La capa actual distingue entre proveedor activo y perfil activo:
+
+- `provider profiles` guardan base URL, ultimo modelo y credenciales cuando aplica.
+- `agentName` queda reservado como nombre operativo para futuros subagentes.
+- los proveedores visibles ya resuelven perfiles de forma compatible; `ollama` y `zai` fueron la primera migracion completa y el resto usa fallback a la configuracion anterior.
+- La configuracion anterior sigue sirviendo como fallback para no romper instalaciones existentes.
+
+## Convenciones de Código
 
 - **TypeScript estricto desactivado** (`strict: false`), pero mantener buenas prácticas de tipado.
 - **Módulos ESM** (`"type": "module"`), usar `import`/`export` siempre.
@@ -65,6 +65,6 @@ El proyecto ya no debe asumirse como proveedor-unico. La capa actual distingue e
 ## Notas Importantes
 
 - No publicar el paquete directamente; el proceso de publicación requiere la variable de entorno `AUTHORIZED`.
-- `tsconfig.json` se usa para compilaciones del proyecto y `tsconfig.typecheck.json` para validación de tipos.
-- Los archivos de distribución se generan en `dist/`.
+- `tsconfig.json` se usa para compilaciones del proyecto y `tsconfig.typecheck.json` para validación de tipos.
+- Los archivos de distribución se generan en `dist/`.
 - Consultar `RECOVERY_NOTES.md` y `RENAMING_NOTES.md` para contexto histórico del proyecto.

package/docs/PHASE_3_VALIDATION.md

@@ -20,7 +20,7 @@ La Fase 3 cubre:
 Ejecutar:
 
 ```sh
-npm run build
+pnpm build
 ```
 
 Resultado esperado:
@@ -31,7 +31,7 @@ Resultado esperado:
 Tambien se puede ejecutar:
 
 ```sh
-npm run typecheck
+pnpm typecheck
 ```
 
 Estado actual:

package/docs/PUBLISH.md

@@ -0,0 +1,199 @@
+# Publicar Context Code en npmjs
+
+Guía completa de los caminos para publicar el paquete `@iaforged/context-code`.
+El paquete se publica al registry oficial de npmjs (`https://registry.npmjs.org/`)
+y puede subirse tanto con `pnpm` como con `npm`. El cliente que uses al publicar
+es independiente del cliente que usen los usuarios finales para instalarlo.
+
+---
+
+## Antes de publicar — checks obligatorios
+
+```bash
+pnpm whoami                              # debe imprimir tu usuario de npmjs
+# o si vas a usar npm:
+npm whoami
+
+pnpm view @iaforged/context-code version # versión actual en el registry
+git status                               # cero cambios pendientes en main
+node --check cli.js                      # bundle de producción válido
+```
+
+Si no estás logueado:
+
+```bash
+pnpm login --registry=https://registry.npmjs.org/
+# o:
+npm login --registry=https://registry.npmjs.org/
+```
+
+Variables/flags que la pipeline interna necesita:
+
+- `AUTHORIZED=1` — obligatorio. El script `scripts/preflight-check.mjs` corre
+  como `prepublishOnly` y aborta si esa variable no está. Es la salvaguarda
+  contra publicaciones accidentales desde una terminal cualquiera.
+- `--access public` — el paquete es scoped (`@iaforged/...`); por defecto los
+  scoped son privados, hay que forzar público.
+- `--no-git-checks` (pnpm) — la pipeline modifica `package.json` durante la
+  publicación, así que `pnpm` no debe quejarse por árbol sucio.
+
+---
+
+## Opción A — Pipeline completa (recomendado): `pnpm pubpackages`
+
+Es el flujo "todo en uno" que vive en `scripts/pubpackages.sh`:
+
+```bash
+pnpm pubpackages
+```
+
+Pasos que ejecuta:
+
+1. `pnpm build` — compila TypeScript a `dist/`.
+2. Bump de versión automático en `package.json` (1.3.5 → 1.3.6; al llegar a
+   x.x.9 salta a x.(y+1).0).
+3. Genera un `package.json` "limpio" para publicar (sin `devDependencies`, sin
+   `pnpm.*`, sin scripts de desarrollo). Mantiene una copia del original.
+4. `pnpm publish --access public --no-git-checks`.
+5. Restaura el `package.json` original (vía `trap EXIT`) aunque la publicación
+   falle.
+
+Equivalente con npm si prefieres no usar pnpm para publicar (mismo script,
+mismo flujo — pnpm solo orquesta el bash):
+
+```bash
+AUTHORIZED=1 bash ./scripts/pubpackages.sh
+```
+
+> El `pnpm` interno del script seguirá invocándose para `pnpm build` y
+> `pnpm publish`. Si quieres una versión 100% npm, copia el script y reemplaza
+> esas dos invocaciones por `npm run build` y `npm publish --access public`.
+
+---
+
+## Opción B — Publicación manual desde PowerShell (Windows)
+
+`publish-package.ps1` está en la raíz del repo. No bumpea versión: publica
+exactamente lo que haya en `package.json`. Útil para reintentar una publicación
+que falló o para subir versiones beta/preview.
+
+```powershell
+.\publish-package.ps1                     # tag latest, access public
+.\publish-package.ps1 -Tag beta
+.\publish-package.ps1 -Tag rc -Access public
+```
+
+Lo que hace:
+
+1. Localiza `pnpm` en el PATH (o en rutas típicas de Windows: `nvm`, `npm` global, `Program Files\nodejs`).
+2. Pone `AUTHORIZED=1`.
+3. Corre `node --check cli.js` para validar el bundle.
+4. `pnpm publish --tag <tag> --access <access> --no-git-checks`.
+
+---
+
+## Opción C — Una línea directa (cuando ya sabes qué quieres subir)
+
+Con pnpm:
+
+```bash
+pnpm build
+AUTHORIZED=1 pnpm publish --access public --no-git-checks
+```
+
+Con npm:
+
+```bash
+pnpm build                                # o npm run build si quieres todo npm
+AUTHORIZED=1 npm publish --access public
+```
+
+Variantes con tag distinto a `latest`:
+
+```bash
+AUTHORIZED=1 pnpm publish --access public --tag beta --no-git-checks
+AUTHORIZED=1 npm publish --access public --tag beta
+```
+
+> Nota: con `npm publish` no necesitas `--no-git-checks` — npm no valida árbol
+> de git, solo pnpm lo hace por defecto.
+
+---
+
+## Diferencias prácticas pnpm vs npm al publicar
+
+| Aspecto | pnpm | npm |
+|---|---|---|
+| Lee `.npmrc` raíz | sí | sí |
+| Lee `pnpm-workspace.yaml#allowBuilds` | sí | no aplica (no bloquea install scripts) |
+| Valida árbol git por defecto | sí (necesita `--no-git-checks`) | no |
+| Respeta `prepublishOnly` script | sí | sí |
+| Respeta `publishConfig.registry` | sí | sí |
+| Archivos incluidos en el tar | igual (lee `files` de `package.json` y `.npmignore`) | igual |
+| Reduce el tamaño del tar | igual (ambos comprimen con `tar.gz`) | igual |
+| Velocidad real | parecida; pnpm hace una pasada más para validar el lockfile | parecida |
+
+El paquete resultante en el registry es **bit-by-bit idéntico** independiente
+del cliente que lo suba — los usuarios finales pueden instalar con `npm`,
+`pnpm`, `yarn` o `bun` sin diferencia.
+
+---
+
+## Verificación post-publicación
+
+```bash
+pnpm view @iaforged/context-code version      # versión publicada
+pnpm view @iaforged/context-code dist-tags    # qué dist-tag apunta dónde
+
+# instalar la versión recién subida en una carpeta limpia para probar:
+mkdir /tmp/cc-test && cd /tmp/cc-test
+pnpm add @iaforged/context-code@latest
+./node_modules/.bin/context --version
+```
+
+Si publicaste con un tag distinto a `latest`:
+
+```bash
+pnpm add @iaforged/context-code@beta
+```
+
+---
+
+## Si algo falla
+
+| Error | Causa típica | Cómo se arregla |
+|---|---|---|
+| `ENEEDAUTH` | no estás logueado | `pnpm login` o `npm login` |
+| `403 Forbidden` | el usuario no tiene permisos de publish en el scope | añade el usuario al scope `@iaforged` en npmjs.com |
+| `Cannot publish over previously published version` | la versión ya existe | bump de versión (manual o por `pubpackages`) |
+| `ERR_PNPM_GIT_UNCLEAN` | árbol sucio | `git stash` o `--no-git-checks` |
+| El preflight aborta sin publicar | falta `AUTHORIZED=1` | añadir la variable al entorno |
+| `tsc no se reconoce` durante prepublish | falta `typescript` en devDeps | `pnpm add -D typescript` (ya está en main) |
+
+---
+
+## Política de versiones
+
+El bump automático del `pubpackages.sh` sigue una variante mínima:
+- `patch` incrementa cada release.
+- Al llegar a `patch === 9` salta a `minor + 1` y `patch = 0`.
+- Nunca toca `major`.
+
+Para bumpear manualmente (p. ej. una major):
+
+```bash
+node -e "const p=require('./package.json'); p.version='2.0.0'; require('fs').writeFileSync('package.json', JSON.stringify(p,null,2)+'\n')"
+AUTHORIZED=1 pnpm publish --access public --no-git-checks
+```
+
+---
+
+## Despublicar / depreciar (no recomendado)
+
+npm bloquea unpublish después de 72h. Para marcar una versión como obsoleta:
+
+```bash
+npm deprecate @iaforged/context-code@1.3.5 "Usa 1.3.6 o superior"
+```
+
+Esto no quita el paquete del registry, solo añade un warning al instalar.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@iaforged/context-code",
-  "version": "1.2.12",
+  "version": "1.3.6",
   "description": "Context Code es un asistente de desarrollo para la terminal. Puede revisar tu proyecto, editar archivos, ejecutar comandos y apoyarte en tareas reales de programacion.",
   "author": "Context AI",
   "license": "MIT",
@@ -138,7 +138,5 @@
     "@img/sharp-win32-x64": "^0.34.2",
     "@whiskeysockets/baileys": "7.0.0-rc.9"
   },
-  "scripts": {
-    "prepublishOnly": "node ./scripts/preflight-check.mjs"
-  }
-}
+  "scripts": {}
+}