dsh-context 0.44.0 → 0.45.0

package/lib/index.js

@@ -5,6 +5,7 @@ import { fileURLToPath } from "node:url";
 import { z } from "zod";
 import { deriveEventMessage } from "@deepseek-ai/dsh-session";
 import z$1 from "@deepseek-ai/schemastery";
+import { randomUUID } from "node:crypto";
 /**
 * Recover the MCP server display label from a proxied tool name, or undefined
 * for non-MCP names. `dsh-mcp-client` names tools `mcp__<server>__<rawName>`
@@ -2305,6 +2306,84 @@ function installSettings(ctx) {
 	});
 }
 //#endregion
+//#region src/host/stepIdentity.ts
+/**
+* Step-boundary message identity guard (issue #51 compatibility).
+*
+* The harness refuses to LOAD any session whose durable log carries a
+* `user/message` event whose message lacks a non-empty string `id`
+* (`assertMessageEventShape`) — while the runtime append path runs no such
+* check. One unidentified message therefore persists silently and permanently
+* bricks the session at its next load (`... failed validation: session event
+* at seq N lacks an identified message`). The observed archive held a wrap-up
+* notice whose `id` (and `summary`) had been stripped upstream of the append —
+* a shape no shipped harness producer emits, i.e. a delivery-boundary rebuild
+* outside the audited paths of both this plugin and the harness.
+*
+* This guard hardens the durability boundary from the plugin side. The agent
+* loop appends every step-boundary `user/message` from the `agent/pre-step`
+* decision's `messages` — the one seam all claimed inbox input (prompts,
+* steering, tool-deferred context) flows through before it persists. A
+* prepended listener sits OUTERMOST in that waterfall, so after `next()`
+* resolves it sees the final message list: any message that would persist
+* unidentified gets a fresh id; everything else passes by reference, and the
+* decision object is copied only when a mint happened.
+*
+* Fail-open by contract: a hostile entry (one that throws on property access),
+* a missing list, or any unexpected shape leaves the decision verbatim — a
+* guard must never break the turn it protects. Minted ids carry the `dshctx-`
+* prefix so a backfilled message stays identifiable in the wild.
+*/
+/** Prefix marking an id this guard minted (forensically distinguishable). */
+const MINTED_ID_PREFIX = "dshctx-";
+/**
+* Whether the message fails the harness's restore-time identity check (a
+* non-empty string id). Non-object entries are unfixable (an id needs a
+* container) and stay verbatim.
+*/
+function lacksId(message) {
+	if (typeof message !== "object" || message === null) return false;
+	const id = message.id;
+	return typeof id !== "string" || id === "";
+}
+/**
+* Mint ids for the messages that would persist unidentified.
+* @param messages - the decision's message list, in append order.
+* @returns the rewritten list (untouched entries by reference), or undefined
+*   when every entry already carries an identity.
+*/
+function identifiedMessages(messages) {
+	let copy;
+	for (const [index, message] of messages.entries()) {
+		if (!lacksId(message)) {
+			copy?.push(message);
+			continue;
+		}
+		copy ??= messages.slice(0, index);
+		copy.push({
+			...message,
+			id: MINTED_ID_PREFIX + randomUUID()
+		});
+	}
+	return copy;
+}
+/** Arm the prepended `agent/pre-step` guard on the plugin's context. */
+function watchStepIdentity(ctx) {
+	ctx.on("agent/pre-step", async (_input, next) => {
+		const decision = await next();
+		try {
+			if (decision.kind !== "enter" || !Array.isArray(decision.messages)) return decision;
+			const identified = identifiedMessages(decision.messages);
+			return identified === void 0 ? decision : {
+				...decision,
+				messages: identified
+			};
+		} catch {
+			return decision;
+		}
+	}, { prepend: true });
+}
+//#endregion
 //#region src/host/version.ts
 /**
 * Runtime harness-version probe behind the baseline gate (host/index.ts).
@@ -2422,6 +2501,7 @@ function apply(ctx, config) {
 		return;
 	}
 	const attribution = createToolAttribution(ctx);
+	watchStepIdentity(ctx);
 	const gate = watchDetailChannel(ctx, resolveBounds(config));
 	ctx.sessionProjections.register(createContextTimelineDefinition(config, () => gate.live));
 	ctx.sessionProjections.register(createContextHeadersDefinition((name) => attribution.ownerOf(name)));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-context",
-  "version": "0.44.0",
+  "version": "0.45.0",
   "description": "A DeepSeek Harness plugin for context insight and management, with context dashboard and context command, for understanding how the context is made of, and how it evolves.",
   "author": "bowenliang123",
   "repository": {