@north-light/crouter 0.3.183 → 0.3.185

package/dist/pi-extensions/canvas-bash-valve.js

@@ -28,6 +28,7 @@ import { spawn } from 'node:child_process';
 import { closeSync, existsSync, mkdirSync, openSync, readFileSync, readSync, rmSync, statSync, writeFileSync, } from 'node:fs';
 import { homedir } from 'node:os';
 import { backgroundBashJob, bashJobPaths, formatBashElapsed, newBashJobId } from '../core/bash-jobs.js';
+import { Type } from 'typebox';
 import { createBashToolDefinition } from '@earendil-works/pi-coding-agent';
 // ---------------------------------------------------------------------------
 // Deadline — 5 minutes by default, overridable via CRTR_BASH_VALVE_MS
@@ -342,6 +343,49 @@ export function createValveOperations(nodeId, contextDir) {
 // ---------------------------------------------------------------------------
 // Extension
 // ---------------------------------------------------------------------------
+// ---------------------------------------------------------------------------
+// `purpose` — the one line a person reads while a command runs
+//
+// A deliberate deviation from taking pi's definition verbatim, and the only one
+// here. Everywhere crtr's output reaches a non-technical audience, the host has
+// to render SOMETHING per step, and without this field its only material is the
+// command — which yields "Running command" for an entire turn. The model is the
+// only party that knows why it is running this, so it says so, in one clause,
+// before the command streams.
+//
+// Declared FIRST so it arrives ahead of `command` in the argument stream: a host
+// parsing partial JSON can show the label while the command is still being
+// written, rather than after the call is complete and about to finish.
+//
+// The execute path ignores it entirely — this is a labelling channel, not an
+// input. Optional, so a model that omits it behaves exactly as before.
+//
+// Upstream ask: pi's own bash tool should carry this (Claude Code's bash tool
+// has shipped an equivalent `description` field for years). Until it does, the
+// field is re-declared here on top of pi's schema rather than forked into it.
+// ---------------------------------------------------------------------------
+const PURPOSE_DESCRIPTION = [
+    'One short clause naming what this step is FOR, in the words of the person you',
+    'are working for — "Reading the Acme thread", not "Fetching emails" and never',
+    '"Running GMAIL_FETCH_EMAILS". A person reads this while the command runs; it',
+    'is the only thing they see of this step. Under about eight words. Omit it for',
+    'steps that only touch your own scratch work.',
+].join(' ');
+/**
+ * Prepend an optional `purpose` to pi's bash schema, carrying pi's own property
+ * definitions through verbatim — so a future upstream change to the `command`
+ * or `timeout` wording still reaches the model, and this file owns exactly one
+ * field.
+ */
+function withPurpose(definition) {
+    return {
+        ...definition,
+        parameters: Type.Object({
+            purpose: Type.Optional(Type.String({ description: PURPOSE_DESCRIPTION })),
+            ...definition.parameters.properties,
+        }),
+    };
+}
 export default function (pi) {
     const nodeId = process.env['CRTR_NODE_ID'];
     if (nodeId === undefined || nodeId.trim() === '')
@@ -356,6 +400,6 @@ export default function (pi) {
     // every session_start is idempotent (last registration wins).
     pi.on('session_start', (_event, ctx) => {
         const operations = createValveOperations(nodeId, contextDir);
-        pi.registerTool(createBashToolDefinition(ctx.cwd, { operations }));
+        pi.registerTool(withPurpose(createBashToolDefinition(ctx.cwd, { operations })));
     });
 }

package/dist/types.d.ts

@@ -301,7 +301,10 @@ export interface InstalledPlugin {
 }
 export interface InstalledMarketplace {
     name: string;
-    scope: Scope;
+    /** Never `builtin`: marketplaces are registered by the user into the user or
+     *  project scope, and `listInstalledMarketplaces` has no builtin directory to
+     *  read. `builtin` describes plugins that ship with crtr, not their source. */
+    scope: Exclude<Scope, 'builtin'>;
     root: string;
     manifest: MarketplaceManifest;
     url: string;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@north-light/crouter",
-  "version": "0.3.183",
+  "version": "0.3.185",
   "description": "crtr — agent runtime with memory, plugins, and marketplaces",
   "type": "module",
   "main": "dist/index.js",

package/runtime.lock.json

@@ -1,12 +1,12 @@
 {
   "name": "@north-light/crouter",
-  "version": "0.3.183",
+  "version": "0.3.185",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "@north-light/crouter",
-      "version": "0.3.183",
+      "version": "0.3.185",
       "hasInstallScript": true,
       "license": "MIT",
       "dependencies": {