@north-light/crouter-api 0.3.269 → 0.3.270

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

@@ -26,6 +26,10 @@ export interface BrokerWelcomeSnapshot<M = unknown> {
     messages: M[];
     /** Stable session-entry ids aligned 1:1 with `messages`. */
     messageIds?: string[];
+    /** Presentation visibility aligned 1:1 with `messages`. */
+    messageVisibility: Array<'visible' | 'internal'>;
+    /** Presentation visibility of the run currently owned by the engine. */
+    turnVisibility: 'visible' | 'internal';
     state?: {
         isStreaming?: boolean;
     };
@@ -42,6 +46,11 @@ export interface BrokerWelcomeFrame<M = unknown> {
     type: 'welcome';
     snapshot?: BrokerWelcomeSnapshot<M>;
 }
+/** The presentation classification of the run whose native events follow. */
+export interface BrokerTurnVisibilityFrame {
+    type: 'turn_visibility';
+    visibility: 'visible' | 'internal';
+}
 /**
  * The crtrd broker `node_named` control frame — the node's generated name at the
  * instant crtrd committed it.
@@ -68,11 +77,11 @@ export interface BrokerNodeNamedFrame {
 }
 /**
  * The broker-control frames a relay consumer reads: `welcome` (catch-up snapshot),
- * `error`, and `node_named`. The broker interleaves others (display_*, ack, …)
+ * `turn_visibility`, `error`, and `node_named`. The broker interleaves others (display_*, ack, …)
  * under non-colliding `type` discriminants; a relay mapper drops those through its
  * `default` arm untyped, so they are not enumerated here.
  */
-export type BrokerControlFrame<M = unknown> = BrokerWelcomeFrame<M> | BrokerErrorFrame | BrokerNodeNamedFrame;
+export type BrokerControlFrame<M = unknown> = BrokerWelcomeFrame<M> | BrokerTurnVisibilityFrame | BrokerErrorFrame | BrokerNodeNamedFrame;
 /**
  * What the crtrd broker attach delivers to a relay consumer: the live engine
  * event stream (`E` — pi's `AgentSessionEvent`, relayed verbatim) unioned with the

package/dist/api/dto/broker.js

@@ -1,8 +1,8 @@
 // Broker attach-protocol envelope DTOs — the crtrd-specific control frames the
 // broker interleaves around pi's native agent-session event stream over a node's
 // `view.sock` (and its WS bridge, spec §5). This module owns ONLY that envelope
-// vocabulary: the two broker-control frames a relay consumer reads (`welcome` +
-// `error`), the welcome snapshot they carry, and the relay union that folds them
+// vocabulary: the broker-control frames a relay consumer reads, the welcome
+// snapshot they carry, and the relay union that folds them
 // together with the live engine event stream.
 //
 // PURITY (spec §3.1): like every file under `src/api/`, this imports NOTHING —

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

@@ -244,6 +244,8 @@ export interface NodeSnapshotDTO {
     snapshot: {
         messages: unknown[];
         messageIds?: string[];
+        messageVisibility: Array<'visible' | 'internal'>;
+        turnVisibility: 'visible' | 'internal';
         stats: unknown;
         state: Record<string, unknown>;
         display: {
@@ -282,6 +284,8 @@ export interface NodeMessagesPageDTO {
     messages: unknown[];
     /** Stable session-entry ids aligned 1:1 with `messages`. */
     message_ids?: string[];
+    /** Presentation visibility aligned 1:1 with `messages`. */
+    message_visibility: Array<'visible' | 'internal'>;
     /** Opaque cursor toward older messages; null at the start of the session. */
     next_cursor: Cursor | null;
     captured_at: IsoTime;

package/dist/shared/generated-context.d.ts

@@ -11,8 +11,7 @@ export declare const STALL_REPROMPT: string;
 /** The daemon's parking mandate: the last turn of a conversation the unattended
  *  clock is concluding. Delivered live, wrapped in a `park` runtime card. It
  *  governs both the node's durable inheritance and reader-facing output:
- *  one update for subscribers and history, then a silent stop with no assistant
- *  prose for an external channel to relay.
+ *  one update for subscribers and history, then a brief completion reply.
  *
  *  The durable inheritance shares a CONTRACT with `node yield`'s pre-invocation
  *  guide (roadmap current, short and shrinking; context dir for in-progress

package/dist/shared/generated-context.js

@@ -16,8 +16,7 @@ export const STALL_REPROMPT = "You've stopped but you're not waiting on anyone a
 /** The daemon's parking mandate: the last turn of a conversation the unattended
  *  clock is concluding. Delivered live, wrapped in a `park` runtime card. It
  *  governs both the node's durable inheritance and reader-facing output:
- *  one update for subscribers and history, then a silent stop with no assistant
- *  prose for an external channel to relay.
+ *  one update for subscribers and history, then a brief completion reply.
  *
  *  The durable inheritance shares a CONTRACT with `node yield`'s pre-invocation
  *  guide (roadmap current, short and shrinking; context dir for in-progress
@@ -28,8 +27,8 @@ export const PARK_SUMMARY_PROMPT = 'This conversation has been idle with nothing
     + '2. Rewrite `$CRTR_CONTEXT_DIR/roadmap.md` for a fresh context window. This is the only handoff document a later fresh cycle receives in full. Preserve the current goal and exit criteria when they still apply, then state the present outcome; what remains or is blocked; decisions or questions still open; exact recovery handles for in-flight state; and the first safe move on return. Keep strategy and present state, not a transcript recap. Delete stale and completed steps instead of marking them done; the roadmap should stay short and shrink. Write a minimal one now if none exists.\n\n'
     + '3. Put supporting material in your context directory only when the roadmap would become bulky without it. Rewrite existing living documents rather than leave superseded versions. Name every supporting file the next cycle must read from the roadmap and say what it is for—the revive shows filenames but does not inject their contents. Task state, identifiers, and recovery detail belong here, not in memory.\n\n'
     + '4. Use memory only for a non-obvious, reusable lesson that should survive this task and is not already recorded. Read `crtr memory write -h`, find before writing, and choose the narrowest scope that will reach the next agent who needs it. Do not put a conversation recap, task status, recovery handles, or facts already captured in code or docs into memory.\n\n'
-    + '5. Push exactly one regular update with `crtr push update --tier deferred`, never `crtr push final`. Write it for subscribers and history, not as a second roadmap. Its first line must stand alone as the current outcome, blocker, or decision that matters; then include only unfinished work, a needed decision, and concrete handles a subscriber may need. This concludes the conversation; it does not finish the mandate.\n\n'
-    + '6. Keep this entire turn silent in the conversation: produce no assistant prose before, between, or after tool calls, and do not narrate the work. Once every required tool call has finished, end the response immediately without emitting any text, sign-off, summary, acknowledgement, or other visible content by emitting the `stop` token with no text. The deferred update from step 5 is the only reader-facing conclusion. A later message reopens you on a fresh context window grounded in your goal and roadmap, so the inheritance you leave now is what you get back.';
+    + '5. Push exactly one regular update with `crtr push update --tier deferred`, never `crtr push final`. Write for someone who has not seen this conversation: name the work in plain terms, say where it stands, and say what remains or is blocked. Put the current outcome in the first line; include only needed decisions and recovery handles. This concludes the conversation, not the mandate.\n\n'
+    + '6. When finished, reply with exactly `done`.';
 /** Static recovery prompts shared by the broker producer and display classifier. */
 export const AUTH_FAULT_RECOVERY_BODY = 'Provider credentials were just updated (a new login landed). Your previous turn stopped on a provider authentication failure. Continue from where you left off and retry the work that failed.';
 export const CONNECTION_FAULT_RECOVERY_BODY = 'The network connection is back online. Your previous turn stopped on a connection error (the network was down). Continue from where you left off and retry the work that failed.';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@north-light/crouter-api",
-  "version": "0.3.269",
+  "version": "0.3.270",
   "description": "Typed crtrd /v1 API contract — DTOs, route builders, the error contract, and the CrtrClient. Zero runtime dependencies.",
   "type": "module",
   "main": "./dist/api/index.js",