@mstar-harness/dsh 3.7.3 → 3.8.0

package/dist/types.d.ts

@@ -1,11 +1,16 @@
 /**
- * `mstar-engine-status` catalog source: a durable `catalog`-form
- * MessageSource the plugin appends to
- * every composed step at `agent/pre-step`, so the model-visible engine-status
- * row is reconstructable from the session log without re-parsing its prose
- * (model-visible ⟺ logged — dsh packages/AGENTS.md). Merge-extensible
- * `MessageSourceMap` augmentation mirroring the `@deepseek-ai/dsh-tool-skill`
- * precedent (declare module '@deepseek-ai/dsh-llm' + catalog-form source).
+ * `mstar-engine-status` catalog source + payload: the durable `catalog`-form
+ * MessageSource the plugin appends to every composed step at
+ * `agent/pre-step`, so the model-visible engine-status row is
+ * reconstructable from the session log without re-parsing its prose
+ * (model-visible ⟺ logged — dsh packages/AGENTS.md), plus the NON-persisted
+ * payload that row is rendered from.
+ *
+ * The source is the first-party `plugin` arm and nothing else: dsh freezes
+ * the source vocabulary per released session-format edge, so a custom `kind`
+ * or any extra `source` member makes a released edge refuse the whole session
+ * log. The structured facts live in
+ * {@link MstarEngineStatusPayload} instead.
  *
  * `mstar-iteration-gate` is the sibling catalog row: the boot-cached
  * `evaluatePhaseGate` verdict (tool result shape) appended after the
@@ -16,15 +21,29 @@
  */
 import type { EnforcementFlag } from '@mstar-harness/engine';
 /**
- * Durable provenance for the ONE unified engine-status catalog row. The
- * catalog is a `catalog`-form context, so it records the facts it published
- * beside the model-facing prose: a consumer presenting the row must not
- * re-parse the `<mstar_engine_status>` block, whose framing exists for the
- * model.
+ * The ONE unified engine-status catalog row's `source`: the first-party
+ * `plugin` arm with a CLOSED member set — exactly these three keys, never a
+ * fourth.
+ *
+ * `plugin` carries the plugin's identity literal and `form: 'catalog'` the
+ * row's first-party presentation; both are opaque, already-admitted
+ * vocabulary at every released session-format edge. Everything the row
+ * publishes about the workspace lives in
+ * {@link MstarEngineStatusPayload}, which never rides `source`.
  */
 export interface MstarEngineStatusSource {
-    readonly kind: 'mstar-engine-status';
+    readonly kind: 'plugin';
+    readonly plugin: 'mstar-engine-status';
     readonly form: 'catalog';
+}
+/**
+ * The engine-status payload the model-facing row is rendered from — the
+ * facts the catalog publishes BESIDE the prose (a consumer presenting the row
+ * must not re-parse the `<mstar_engine_status>` block, whose framing exists
+ * for the model). Deliberately NOT persisted on the message `source`: no
+ * released historical session-format edge admits extra `source` members.
+ */
+export interface MstarEngineStatusPayload {
     /**
      * The unified mstar version: the `@mstar-harness/dsh` plugin package
      * version (own manifest). The single-version invariant pins the bundled
@@ -187,7 +206,7 @@ export type WorkflowSelectionView = {
  * one-liner. All fields come from the same per-workspace cached build as
  * the rest of the row (one status.json / compass / knowledge-index read
  * per cache refresh — the TTL-bounded staleness tradeoff documented on
- * `buildCatalogSources`).
+ * `buildCatalogPayload`).
  */
 export interface MstarHarnessState {
     /**
@@ -332,8 +351,3 @@ export interface AgentFlowView {
     readonly events: readonly AgentFlowEventView[];
     readonly summary: readonly AgentFlowSummaryRow[];
 }
-declare module '@deepseek-ai/dsh-llm' {
-    interface MessageSourceMap {
-        'mstar-engine-status': MstarEngineStatusSource;
-    }
-}

package/harness-skills/mstar-artifacts/references/status-and-residuals.md

@@ -157,7 +157,7 @@ Body conventions (`## Direction` + goal items as `- [ ]` / `- [x]` markdown task
 
 ## Fail-loud handoff contract
 
-Findings must pass engine validation **before** registration into the project register: `validateResidual(entry)` per entry, `validateProjectRegister(doc)` for the whole register, `validateWorkflowSnapshot(doc)` for the snapshot, `validateStatus` for the v2 root (`mstar status validate <path>` / engine import). Malformed entries — **non-object**, missing any of the nine required fields (`id`, `title`, `severity`, `source`, `scope`, `decision`, `owner`, `target`, `tracking` — mirroring engine `RESIDUAL_REQUIRED_FIELDS` in `packages/engine/src/status.ts`), or **severity** outside the enum — are **rejected** (`ok:false` + violation): fix and rewrite — never silent pass-through, downgrade-write, or “write then patch”.
+Findings must pass engine validation **before** registration into the project register: `validateResidual(entry)` per entry, `validateProjectRegister(doc)` for the whole register, `validateWorkflowSnapshot(doc)` for the snapshot, `validateStatus` for the v2 root (`mstar status validate <path>` / engine import). Malformed entries — **non-object**, missing any of the nine required fields (`id`, `title`, `severity`, `source`, `scope`, `decision`, `owner`, `target`, `tracking` — mirroring engine `RESIDUAL_REQUIRED_FIELDS` in `packages/engine/src/status.ts`), or **`severity`** / **`decision`** outside their enums (`status.residual.invalid-severity` / `status.residual.invalid-decision`) — are **rejected** (`ok:false` + violation): fix and rewrite — never silent pass-through, downgrade-write, or “write then patch”. A *lifecycle* value such as `"resolved"` in `decision` leaves the **whole register unwritable** — `validateProjectRegister(doc)` then fails the document, so the engine refuses every subsequent write to that register, not just that entry.
 
 dsh-derived findings map their keys per the engine-residual validation verification spec §5; dsh keys never enter the schema.
 

package/harness-skills/mstar-host/references/dsh.md

@@ -36,7 +36,14 @@ or a custom profile).
   automatically by `ClientModuleHostService` — no separate profile layer or
   install step. It registers a **`conversation.view`** view-ring tab
   (`id: 'mstar-workflow'`, `order: 20`) labeled **"MStar 工作流" / "MStar
-  Workflow"** rendering the latest `mstar-engine-status` catalog row as the
+  Workflow"** rendering the latest `mstar-engine-status` catalog **anchor** row
+  — the persisted source is the bare first-party `plugin` arm
+  (`{ kind: 'plugin', plugin: 'mstar-engine-status', form: 'catalog' }`, no
+  payload members), and the payload is fetched from the host's
+  `/api/mstar/engineStatus` endpoint (the gateway owns the route; the browser
+  half calls `connection.rpc.call('/api', 'mstar/engineStatus', { args: { sessionId, cwd } })`
+  and renders the session's stored snapshot, or an explicit unavailable reason) —
+  as the
   **MStar Workflow layout** — a right sidebar (plans ≤5 in time-desc order +
   `+N more`, open residual findings ≤10 with severity chips + overflow hint,
   policy with **enforcement first** then push / worktree / control worktree,
@@ -208,9 +215,11 @@ or a custom profile).
   the zones stack vertically. Pure `projectGraph` projection (never throws,
   explicit degraded states — muted empty states, never orange warn boxes).
   The branches block left the sidebar in plan `20260810-panel-sidebar-info`
-  (its anchor fields stay in the catalog source; the iteration zone renders
-  them via plan `20260810-panel-canvas-zones`); refresh follows the session
-  snapshot, no polling — while the main agent is ACTIVELY orchestrating, a
+  (its anchor fields ride the row's per-session snapshot payload, NOT the
+  persisted source — the source is the bare first-party `plugin` arm; the
+  iteration zone renders them via plan `20260810-panel-canvas-zones`); refresh
+  follows the session snapshot, no polling — while the main agent is ACTIVELY
+  orchestrating, a
   ledger record (dispatch/settle) invalidates the workspace's TTL-cached
   catalog row so the next pre-step rebuilds and (digest text change)
   re-injects it, and the panel refreshes per step (seconds, not the 60 s TTL);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mstar-harness/dsh",
-  "version": "3.7.3",
+  "version": "3.8.0",
   "description": "Morning Star harness dsh (DeepSeek Harness) cordis function plugin — in-process engine gates (status/dispatch/lease) with hard refusal channels.",
   "keywords": [
     "dsh",
@@ -47,7 +47,8 @@
       "inject": [
         "@deepseek-ai/dsh-client-store",
         "@deepseek-ai/dsh-client-ui-conversation",
-        "@deepseek-ai/dsh-client-locale"
+        "@deepseek-ai/dsh-client-locale",
+        "@deepseek-ai/dsh-client-connection"
       ],
       "platform": "web"
     }
@@ -56,6 +57,7 @@
     "pretest": "bun run build-client",
     "test": "bun test",
     "typecheck:tests": "bunx tsc --noEmit -p tests/tsconfig.json",
+    "typecheck:src": "bunx tsc --noEmit -p tsconfig.json",
     "bundle-assets": "bun run scripts/bundle-harness-assets.ts",
     "build": "bun run bundle-assets && rm -rf dist && bun build src/index.ts src/invariant.ts --target node --outdir dist --external @deepseek-ai/cordis --external @deepseek-ai/dsh-skill-filesystem --external @deepseek-ai/dsh-tools --external @deepseek-ai/dsh-llm && bun run build-client && bunx tsc",
     "build-client": "bun run scripts/build-client-bundle.ts",