@north-light/crouter 0.3.185 → 0.3.187

package/dist/api/dto/broker.d.ts

@@ -28,38 +28,6 @@ export interface BrokerWelcomeSnapshot<M = unknown> {
 export interface BrokerWelcomeFrame<M = unknown> {
     type: 'welcome';
     snapshot?: BrokerWelcomeSnapshot<M>;
-    /** The last few id-bearing user-message dispatches from the broker's message
-     *  ledger, oldest first — so a reattaching follower can key the snapshot's
-     *  trailing user wakes by id (the id a sender minted via `message_id` on
-     *  `POST .../messages`) instead of discarding them heuristically. Live-process
-     *  memory only: a broker restart loses it. Absent on a broker pinned to an
-     *  older runtime generation. */
-    recentUserMessages?: Array<{
-        id: string;
-        text: string;
-    }>;
-}
-/**
- * The additive identity fields the broker sets on a relayed pi `queue_update`:
- * id arrays PARALLEL to pi's text arrays (`steeringIds[i]` identifies
- * `steering[i]`). Sender-minted when the send carried `message_id`,
- * broker-minted otherwise. Absent on a broker pinned to an older runtime
- * generation — consumers fall back to bare texts. Intersect with the pinned pi
- * `queue_update` event shape to read them typed.
- */
-export interface RelayedQueueUpdateIdentity {
-    steeringIds?: string[];
-    followUpIds?: string[];
-}
-/**
- * The additive identity field the broker sets on a relayed USER-role
- * `message_start`: the message's crouter id — the `message_id` its sender
- * minted, or a broker-minted one. Absent when the message carries none (an
- * engine-command expansion, a pre-ledger replay, an older broker). Intersect
- * with the pinned pi `message_start` event shape to read it typed.
- */
-export interface RelayedUserMessageStartIdentity {
-    crtrMessageId?: string;
 }
 /**
  * The broker-control frames a relay consumer reads: `welcome` (catch-up snapshot)

package/dist/api/dto/messages.d.ts

@@ -26,11 +26,6 @@ export interface SendMessageRequest {
      *  body only — rejected with fresh/reopen/situational_context/
      *  output_schema or tier 'deferred'. Absent → durable inbox (unchanged). */
     delivery?: 'interactive';
-    /** Sender-minted message identity for a `delivery:'interactive'` send. The
-     *  broker mirrors it through pi's queues and echoes it on the relayed user
-     *  `message_start` (`crtrMessageId`), so an optimistic sender (the gateway)
-     *  retires its pending entry by exact id. Ignored on the durable-inbox path. */
-    message_id?: string;
 }
 /** Result of an immediate message send. */
 export interface MessageResultDTO {

package/dist/builtin-memory/internal/agent-shaping.md

@@ -47,7 +47,7 @@ Specialist sub-personas hang off a parent kind — `plan/reviewers/*` (architect
 
 ### Custom personas
 
-The roster is extensible. Add a `kinds.<name>` entry to a `config.json` at user or project scope (fields: `whenToUse` required, plus optional `model`, `orchestratorModel`, `tools`, `extensions`, `availableTo`) and author the persona prose at `kinds/<name>/00-base.md` (and `01-orchestrator.md`) gated `{kind: <name>, mode: ...}`. A standing personal assistant, for example, is a scope-configured custom `personal-assistant` kind rather than a builtin kind. The registry merges **project > user > builtin**, so a custom kind can add a new role or shadow a builtin one without restating the rest. Reach for a custom kind when a **recurring role** wants its own standing discipline and model/tool defaults that outlast any single task — not for a one-off instruction, which belongs in the spawn prompt.
+The roster is extensible. Add a `kinds.<name>` entry to a `config.json` at user or project scope (fields: `whenToUse` required, plus optional `model`, `orchestratorModel`, `tools`, `extensions`, `availableTo`) and author the persona prose at `kinds/<name>/00-base.md` (and `01-orchestrator.md`) gated `{kind: <name>, mode: ...}`. A standing personal assistant, for example, is a scope-configured custom `personal-assistant` kind rather than a builtin kind. The registry merges **project > user > builtin**, so a custom kind can add a new role or shadow a builtin one without restating the rest. A plugin can ship a kind the same way — a `kinds` block in its manifest plus gated persona docs in its memory tree; an enabled plugin's entries layer directly below its host scope's own `config.json` (see `internal/plugins`). Reach for a custom kind when a **recurring role** wants its own standing discipline and model/tool defaults that outlast any single task — not for a one-off instruction, which belongs in the spawn prompt.
 
 ## Modes — base vs orchestrator
 

package/dist/builtin-memory/internal/plugins.md

@@ -64,6 +64,15 @@ The `<plugin-name>` directory IS the plugin. The manifest's `name` field must ma
 | `owner` | optional | Author info. |
 | `commands` | optional | Plugin-root-relative path to a `commands.json` command manifest. It must appear with `transport`; together they make the plugin contribute `crtr` commands — see [Plugin commands](#plugin-commands). |
 | `transport` | optional | Required exactly when `commands` is present. `{ "kind": "exec", "executable": "bin/cmd.js" }` runs executable leaves; a passthrough-only exec manifest may omit `executable`. `{ "kind": "http", "endpoint": "https://…", "authEnv": "TOKEN_NAME" }` calls a remote HTTP command surface. Archive-installed plugins also carry crouter-synthesized `bundle` provenance; authors do not add it. |
+| `kinds` | optional | Kind-registry contributions, keyed by full kind string — the same two entry shapes a scope `config.json` `kinds` block accepts: a FULL entry (`whenToUse` required, plus optional `model`, `orchestratorModel`, `tools`, `extensions`, `availableTo`) defines or shadows a kind; a sparse PATCH overrides launch knobs of a kind a lower layer defines. See [Plugin kinds](#plugin-kinds). |
+
+## Plugin kinds
+
+A plugin can ship a complete persona kind: declare the registry entry in the manifest's `kinds` block, and author the persona prose as ordinary plugin memory docs gated `{kind: <name>, mode: base}` (and `{kind: <name>, mode: orchestrator}`) with `system-prompt-visibility: content` — the same shape a builtin kind uses at `kinds/<kind>/00-base.md`. Nothing else is needed: gates evaluate uniformly over plugin docs, so the persona splices into any node launched with that kind.
+
+`readMergedLaunchConfig` layers an enabled plugin's `kinds` entries directly above the builtin registry and below its host scope's own `config.json` — full precedence: builtin → user-scope plugins → user config → profile → per project root (that root's plugins → that root's config). So a plugin kind appears in `crtr node new -h` and is launchable like any other, and a user or project `config.json` can still patch or shadow it. Plugins within one scope layer name-sorted; the scope's own config always wins.
+
+For archive plugins the declaration lives in the archive's `bundle.json` — `{"bundleVersion": 1, "kinds": {…}}` — and the installer copies the block into the synthesized manifest. Install validates the block strictly (an invalid entry fails the install with per-entry reasons); the read side drops invalid entries silently, so the loud gate is install time.
 
 ## Scopes
 

package/dist/clients/attach/input/controller.js

@@ -2,7 +2,6 @@
 // lifetime belongs to InputOverlayOwner; viewer permission belongs to the single
 // ViewerCapabilities value supplied by session/input-wiring.
 import { spawn } from 'node:child_process';
-import { randomUUID } from 'node:crypto';
 import { readFileSync, unlinkSync, writeFileSync } from 'node:fs';
 import { tmpdir } from 'node:os';
 import { join } from 'node:path';
@@ -46,7 +45,7 @@ export class InputController {
         this.emitCommand({ type: 'cycle_ladder', direction });
     }
     sendInterrupting(text) {
-        return this.emitDrive({ type: 'prompt', text, interrupt: true, message_id: randomUUID() });
+        return this.emitDrive({ type: 'prompt', text, interrupt: true });
     }
     attachDialog(request) {
         this.overlays.attachDialog(request);
@@ -182,7 +181,7 @@ export class InputController {
         if (delivery !== 'steer' && delivery !== 'prompt')
             return;
         const expanded = this.expandImagePlaceholders(classification.kind === 'slash' ? text : classification.text);
-        if (!this.emitDrive(delivery === 'steer' ? { type: 'steer', text: expanded, message_id: randomUUID() } : { type: 'prompt', text: expanded, message_id: randomUUID() }))
+        if (!this.emitDrive(delivery === 'steer' ? { type: 'steer', text: expanded } : { type: 'prompt', text: expanded }))
             return;
         this.editor.addToHistory(classification.trimmed);
         this.editor.setText('');
@@ -194,7 +193,7 @@ export class InputController {
         const trimmed = text.trim();
         if (!trimmed)
             return;
-        if (!this.emitDrive({ type: 'follow_up', text: this.expandImagePlaceholders(text), message_id: randomUUID() }))
+        if (!this.emitDrive({ type: 'follow_up', text: this.expandImagePlaceholders(text) }))
             return;
         this.editor.addToHistory(trimmed);
         this.editor.setText('');

package/dist/clients/attach/overlays/mcp.js

@@ -39,7 +39,7 @@
 // as cached but fails to reconnect). Action names verified against the
 // installed adapter (pi-mcp-adapter index.ts: "auth-start" / "auth-complete" /
 // "ui-messages"; `connect: <name>`).
-import { createHash, randomUUID } from 'node:crypto';
+import { createHash } from 'node:crypto';
 import { existsSync } from 'node:fs';
 import { homedir } from 'node:os';
 import { join, resolve } from 'node:path';
@@ -257,7 +257,6 @@ export function startMcpServerAction(row, send, notify) {
         send({
             type: 'prompt',
             text: `Run mcp({ action: "auth-start", server: ${nameJson} }) and show me the returned OAuth URL verbatim (with any instructions). If the server does not need OAuth, run mcp({ connect: ${nameJson} }) instead and report the result.`,
-            message_id: randomUUID(),
         });
         notify(`Asking the engine to start OAuth for ${row.name}…`);
     }
@@ -265,7 +264,6 @@ export function startMcpServerAction(row, send, notify) {
         send({
             type: 'prompt',
             text: `Run mcp({ connect: ${nameJson} }) to reconnect that MCP server and report the result. If it fails with an authentication or authorization error, run mcp({ action: "auth-start", server: ${nameJson} }) and show me the returned OAuth URL verbatim (with any instructions).`,
-            message_id: randomUUID(),
         });
         notify(`Asking the engine to reconnect ${row.name}…`);
     }

package/dist/clients/attach/slash/dispatch.js

@@ -22,7 +22,6 @@
 // SCOPED OUT (no engine method): `/login`, `/logout`, `/share`,
 // `/trust` — a brief "not supported in attach" notice, never a frame.
 import { execFile } from 'node:child_process';
-import { randomUUID } from 'node:crypto';
 import { BUILTIN_SLASH_COMMANDS } from '../../../core/runtime/pi-vendored.js';
 import { surfaceTmuxStyleArgs } from '../../../core/runtime/surface-bg.js';
 import { viewerOperationForSlash } from '../input/capabilities.js';
@@ -452,7 +451,6 @@ function promoteNode(arg, ctx) {
         ctx.send({
             type: 'prompt',
             text: 'You have just been promoted to an orchestrator. Your new-role guidance is arriving — read it, author your roadmap, and start delegating.',
-            message_id: randomUUID(),
         });
     });
     child.stdin?.end();