@gonrocca/zero-pi 0.1.20 → 0.1.21

package/extensions/autotune-extension.ts

@@ -157,7 +157,7 @@ function evaluateAndTune(ctx: PiSessionContext): void {
   if (data === null) {
     // Absent or unparseable `zero.json` — no profile to safely tune. Skip with
     // a single non-blocking warning; never synthesize a `models` map (AC 6.4).
-    notify("zero autotune: ~/.pi/zero.json missing or unreadable — skipping", "warning");
+    notify("zero autotune: ~/.pi/zero.json falta o no se puede leer — se omite", "warning");
     return;
   }
 
@@ -213,7 +213,7 @@ function evaluateAndTune(ctx: PiSessionContext): void {
   );
   for (const adj of pending) {
     notify(
-      `zero autotune suggests: ${adj.phase} → ${adj.to} — run /zero-models to apply`,
+      `zero autotune sugiere: ${adj.phase} → ${adj.to} — corré /zero-models para aplicar`,
       "info",
     );
   }

package/extensions/autotune.ts

@@ -526,7 +526,7 @@ export function decideAdjustments(
     if (to === null) continue; // already at top tier, or untierable
 
     const blame = phase === "build" ? "corregir" : "replantear";
-    const reason = `avg ${measure.toFixed(1)} ${blame}/run over ${stat.v2Samples} v2 runs`;
+    const reason = `prom ${measure.toFixed(1)} ${blame}/run en ${stat.v2Samples} runs v2`;
 
     adjustments.push({ phase, from: currentModel, to, reason });
   }

package/extensions/conversation-resume.ts

@@ -368,21 +368,21 @@ export default function register(pi?: PiAPI): void {
 
       try {
         const path = writeFromContext(ctx, reason);
-        if (path) notify(ctx, `zero resume written: ${path}`, "info");
+        if (path) notify(ctx, `zero: resumen guardado en ${path}`, "info");
       } catch (err) {
-        notify(ctx, `zero resume failed: ${err instanceof Error ? err.message : String(err)}`, "warning");
+        notify(ctx, `zero: falló el resumen — ${err instanceof Error ? err.message : String(err)}`, "warning");
       }
     });
   }
 
   if (typeof pi.registerCommand === "function") {
     pi.registerCommand("zero-resume", {
-      description: "Write .pi/zero-resume.md with restore command and conversation tail",
+      description: "Escribe .pi/zero-resume.md con el comando de restauración y el final de la conversación",
       handler: async (_args, ctx) => {
         try {
           const path = writeFromContext(ctx, "manual");
           if (!path) {
-            notify(ctx, "zero-resume: no persisted session context found", "warning");
+            notify(ctx, "zero-resume: no hay contexto de sesión persistido", "warning");
             return;
           }
           const command = sessionFile(ctx)
@@ -390,7 +390,7 @@ export default function register(pi?: PiAPI): void {
             : sessionId(ctx)
               ? `pi --session ${sessionId(ctx)}`
               : "pi --resume";
-          notify(ctx, `zero-resume: wrote ${path}\nrestore: ${command}`, "info");
+          notify(ctx, `zero-resume: escrito ${path}\nrestaurar: ${command}`, "info");
         } catch (err) {
           notify(ctx, `zero-resume: ${err instanceof Error ? err.message : String(err)}`, "error");
         }

package/extensions/spec-merge-extension.ts

@@ -121,12 +121,12 @@ function renderSyncReport(slug: string, date: string, summary: MergeSummary): st
 /** Render the human-facing one-shot report of a `MergeSummary`. */
 function describeSummary(summary: MergeSummary): string {
   const lines: string[] = [];
-  if (summary.added.length > 0) lines.push(`  added:    ${summary.added.join(", ")}`);
+  if (summary.added.length > 0) lines.push(`  agregados:    ${summary.added.join(", ")}`);
   if (summary.modified.length > 0) {
-    lines.push(`  modified: ${summary.modified.join(", ")}  (replaces existing spec text)`);
+    lines.push(`  modificados:  ${summary.modified.join(", ")}  (reemplaza el texto de spec existente)`);
   }
   if (summary.removed.length > 0) {
-    lines.push(`  removed:  ${summary.removed.join(", ")}  (deletes from the store)`);
+    lines.push(`  eliminados:   ${summary.removed.join(", ")}  (borra del store)`);
   }
   return lines.join("\n");
 }
@@ -168,8 +168,8 @@ function runSync(args: string, ctx: PiCommandContext): void {
   const slug = resolveSlug(args);
   if (slug === null) {
     notify(
-      "zero-sync: no run slug given and no single sync candidate found — " +
-        "run /zero-sync <slug> (the slug of the run's .sdd/<slug>/ directory)",
+      "zero-sync: no se dio slug de run y no hay un único candidato — " +
+        "corré /zero-sync <slug> (el slug del directorio .sdd/<slug>/ del run)",
       "warning",
     );
     return;
@@ -181,7 +181,7 @@ function runSync(args: string, ctx: PiCommandContext): void {
     // A legacy run produced no delta `spec.md` — nothing to sync. This is not
     // an error: legacy runs finish in legacy mode (additive design).
     notify(
-      `zero-sync: ${deltaPath} not found — this run produced no delta spec.md, nothing to sync`,
+      `zero-sync: ${deltaPath} no existe — este run no produjo un spec.md delta, nada para sincronizar`,
       "warning",
     );
     return;
@@ -190,7 +190,7 @@ function runSync(args: string, ctx: PiCommandContext): void {
   // An empty delta (no blocks in any section) is valid — report and stop
   // before touching the store.
   if (isEmptyDelta(parseDelta(deltaText))) {
-    notify(`zero-sync: empty delta in ${deltaPath} — nothing to sync, store left untouched`, "info");
+    notify(`zero-sync: delta vacío en ${deltaPath} — nada para sincronizar, store sin cambios`, "info");
     return;
   }
 
@@ -204,7 +204,7 @@ function runSync(args: string, ctx: PiCommandContext): void {
     // the store is flagged out of sync for a manual fix.
     const detail = result.errors.map((e) => `  - [${e.kind}] ${e.message}`).join("\n");
     notify(
-      `zero-sync: store NOT updated — the delta has guardrail errors:\n${detail}`,
+      `zero-sync: store NO actualizado — el delta tiene errores de guardrail:\n${detail}`,
       "error",
     );
     return;
@@ -219,7 +219,7 @@ function runSync(args: string, ctx: PiCommandContext): void {
     renameSync(tmp, STORE_FILE);
   } catch (err) {
     notify(
-      `zero-sync: failed to write the store at ${STORE_FILE}: ${
+      `zero-sync: no se pudo escribir el store en ${STORE_FILE}: ${
         err instanceof Error ? err.message : String(err)
       }`,
       "error",
@@ -240,16 +240,16 @@ function runSync(args: string, ctx: PiCommandContext): void {
       if (existsSync(src)) copyFileSync(src, join(archiveDir, name));
     }
     writeFileSync(join(archiveDir, "sync.md"), renderSyncReport(slug, date, result.summary), "utf8");
-    archiveNote = `archived to ${archiveDir}`;
+    archiveNote = `archivado en ${archiveDir}`;
   } catch (err) {
-    archiveNote = `WARNING: store updated but archive step failed: ${
+    archiveNote = `ATENCIÓN: store actualizado pero falló el archivado: ${
       err instanceof Error ? err.message : String(err)
     }`;
   }
 
   const detail = describeSummary(result.summary);
   notify(
-    `zero-sync: canonical store updated (${STORE_FILE})\n${detail}\n${archiveNote}`,
+    `zero-sync: store canónico actualizado (${STORE_FILE})\n${detail}\n${archiveNote}`,
     "info",
   );
 }
@@ -266,7 +266,7 @@ export default function register(pi?: PiExtensionAPI): void {
 
   pi.registerCommand("zero-sync", {
     description:
-      "Fold a /forge run's delta spec.md into the canonical .sdd/specs/ store — /zero-sync <slug>",
+      "Integra el spec.md delta de un run /forge al store canónico .sdd/specs/ — /zero-sync <slug>",
     handler: (args: string, ctx: PiCommandContext): void => {
       try {
         if (!ctx || !ctx.ui || typeof ctx.ui.notify !== "function") return;

package/extensions/zero-models.ts

@@ -257,7 +257,7 @@ export default function register(pi?: PiExtensionAPI): void {
 
   pi.registerCommand("zero-models", {
     description:
-      "Show or set the per-phase SDD models — /zero-models [<phase>=[<provider>/]<model>]",
+      "Muestra o cambia los modelos SDD por fase — /zero-models [<fase>=[<provider>/]<modelo>]",
     handler: async (args: string, ctx: PiCommandContext): Promise<void> => {
       try {
         const data = readZeroJson();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gonrocca/zero-pi",
-  "version": "0.1.20",
+  "version": "0.1.21",
   "description": "zero-pi — an installable layer for pi (pi.dev): the zero spec-driven development workflow, skill auto-learning, and an animated ZERO startup banner. Adds capability to pi without modifying pi.",
   "type": "module",
   "keywords": [

package/prompts/forge.md

@@ -14,10 +14,11 @@ claim success unless veredicto returned `pasa`.
 If the request begins with `--continue [slug]`, resume that unfinished run from
 its `.sdd/<slug>/` artifacts instead of starting fresh.
 
-**Work quietly.** Emit one short status line per phase (`explore → …`, the
-verdict, the round count) — no step-by-step narration, no reasoning out loud,
-and do not echo tool output or agent listings back into the chat. The four
+**Output and language.** Follow the orchestrator's `## Language Boundary` and
+`## Output Contract`: user-facing chat in Spanish (natural Rioplatense voseo),
+the bounded per-phase summary, no raw tool output, no agent listings, no
+step-by-step narration — progress and the final verdict, never a log. The four
 `zero-*` sub-agents already exist; delegate to them directly without running a
-`subagent` listing. The user wants progress and the final verdict, not a log.
+`subagent` listing.
 
 Feature request: $ARGUMENTS

package/prompts/orchestrator.md

@@ -112,30 +112,84 @@ start of a run and delegate each phase's sub-agent to its configured
 provider + model. When the file is absent, a phase is missing, or its provider
 entry is empty, fall back to the session's default model.
 
+## Language Boundary
+
+A zero SDD run has two language surfaces — keep them apart.
+
+- **User-facing chat — Spanish.** Every message you print to the user is in
+  Spanish, in natural Rioplatense voseo: phase status lines, phase summaries,
+  the execution-mode question, the approval question, and the final verdict.
+  This holds in interactive and automatic mode alike.
+- **Sub-agent briefs — English.** Write the briefs you hand to the `zero-*`
+  sub-agents in English, and expect their result envelopes back in English.
+  English keeps token use down and gives the executors one consistent
+  operating language. You translate and synthesize into Spanish for the user;
+  the sub-agents never address the user directly.
+- **Fixed identifiers — verbatim.** Never translate identifiers. Keep verdict
+  values (`pasa`, `corregir`, `replantear`, `cap-reached`), feature slugs,
+  file and directory paths, model ids, and command names (`/forge`,
+  `/zero-sync`) exactly as they are, even inside Spanish text.
+
+## Output Contract
+
+What you print to the user is bounded. A zero SDD run reads as a short, calm
+progress stream — not a log.
+
+**Phase start.** When a phase begins, emit one short Spanish line with: the
+phase name, the model and provider it runs on — read from `~/.pi/zero.json` as
+`<modelo> (<provider>)`, or the session's default model when the file has no
+entry for that phase — and a brief gloss of what the phase does. Inside the
+build/veredicto loop, also include the round number. One line per phase:
+
+- `Fase explore · <modelo> (<provider>) — exploro el código y junto hallazgos`
+- `Fase plan · <modelo> (<provider>) — escribo requisitos, diseño y tareas`
+- `Fase build · ronda <n> · <modelo> (<provider>) — implemento las tareas y corro los tests`
+- `Fase veredicto · ronda <n> · <modelo> (<provider>) — reviso la build y doy el veredicto`
+
+**Phase summary.** When a phase finishes, emit a bounded summary — never
+free-form prose:
+
+- `Estado:` one line — the phase and its outcome (for veredicto, the verdict).
+- `Resumen:` at most two lines of what the phase produced, user-relevant only.
+- `Artefactos:` the `.sdd/<slug>/` path(s) the phase wrote — the path, never
+  the file contents.
+- `Siguiente:` the next phase, or that the run is ending.
+
+When summarising the plan phase, also report the run's total changed-lines
+forecast from the `## Review Workload` section of `tasks.md`, naming each
+over-budget exception with its reason — or stating that every task is within
+the per-task budget.
+
+**Never noise.** Do not echo raw tool output, file dumps, full sub-agent result
+envelopes, or a sub-agent discovery/listing into the chat, and do not narrate
+your internal reasoning. Reference an artifact by its path; never paste its
+contents. Summarize each sub-agent's result in one short message — synthesize,
+do not relay.
+
+**Approval question.** In interactive mode, after the phase summary, ask a
+single Spanish question — `¿Continuamos?` — never a bilingual one. Accept
+continue, stop, or feedback.
+
+**Run end.** When the run ends, state the final verdict and say plainly whether
+the result is **verificado** (a `pasa` verdict) or **no verificado** (the
+iteration cap reached without `pasa`). Never claim success without a `pasa`.
+
+**Always visible.** Trimming noise must never make the run look frozen: the
+phase name is always stated at phase start, and the round number is always
+stated inside the build/veredicto loop. A phase that runs long keeps showing
+progress through the working indicator — never go silent for a long stretch.
+
 ## Execution mode
 
-At the start of a run, ask the user which mode they want:
+At the start of a run, ask the user — in Spanish — which mode they want:
 
-- **interactive** (default): after each phase, show a concise summary of what
-  the phase produced and what the next phase will do, then ask
-  "¿Continuamos? / Continue?" before proceeding. Accept continue, stop, or
-  feedback to adjust.
-- **automatic**: run all phases back to back without pausing; show the final
-  result only.
+- **interactive** (default): pause after each phase. Emit the phase summary
+  defined in the Output Contract, then ask `¿Continuamos?` before proceeding.
+- **automatic**: run all phases back to back without pausing; show only the
+  final result.
 
 Cache the mode for the run.
 
-When summarising the plan phase, report the run's total changed-lines forecast
-from the `## Review Workload` section of `tasks.md`, name each over-budget
-exception with its reason, and — when there are no exceptions — state that all
-tasks are within the per-task budget.
-
-## Visibility
-
-While a phase runs, keep the user informed of progress — never run silently for
-a long stretch. The user must always be able to tell which phase and round the
-run is in.
-
 ## Run memory
 
 zero runs improve each other. The pipeline reads from and writes to Cortex —

package/prompts/phases/build.md

@@ -19,4 +19,9 @@ change within the plan's scope — do not expand it on your own initiative.
 Run the test suite and make it pass before reporting the phase complete. Report
 what you changed so the veredicto phase has something concrete to review.
 
-**Work quietly.** Report only your phase's outcome — concise findings, plan, result, or verdict. No step-by-step narration, no reasoning out loud, no echoing tool output.
+**Return contract.** Return a concise result envelope to the orchestrator: your
+phase's outcome (findings, plan, build result, or verdict with its concrete
+reasoning) and the `.sdd/<slug>/` artifact path(s) you touched. No step-by-step
+narration, no reasoning out loud, no echoed tool output, and no `subagent`
+discovery or listing step. Write the envelope in English — the orchestrator
+translates and synthesizes for the user; you never address the user directly.

package/prompts/phases/explore.md

@@ -21,4 +21,9 @@ If the orchestrator includes prior-run memory in your brief, use it: past runs
 record what already broke in this code and which plans were sent back. Fold the
 relevant points into the findings under a "Prior runs" heading.
 
-**Work quietly.** Report only your phase's outcome — concise findings, plan, result, or verdict. No step-by-step narration, no reasoning out loud, no echoing tool output.
+**Return contract.** Return a concise result envelope to the orchestrator: your
+phase's outcome (findings, plan, build result, or verdict with its concrete
+reasoning) and the `.sdd/<slug>/` artifact path(s) you touched. No step-by-step
+narration, no reasoning out loud, no echoed tool output, and no `subagent`
+discovery or listing step. Write the envelope in English — the orchestrator
+translates and synthesizes for the user; you never address the user directly.

package/prompts/phases/plan.md

@@ -81,4 +81,9 @@ means the same number on every run.
   per-task estimates, and the over-budget exceptions list — state "none" when
   there are no exceptions.
 
-**Work quietly.** Report only your phase's outcome — concise findings, plan, result, or verdict. No step-by-step narration, no reasoning out loud, no echoing tool output.
+**Return contract.** Return a concise result envelope to the orchestrator: your
+phase's outcome (findings, plan, build result, or verdict with its concrete
+reasoning) and the `.sdd/<slug>/` artifact path(s) you touched. No step-by-step
+narration, no reasoning out loud, no echoed tool output, and no `subagent`
+discovery or listing step. Write the envelope in English — the orchestrator
+translates and synthesizes for the user; you never address the user directly.

package/prompts/phases/veredicto.md

@@ -29,4 +29,9 @@ State the verdict's reasoning concretely — the specific defects for `corregir`
 the specific plan flaw for `replantear`. The orchestrator persists that
 reasoning to the run's memory trace, so future runs depend on it being precise.
 
-**Work quietly.** Report only your phase's outcome — concise findings, plan, result, or verdict. No step-by-step narration, no reasoning out loud, no echoing tool output.
+**Return contract.** Return a concise result envelope to the orchestrator: your
+phase's outcome (findings, plan, build result, or verdict with its concrete
+reasoning) and the `.sdd/<slug>/` artifact path(s) you touched. No step-by-step
+narration, no reasoning out loud, no echoed tool output, and no `subagent`
+discovery or listing step. Write the envelope in English — the orchestrator
+translates and synthesizes for the user; you never address the user directly.

package/skills/sdd-routing/SKILL.md

@@ -35,7 +35,8 @@ the feature request. Pass that described work **verbatim** — do not rephrase,
 summarize, translate, or interpret it. The existing `/forge` workflow does the
 rest: an ordinary SDD run with all four phases (explore, plan, build,
 veredicto), the round cap, and the veredicto verdict, exactly as an explicit
-`/forge` invocation behaves.
+`/forge` invocation behaves — including its Spanish, low-noise output, governed
+by the orchestrator's `## Language Boundary` and `## Output Contract`.
 
 ## When NOT to route — be conservative