@mstar-harness/dsh 3.7.3 → 3.8.1

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` 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,36 @@
  */
 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 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`.
+ *
+ * The `plugin` union is the PERSISTED-LOG vocabulary, not a write-time
+ * choice: the plugin emits `mstar-engine`, while rows emitted by shipped
+ * builds before 2026-09-11 persist `mstar-engine-status` in already-written
+ * session logs. Both are valid persisted rows; the panel's anchor reader
+ * accepts both (data compat for persisted session logs, not a code-compat
+ * layer).
  */
 export interface MstarEngineStatusSource {
-    readonly kind: 'mstar-engine-status';
+    readonly kind: 'plugin';
+    readonly plugin: 'mstar-engine' | '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 +213,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 +358,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

@@ -34,217 +34,94 @@ or a custom profile).
 - Web client plugin (workflow panel): the same `mstar` bundle row carries a
   browser client half (`dsh.client` + `exports["./client"]`) discovered
   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
-  **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,
-  leases, knowledge, direction) over a bottom **fixed meta dock** (version +
-  harness dir; small muted, hairline-separated, does NOT scroll with the
-  sidebar digest — the former header row was removed), and an **HTML/CSS zone
-  dashboard** (the react-flow cyclic graph was removed in plan
-  `20260810-panel-canvas-zones`): the canvas fills the Tab (the page never
-  scrolls; the zone container is the only scroll body) with an **iteration
-  zone** (Step 1–5 stepper + `Step N/5` badge + active-highlight / inactive
-  dimmed state; the steps carry a FOUR-STATE machine — `current` / `next` /
-  `done` / `idle` (plan `20260812-panel-f5-iteration-zone-fix` Task 1): every
-  step BEFORE the current one projects `done`「已完成」(completed — a finished
-  Step 1 must not read as idle while Step 2 is current), `next` is the single
-  forward target, `idle` is schema-only + the branch panel — iteration base /
-  target / spec integration, rendered only while active; the expanded head is
-  a LEFT-RIGHT SPLIT — branches (small left half, WIDTH-CAPPED — `flex: 0 1
-  260px` + `max-width: 280px`, never stretches with the container; the <860px
-  column stack resets to content height) + steps (large right half, `flex: 1 1
-  0` absorbing the remaining width) via `data-iteration-head-split`, stacking
-  on narrow widths, and NO branch panel
-  when there is no active iteration; the current step follows the steering
-  compass: `compassStatus: 'active'` (Phase 1 in flight) → Step 1
-  (iteration-start) is CURRENT with verdict `unknown` — no PASS/FAIL badge,
-  plan `20260811-panel-f4-iteration-zone`; **the iteration info section is
-  SHARED by the tasks AND agents tabs** (plan
-  `20260812-panel-f5-design-system` Task 8, user round-4 decision #4 — one
-  `IterationInfoSection` component, both tabs render the same `view.iteration`
-  block: summary + steps + branches), a **tasks zone** (5-column
-  kanban: Todo / InProgress / InReview / Done / `blocked-unknown` — the
-  Blocked state and the former `unknown` catch-all fold into ONE merged
-  column titled「受阻/未知」/「Blocked / Unknown」, plan
-  `20260813-panel-quick-fixes` Task 1 — with count badges; every column
-  caps its rendered rows at `PLAN_CAP` and shows a clickable 「更多」/「收起」
-  expand button (`data-kanban-more` anchor) unfolding the full column — the
-  projection keeps ALL plan rows, the cap is a render concern never a
-  discard), an **agent-execution zone** (the FOUR EXPECTED_ROLE_FLOW stage/phase
-  columns — review-edit-chain → sdd-implement → qc-tri → qa-gate, the
-  terminal stage; the former `sdd-task-review` stage is removed and its SDD
-  L2 reviewer is now the PIPELINE role `code-reviewer` (v2.1.1, the former
-  `generalPurpose` seat) — a strict FOUR-column layout with NO standalone
-  unknown column (plan `20260812-panel-f5-design-system` Task 5, user
-  2026-08-12 round-2 decision — the former rightmost UNKNOWN column of plan
-  `20260812-panel-f5-agent-layout` is superseded): the `general` bucket
-  sinks into an **unknown SUB-PARTITION at the bottom of the `qa-gate`
-  column** (a `data-sub-bucket="unknown"` caption row 「unknown / 未匹配角色」
-  after the last qa-gate card, then the general cards; the standalone
-  on-demand column was already removed in the agent-layout plan); `explore`
-  is removed — no card, no column. The columns are laid out in **TWO
-  side-by-side Phase groups** (plan `20260812-panel-f5-design-system` Task 8,
-  user round-4 decision #2; side-by-side layout per plan
-  `20260813-panel-agent-canvas-legend-layout` Task 2): the **Phase 1 group
-  on the LEFT** (review-edit-chain — the sequential Review & Edit chain:
-  product-manager → architect → writing-specialist) and the **Phase 2 group
-  on the RIGHT** (sdd-implement → qc-tri → qa-gate — the iterative plan
-  loop), top-aligned (all group label rows share the same `y = PAD_Y`), each
-  with its group label row; the **Phase-2 label annotates the CURRENT PLAN**
-  (projected `agents.activePlanId` = the first InProgress `state.plans[]`
-  row, `data-canvas-group-plan`; `+N more` when several plans run in
-  parallel, muted「无进行中 plan」when none). The `sdd-implement` column is split into SUB-BUCKETS by
-  the PROJECTED `entity.bucket` (never a render guess): the **implementor**
-  partition ABOVE — the flow roles in the stage's original order
-  (fullstack-dev / fullstack-dev-2 / frontend-dev), then the on-demand
-  roles (ops-engineer / prompt-engineer, carrying the **on-demand badge** —
-  the standalone on-demand column is gone) — and the **sdd-reviewer**
-  partition BELOW (code-reviewer, idle included), with the implementor /
-  sdd-reviewer caption labels; `zone: 'on-demand'` entities live in the
-  implementor partition, `zone: 'general'` entities render in the qa-gate
-  column's bottom unknown sub-partition. The subagent ENTITY cards aggregate **by role** from actual
-  dispatch evidence: the same role across sessions folds into one card ×N,
-  and every off-roster dispatch (the former `generalPurpose` SDD reviewer,
-  `scout`, anonymous `role === ''`) folds into the single `general` bucket
-  entity — the card is ROLE-TITLED (the role id, e.g. `fullstack-dev`); the
-  agent session id / task tag (`planId#taskId`) ride the RECORD line, never
-  the title. Cards show the role chip / status point / ×N count; running
-  entities carry the business glow-pulse
-  highlight, un-evidenced stages render the dashed "待执行" pending
-  placeholder with their expected role chips, un-evidenced KNOWN_AGENTS
-  members render dashed idle cards (the full 14-role roster is never
-  hidden), and the header shows the `N executing · M pending` summary.
-  Cards carry the projected **emphasis tier** (plan
-  `20260812-panel-f5-design-system` Task 4, design doc §3): `emphasis:
-  'current' | 'next' | 'off' | null` — the iteration's current-phase roles
-  render at **100%** chrome intensity, later-phase expected roles at **75%**,
-  already-passed / stage-less (on-demand, general) roles at **45%**, and
-  `null` (no iteration / unresolved transition) applies NO override — always
-  a chrome **alpha mix** (`--mstar-canvas-emphasis-*` tokens; never a
-  whole-card `opacity`, so the status point + running glow stay opaque).
-  Settled entities get a **standalone GREEN done frame + green ✓** (plan
-  `20260812-panel-f5-design-system` Task 8, user round-4 decisions #1/#3:
-  `data-agent-done="true"` — a full-strength success border + 1px ring on
-  the rounded card body + the ✓ in the status point) **ONLY when
-  `emphasis ≠ 'off'`** — an off-tier role (already-passed / stage-less
-  on-demand + general) renders the muted dot instead and NEVER shows the
-  completion marker (the completed state never appears on a stage-less
-  role). The canvas filters to the CURRENT iteration only (plan
-  `20260813-panel-quick-fixes` Task 2): dispatch evidence projects for the
-  current iteration's plans — the steering compass `iterationId` when
-  active, else the nearest iteration derived from the catalog
-  `plans[].iterationRefs` (the most-recent plan's refs by 8-digit id date
-  prefix + doneAt); provably cross-iteration events produce no entity/edge
-  (the roster keeps its idle cards); plan-less / unknown-plan / standalone
-  dispatches are never hidden. Status honesty (Task 2): `advisory` is NO
-  LONGER terminal — a soft-enforcement dispatch falls through to its paired
-  settle (green ✓ when a settle exists, `running` when none) while `denied`
-  stays terminal; the advisory verdict still renders in the event log. The
-  canvas legend sits BELOW the viewport (Task 3 — moved from above, user
-  2026-08-13 feedback).
-  Edges (plan `20260812-panel-f5-design-system` Task 5, design doc §2):
-  the `expected` stage skeleton arrows AND the ANIMATED **next** edge (the
-  former `@keyframes agent-dash-flow` dash-flow arrow of plan
-  `20260810-panel-agent-flow-zone`) are **REMOVED** — flow order is implied
-  by the fixed column order + column labels, the current position by the
-  running card glow + status point — leaving TWO semantic kinds: the
-  evidence-driven **`actual` handoff** edges (same-plan ts-adjacent dispatch
-  entity-key pairs, `general` endpoints filtered, ≤1 per entity pair) drawn
-  as **bezier `C` curves** anchored to card **PORTS** — 4 fixed
-  edge-midpoint ports (north / south / east / west; static-invisible,
-  hover-revealed as small dots) with the arrow tip pulled back to a **10px
-  standoff** off the port — the arrow follows the line's local tangent at
-  the anchor (**H1**), and no line's stroke or arrow crosses any text
-  (**H2**: standoff + side-gap routing, design doc §2.0/§2.5/§2.6;
-  tightened in plan `20260813-panel-quick-fixes` Task 3 — same-column
-  vertical flows whose center-x line would cross an in-between card body
-  (e.g. fullstack-dev → frontend-dev skipping an idle fullstack-dev-2)
-  reroute into the column's LEFT side gap, forward AND reverse, and reverse
-  horizontal beziers keep direction-aware control points BETWEEN the
-  endpoints so they never bulge into the adjacent column) — plus
-  the **bidirectional supervise line** (plan `20260812-panel-f5-agent-layout`
-  Task 1/2) — ONE static design-knowledge sub-bucket edge inside the
-  `sdd-implement` column (implementor ↔ sdd-reviewer — the mstar-sdd
-  mutual-supervision contract), now anchored at the **side-gap vertical
-  anchor** (`x = card right edge + 18px`, vertical bezier flow, arrows along
-  the vertical tangent — design doc §2.5/§2.7); dim dashed by default, lit
-  business SOLID when the projected `evidenced` flag is true —
-  evidence-driven lighting, never a fabricated activation); the 事件记录 tab
-  (`EventLogPage`, spec panel-tabs §5, plan `20260811-panel-event-log`) is a
-  NON-canvas log page with two partitions — **Agent 流转事件** (`view.events`
-  ≤50 latest-first; off-pipeline unexpected dispatches fold in once via
-  `expected: false` and carry a dispatch-only 「未匹配角色」 badge — settle
-  rows are completion records and never flag as unexpected) and **违规记录**
-  (`view.violations`, gate violations with severity/code/message); every row
-  is an expandable native `<details>` (no-JS, keyboard-accessible) whose body
-  shows the full catalog fields — missing fields render「—」, never a guessed
-  value. Layout (plan `20260811-panel-f3-agent-general`): the two partitions
-  render SIDE BY SIDE in a locked-height two-column grid
-  (`repeat(2, minmax(0, 1fr))` — the page never scrolls as a whole; each
-  partition pins its title and owns an internal `overflow-y` scroll on its
-  row list; plan `20260813-panel-quick-fixes` Task 4 root-caused the
-  whole-page scroll — the panel root opts into the host
-  `data-conversation-composer-overlay` (the host's documented full-height
-  opt-in), so the host `.viewArea` becomes a definite-height container and
-  `height:100%` resolves: `.rowList`'s `overflow-y: auto` now scrolls
-  INSIDE the partition and the host page no longer scrolls, with bottom
-  clearance reserving the floating composer via the host-published
-  `--dsh-composer-height`), falling back to two stacked 50/50 locked rows
-  below 1200px —
-  the `data-event-log-*` anchor family is unchanged. The canvas-corner **`AgentEventDock`** is REMOVED with the page
-  (无双份日志 — its row layout + status chips migrated into `EventLogPage`);
-  the fixed footer bar (zone legend + gate summary + violations) died with
-  the WorkflowCanvas in plan `20260811-panel-tabs-shell` — the footer that
-  remains is the freshness marker. Empty branches (spec §2 — plan
-  `20260812-panel-f5-agent-layout` Task 3): waiting keeps the muted hint,
-  and NO harness renders a **CENTERED inactive-state card** (folder icon +
-  「No Morning Star harness detected」 title + the hint copy — the detail
-  panel stays inactive, no tabs / no sidebar, activating automatically once
-  a harness is detected; the `data-mstar-empty="no-harness"` anchor stays on
-  the title, `data-mstar-graph` on the main container). Below 1200px
-  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
-  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);
-  while the main agent IDLES (waiting, no tool calls) the panel keeps the
-  LAST snapshot — no live push channel (documented limit, plan
-  `20260811-panel-f4-timeliness`). Bundle served at
-  `/plugins/@mstar-harness/dsh/client.js` (closure-factory CJS with NO graph
-  library inlined — react-flow removed; the build asserts the bundle contains
-  no `xyflow`/`reactflow` markers, no `@deepseek-ai/*` value imports, and no
-  `import.meta` / ESM statements — the loader runs plugin bundles as classic
-  scripts). **Known limitations**: the stepper's Step 1 (iteration-start) IS
-  the current step while the steering compass is `status: active` (Phase 1 in
-  flight — catalog `compassStatus` field), carrying NO PASS/FAIL badge (Phase
-  1 has no gate verdict); Step 5 (merge-ready) can never be the CURRENT step —
-  the engine phase gate only evaluates Phase 2→3→4 (merge-ready is never a gate
-  transition); it renders `next` only while Step 4 (pr-delivery) is current,
-  idle otherwise;
-  the current step follows the TTL-refreshed `compassStatus` — up to one
-  catalog interval (60 s) behind a mid-session `active`→`locked` flip (bounded,
-  documented staleness, never a wrong verdict); the agent-entity
-  status derivation pairs a PAIRED settle exactly by its dispatch identity
-  (`agent`, `role`, `planId`, `taskId` — under QC-tri N=3 concurrency each
-  settle lands on ITS dispatch), and an unpaired dispatch stays `running`
-  (no paired settle — never guessed, never faked); the current-iteration
-  filter with NO steering compass infers the iteration from plan ids
-  (8-digit date prefix) + doneAt — deterministic, documented heuristic, and
-  only provably cross-iteration events are dropped; no historical back-scan of
-  resumed long logs; no custom
-  top-level slot (the `conversation.view` tab is the only session-level panel
-  seat without dsh-private layout changes); no-session → shell hero
-  (strict-session view ring). Panel acceptance is dual-track: in-loop browser
-  harness verification (agent-browser/CDP against the rebuilt bundle,
-  iteration guides record the verified runs) plus user-restart final GUI
-  acceptance.
+  install step. It registers a **right-Sidebar page tab type** (`id:
+  '@mstar-harness/dsh'`, `kind: 'mstar-workflow'`, one guide-page capsule at
+  `order: 20`) labeled **"启明星工作流" / "Morning
+  Star Workflow"** rendering the latest `mstar-engine` catalog **anchor** row
+  — the persisted source is the bare first-party `plugin` arm
+  (`{ kind: 'plugin', plugin: 'mstar-engine', form: 'catalog' }`, no
+  payload members; the anchor reader also accepts the legacy
+  `mstar-engine-status` identity from persisted logs), 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). **Morning Star Workflow layout**: a narrow-column shell bound to the
+  sidebar pane's definite height — exactly three zones: the **section nav**
+  (任务迭代 / 代理执行 / 事件记录; `data-mstar-tab-nav`), the panel-owned
+  **single scroll body** (`[data-mstar-scroll]` — the ONLY `overflow-y`
+  element in the panel; nothing scrolls horizontally; `data-mstar-graph`
+  rides it), and the pinned **meta dock** (version + harness dir; never
+  scrolls). The workspace-state digest (plans ≤5 time-desc + `+N more`,
+  open residual findings ≤10 with severity chips + overflow hint, policy
+  with **enforcement first** then push / worktree / control worktree,
+  leases, knowledge, direction) renders IN FLOW at the end of the scroll
+  body, closed by the freshness footer (`snapshot {time} · turn {turn}` —
+  the served snapshot's own timestamp + turn, never "live"). The three
+  sections stack in the scroll body: the tasks page (iteration head +
+  **vertical** 5-step stepper with the FOUR-STATE `current` / `next` /
+  `done` / `idle` machine + the branch panel + five stacked status groups
+  — the merged「受阻/未知」/「Blocked / Unknown」column kept, `PLAN_CAP`
+  render caps + the clickable 「更多」/「收起」 expand button
+  (`data-kanban-more`); the projection keeps ALL plan rows — then the
+  project rollup), the events page (two partitions — Agent 流转事件 /
+  违规记录 — as flow rows, every row an expandable native `<details>`
+  carrying the full catalog fields, missing fields render 「—」 never a
+  guessed value), and the agents page — a **vertical grouped list** (the
+  react-flow canvas, its SVG edge layer, card ports and pointer pan are
+  REMOVED): two Phase groups in constant order (Phase 1 review-edit-chain
+  above; Phase 2 sdd-implement → qc-tri → qa-gate below, its label
+  annotating the CURRENT plan — `data-agent-group-plan` + `+N more`),
+  `sdd-implement` split into implementor / reviewer sub-partitions, the
+  `general` bucket sunk into an `unknown` sub-bucket, the full 14-role
+  roster as full-width flow rows (idle rows dashed muted — the roster is
+  never hidden) with role chip / status point / `×N` count / record line,
+  the `N executing · M pending` summary, and the three-entry legend in
+  flow below the list; rows carry the projected **emphasis tier**
+  (`--mstar-canvas-emphasis-*` chrome alpha mix — never a whole-row
+  `opacity`, so the status point + running glow stay opaque), settled
+  entities get the standalone GREEN done frame + ✓
+  (`data-agent-done="true"`) ONLY when `emphasis ≠ 'off'`; the agents page
+  contains zero `<svg>`, zero `data-agent-port` / `data-canvas-*` anchors
+  and no pan transform. The **iteration info section is shared by the
+  tasks AND agents pages** (one `IterationInfoSection`, both render the
+  same `view.iteration` block). Empty branches are explicit states —
+  `waiting` / `loading` / `unavailable` (with its reason) / no-harness
+  each carry their OWN anchor and copy and render no tabs, no digest and
+  no meta dock; no harness renders a CENTERED inactive-state card that
+  activates automatically once a harness is detected (inside the same
+  single scroll zone). Projection is the pure `projectGraph(source)`
+  function (schema constants vs catalog evidence strictly separated; never
+  throws; explicit degraded states — muted empty states, never orange warn
+  boxes). 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); while the main agent IDLES the
+  panel keeps the LAST snapshot — no live push channel. Bundle served at
+  `/plugins/@mstar-harness/dsh/client.js` (closure-factory CJS with NO
+  graph library inlined — react-flow removed; the build asserts the bundle
+  contains no `xyflow`/`reactflow` markers, no `@deepseek-ai/*` value
+  imports, and no `import.meta` / ESM statements — the loader runs plugin
+  bundles as classic scripts). Full realized layout detail:
+  `packages/dsh/README.md` (§ Web client plugin). **Known limitations**:
+  the stepper's Step 1 (iteration-start) IS the current step while the
+  steering compass is `status: active` (Phase 1 in flight — catalog
+  `compassStatus` field), carrying NO PASS/FAIL badge (Phase 1 has no gate
+  verdict); Step 5 (merge-ready) can never be the CURRENT step — the
+  engine phase gate only evaluates Phase 2→3→4; the current step follows
+  the TTL-refreshed `compassStatus` — up to one catalog interval (60 s)
+  behind a mid-session `active`→`locked` flip (bounded, documented
+  staleness, never a wrong verdict); the agent-entity status derivation
+  pairs a PAIRED settle exactly by its dispatch identity (`agent`, `role`,
+  `planId`, `taskId`), and an unpaired dispatch stays `running` (never
+  guessed, never faked); with NO steering compass the current-iteration
+  filter infers the iteration from plan ids (8-digit date prefix) +
+  doneAt — deterministic, documented heuristic, only provably
+  cross-iteration events are dropped, no historical back-scan of resumed
+  long logs; the sidebar chip title is captured at open time; a docked
+  body renders nothing while `tab.visible === false`. Panel acceptance is
+  dual-track: in-loop browser harness verification against the rebuilt
+  bundle plus user-restart final GUI acceptance.
 
 ## Skill loading
 
@@ -315,10 +192,8 @@ build (`catalogTtlMs`, default 60 s).
 
 The plugin records ACTUAL subagent dispatch and real-completion settle events —
 the evidence of what really happened, distinct from the client-side expected
-role flow. The workflow panel's agent-execution zone (the stage/entity
-projection — plan `20260810-panel-agent-flow-zone`) and the 事件记录 tab's
-`EventLogPage` log page (plan `20260811-panel-event-log`) are pure consumers
-of this evidence.
+role flow. The workflow panel's 代理执行 (agents) page and the 事件记录
+tab's `EventLogPage` log page are pure consumers of this evidence.
 
 - **Recording point (one core)**: `DshHostAdapter.dispatchGate` is the SINGLE
   record path behind both dispatch surfaces — the `tools/pre-execute` listener
@@ -346,8 +221,8 @@ of this evidence.
   summary. A MISSING file reads as the empty view ("no actual dispatches yet"
   — recording starts at plan merge); an unreadable file is absent evidence;
   malformed lines are skipped, never fatal.
-- **Settle = real completion pairing, never faked** (plan
-  `20260811-panel-f4-timeliness`): `tools/post-execute` IS part of the
+- **Settle = real completion pairing, never faked**: `tools/post-execute`
+  IS part of the
   verified dsh-tools registry surface (`runPostExecute` dispatches the
   waterfall for every tool call — verified against the upstream source and
   pinned by a real-call probe). The pairing listener matches dispatch TOOLS
@@ -377,8 +252,8 @@ of this evidence.
   top-5 + latest dispatch with HH:MM — the event detail lives in the
   structured source, never the model text). A ledger record (dispatch/settle)
   invalidates the affected workspace's TTL cache entry IMMEDIATELY
-  (apply-scoped `harnessDir → cache key` reverse map + invalidation closure,
-  plan `20260811-panel-f4-timeliness`) → the next pre-step rebuilds and (digest
+  (apply-scoped `harnessDir → cache key` reverse map + invalidation closure)
+  → the next pre-step rebuilds and (digest
   text change) re-injects the row — the 60 s TTL no longer bounds
   ledger-change latency; it still bounds non-ledger staleness.
 - **Maintainer view**: change the ledger shape (event schema, bounds, settle