@mstar-harness/dsh 2.1.1

package/dist/client/panel/graph/schema.d.ts

@@ -0,0 +1,224 @@
+/**
+ * Graph schema constants (spec panel-layout-graph §2.0): the workflow loop
+ * (phase ring — mstar-iteration Phase 1–5) and the per-plan status machine
+ * (mstar-plan-artifacts) are CLIENT-SIDE DESIGN KNOWLEDGE. They are written
+ * once here with their provenance and STRICTLY SEPARATED from catalog
+ * evidence (`iteration.gate.transition` / `state.plans[].status`), which
+ * `projectGraph` projects onto this skeleton.
+ *
+ * Known limitation (spec §2.3 — a documented constraint, not a defect): the
+ * engine phase gate only evaluates Phase 2→3→4, so the catalog never emits
+ * `merge-ready` as current — Step 5 stays schema-only idle. Step 1
+ * (`iteration-start`) IS compass-driven current during Phase 1 — the
+ * `compassStatus: 'active'` field (plan 20260811-panel-f4-iteration-zone)
+ * lights it, so it is NOT a "never current" node; only Step 5 has no source
+ * that can light it. The loop edge is planning semantics (one iteration
+ * closes, the next begins).
+ */
+/** Phase ring node ids in loop order (spec §2.3). */
+export declare const PHASE_IDS: readonly ["iteration-start", "autonomous-execute", "iteration-close", "pr-delivery", "merge-ready"];
+export type PhaseId = (typeof PHASE_IDS)[number];
+/** Plan state machine bucket ids (spec §2.4): 4 known states + the merged
+ * `blocked-unknown` catch-all (plan 20260813-panel-quick-fixes Task 1 — the
+ * `Blocked` state and the former `unknown` catch-all fold into ONE column). */
+export declare const PLAN_STATE_IDS: readonly ["Todo", "InProgress", "InReview", "Done", "blocked-unknown"];
+export type PlanStateId = (typeof PLAN_STATE_IDS)[number];
+export interface PhaseEdge {
+    source: PhaseId;
+    target: PhaseId;
+    kind: 'forward' | 'loop';
+}
+/** Phase ring edges: forward start→…→merge-ready, plus the loop merge-ready→start (spec §2.3). */
+export declare const PHASE_EDGES: PhaseEdge[];
+/** Plan state machine edges (spec §2.4): `Done` is terminal (no out-edges);
+ * `blocked-unknown` keeps the InProgress↔Blocked recovery back-edge (plan
+ * 20260813-panel-quick-fixes Task 1 — the merged column docks the Blocked ⇄). */
+export declare const PLAN_STATE_EDGES: {
+    source: PlanStateId;
+    target: PlanStateId;
+}[];
+/** `gate.transition` → phase id (spec §2.3): the engine emits only these three. */
+export declare const TRANSITION_TO_PHASE: Readonly<Record<string, PhaseId>>;
+/**
+ * Expected role pipeline (spec agent-flow-catalog-graph §2.3): WHO is expected
+ * to be dispatched in each iteration phase. Like the phase ring / plan state
+ * machine above, this is CLIENT-SIDE DESIGN KNOWLEDGE — written once with its
+ * provenance and STRICTLY SEPARATED from catalog evidence: `projectGraph`'s
+ * flow projection lights this skeleton with `state.agentFlow` dispatch events
+ * (stage lit/count) and flags events whose role is NOT in this union
+ * (unexpected — e.g. `general` / `scout` or unregistered roles).
+ *
+ * Provenance (mstar role vocabulary — exact strings, dispatch order):
+ * - review-edit-chain: product-manager → architect → writing-specialist —
+ *   the mstar-iteration §1.6 Review & Edit chain (Prepare-phase design
+ *   review, Phase 1).
+ * - sdd-implement: fullstack-dev / fullstack-dev-2 / frontend-dev /
+ *   code-reviewer — the mstar-sdd implementer roles PLUS the L2 task
+ *   reviewer `code-reviewer` (v2.1.1, upstream roles.ts SSOT — the former
+ *   `generalPurpose` seat; Phase 2 task execution + per-task review).
+ * - qc-tri: qc-specialist ×3 — the mstar-sdd plan QC triage (Phase 2).
+ * - qa-gate: qa-engineer — the QA gate (Phase 2 closing — the pipeline
+ *   TERMINAL stage; ops-engineer is NOT in the pipeline).
+ * - Phase 3–5 (iteration-close / pr-delivery / merge-ready) dispatch no
+ *   routine subagents → no stages (spec §2.3).
+ *
+ * Off-pipeline roles (plan 20260811-panel-f3-agent-general) live in the
+ * KNOWN_AGENTS roster with `zone` markers, NOT here: `ops-engineer` and
+ * `prompt-engineer` are on-demand dispatches (mstar-roles routing table,
+ * as needed) — they stay OUTSIDE this union (their event-log `unexpected`
+ * badge is unchanged; bucket membership and expectedness are ORTHOGONAL
+ * dimensions — plan 20260812-panel-f5-agent-layout Task 1, see
+ * SDD_BUCKET_ROLES). The single `general` bucket (plan
+ * 20260811-panel-f3-agent-general) collects every unmatched / anonymous
+ * dispatch (role ''), plus stray off-roster roles like `scout`; the SDD
+ * per-task reviewer is now the PIPELINE role `code-reviewer` (v2.1.1 — the
+ * former `generalPurpose` seat), so the `general` bucket no longer
+ * describes a pipeline seat.
+ *
+ * General-bucket PLACEMENT (plan 20260812-panel-f5-agent-layout Task 1 —
+ * user 2026-08-12 decision): the `general` bucket moves to its OWN rightmost
+ * UNKNOWN column — the projection still emits `zone: 'general'` entities
+ * (semantics unchanged, placement is a RENDER-layer decision), and the
+ * render (Task 2) places them in that rightmost column. The earlier F4.2
+ * placement (BOTTOM INSIDE the `sdd-implement` column bucket) is
+ * superseded by the F5 user decision; the former SDD implement ↔ review
+ * skeleton EDGE (sdd-implement → general back-edge, the `loop: true` arrow)
+ * stays REMOVED from the projection (plan 20260811-panel-f4-agent-view Task
+ * 1); the F5 supervise line is a SEPARATE sub-bucket edge (see
+ * project-graph.ts `superviseEdges`).
+ *
+ * Matching rules (spec §2.3 — implemented by `projectGraph`'s flow
+ * projection): `expected` ⟺ `event.role` ∈ the union of ALL `roles` below
+ * (EXACT string — `qc-specialist-2` never folds into `qc-specialist`); a role
+ * listed in several stages matches the FIRST stage in this constant order;
+ * `unexpected` ⟺ role ∉ union. Settle rows carry no role (T1 sets ''), so
+ * they never match a stage.
+ */
+export interface ExpectedRoleStage {
+    /** The iteration phase this pipeline stage belongs to (PhaseId union). */
+    phase: PhaseId;
+    /** Pipeline-stage id — the render + match key (`${phase}:${stage}`). */
+    stage: string;
+    /** Expected role ids in dispatch order (mstar-roles / mstar-sdd vocabulary). */
+    roles: readonly string[];
+}
+/** Expected role pipeline skeleton: 4 stages (spec agent-flow-catalog-graph
+ * §2.3; plan 20260812-panel-f5-agent-layout Task 1 — `code-reviewer` joins
+ * the sdd-implement stage: v2.1.1 makes the SDD L2 task reviewer a routine
+ * pipeline role, the former `generalPurpose` seat; ops-engineer /
+ * prompt-engineer stay OFF the pipeline — on-demand; qa-gate is the
+ * terminal stage). */
+export declare const EXPECTED_ROLE_FLOW: readonly ExpectedRoleStage[];
+/**
+ * SDD sub-bucket membership (plan 20260812-panel-f5-agent-layout Task 1 —
+ * CLIENT-SIDE DESIGN KNOWLEDGE): which roles live in which sub-bucket of the
+ * `sdd-implement` column — `implementor` (the implementer roles PLUS the
+ * on-demand ops-engineer / prompt-engineer: they are implementor-family
+ * dispatches, not a separate stage) and `reviewer` (code-reviewer, the SDD
+ * L2 task reviewer — v2.1.1, upstream roles.ts SSOT).
+ *
+ * ORTHOGONAL to expectedness: sub-bucket membership is a LAYOUT dimension,
+ * the `expected` badge follows the EXPECTED_ROLE_FLOW union (a separate
+ * dimension). `implementor` ⊇ the sdd-implement union roles (it also holds
+ * ops-engineer / prompt-engineer, which stay OUTSIDE the union — their
+ * event-log `unexpected` badge is unchanged); `reviewer` ⊆ the union. Do NOT
+ * add on-demand roles to EXPECTED_ROLE_FLOW.roles to "fix" their badge —
+ * that would silently flip it (compass Non-Goal: no event-log classification
+ * changes).
+ */
+export declare const SDD_BUCKET_ROLES: {
+    implementor: readonly string[];
+    reviewer: readonly string[];
+};
+/**
+ * The known-agent roster (spec §4 / §6.2 / decision point D3 + plan
+ * 20260811-panel-f3-agent-general + plan 20260812-panel-f5-agent-layout Task
+ * 1): the static FULL set of ASSIGNABLE roles the panel may ever show —
+ * every EXPECTED_ROLE_FLOW role PLUS the off-pipeline roles `prompt-engineer`
+ * (in the mstar-roles table but not in the pipeline) and `ops-engineer`
+ * (on-demand ops dispatch), PLUS `general` (the single general bucket — see
+ * below). Exactly 14 roles (upstream v2.1.1 roles.ts = 13 assignable +
+ * project-manager is the semantic SSOT — the roster adds `code-reviewer`,
+ * the SDD L2 task reviewer, to reach 14).
+ *
+ * `explore` is DELIBERATELY NOT in the roster (plan
+ * 20260811-panel-f3-agent-general — user F3 feedback): it is a scouting
+ * adjunct role with no standalone presentation value, so it is removed from
+ * the canvas (a stray `explore` dispatch still folds into the `general`
+ * bucket — it is not a KNOWN_AGENTS id).
+ *
+ * `project-manager` is deliberately NOT in the roster (plan
+ * 20260811-panel-f2-quickfix Item 2 — user F2 feedback): it is the PRIMARY
+ * orchestration agent (mstar-roles mapping `mode: primary`), the seat that
+ * DISPATCHES subagents — never an assignable subagent itself, so it must
+ * not appear as a dispatchable entity in the 代理执行 tab.
+ *
+ * The panel NEVER hides a known agent: every member without dispatch
+ * evidence projects as an `idle` entity (spec §6.2 — degraded/empty
+ * branches included). `stage` = the role's stage in EXPECTED_ROLE_FLOW
+ * (first constant-order match); null for the off-pipeline roles, which
+ * carry an explicit `zone` — `on-demand` (ops-engineer / prompt-engineer:
+ * implementor-sub-bucket dispatches with an on-demand badge — the render
+ * places them inside the `sdd-implement` column's implementor partition,
+ * Task 2) or `general` (the general bucket = ANY unmatched / anonymous
+ * dispatch (role '') in the projection — the rightmost UNKNOWN column,
+ * Task 2).
+ *
+ * General-bucket placement (plan 20260812-panel-f5-agent-layout Task 1,
+ * user 2026-08-12): the `general` bucket gets its OWN rightmost unknown
+ * column — the projection keeps emitting `zone: 'general'` entities (the
+ * zone VALUE is unchanged — placement is a render-layer decision, Task 2).
+ */
+/** The general-bucket id (plan 20260811-panel-f3-agent-general): the single
+ * bucket every off-roster / anonymous dispatch folds into — the former SDD
+ * per-task reviewer seat is now the PIPELINE role `code-reviewer` (v2.1.1),
+ * so `general` is purely the unmatched/anonymous catch-all (role '' +
+ * stray roles like `scout`). Single source for the value:
+ * `entityKeyOf`'s fallback key, `roleZone` / `idleZone` defaults and the
+ * KNOWN_AGENTS roster id ALL derive from it — renaming the bucket changes
+ * exactly one constant.
+ *
+ * Placement (plan 20260812-panel-f5-agent-layout Task 1, user 2026-08-12):
+ * the bucket gets its OWN rightmost UNKNOWN canvas column — the render
+ * (Task 2) places `zone: 'general'` entities there; the former F4.2
+ * placement (BOTTOM INSIDE the `sdd-implement` column) is superseded. The
+ * `'general'` literal in the `AgentZone` / `KnownAgent.zone` unions below
+ * is the type-level binding (a union member cannot reference a value) —
+ * keep them in sync with this constant. */
+export declare const GENERAL_BUCKET: "general";
+/**
+ * Agent-entity column zone (plan 20260811-panel-f3-agent-general + plan
+ * 20260812-panel-f5-agent-layout Task 1): `'flow'` (stage columns),
+ * `'on-demand'` (ops-engineer / prompt-engineer — implementor-sub-bucket
+ * dispatches, rendered inside the `sdd-implement` column's implementor
+ * partition with an on-demand badge; the standalone on-demand column is
+ * REMOVED — Task 2) or `'general'` (the general bucket). Placement
+ * semantics (user 2026-08-12 decision): `'general'` renders in its OWN
+ * rightmost UNKNOWN column (Task 2). The zone VALUE is projection-owned and
+ * unchanged; only the render layout (Task 2) changes.
+ */
+export type AgentZone = 'flow' | 'on-demand' | 'general';
+export interface KnownAgent {
+    /** Role id — the entity key and the default card title (render may localize). */
+    id: string;
+    /** Optional display label; render falls back to `id` when absent. */
+    displayName?: string;
+    /** The role's EXPECTED_ROLE_FLOW stage; null → off-pipeline role. */
+    stage?: {
+        phase: PhaseId;
+        stage: string;
+    } | null;
+    /** Off-pipeline zone (plan 20260811-panel-f3-agent-general): 'on-demand'
+     * for the implementor-sub-bucket on-demand roles (ops-engineer /
+     * prompt-engineer — rendered inside the `sdd-implement` column's
+     * implementor partition with an on-demand badge, plan
+     * 20260812-panel-f5-agent-layout Task 1 / Task 2), 'general' (the default
+     * when omitted) for the general bucket. The `'general'` literal is the
+     * type-level binding of `GENERAL_BUCKET` (see above) — a union member
+     * cannot reference a value. */
+    zone?: 'on-demand' | 'general';
+}
+/** Known-agent roster — 14 roles, spec §4 order (project-manager + explore
+ * excluded; `code-reviewer` added by plan 20260812-panel-f5-agent-layout
+ * Task 1 — upstream v2.1.1 roles.ts is the semantic SSOT). */
+export declare const KNOWN_AGENTS: readonly KnownAgent[];

package/dist/client/panel/guards.d.ts

@@ -0,0 +1,12 @@
+/**
+ * Field-level degradation guards for the runtime `mstar-engine-status` source
+ * (spec §2.4): the client does not exhaustively validate the union — it
+ * narrows by `kind`, then degrades per field. Unknown/missing values render
+ * as `unknown`, never as guessed values.
+ */
+/** String field: non-empty string, else null (missing → `unknown`). */
+export declare function str(value: unknown): string | null;
+/** Boolean field: real boolean, else null. */
+export declare function bool(value: unknown): boolean | null;
+/** Count field: finite number, else null. */
+export declare function count(value: unknown): number | null;

package/dist/client/panel/locale.d.ts

@@ -0,0 +1,134 @@
+/**
+ * `mstar-panel` locale namespace (spec §4.3): en (default) + zh, registered
+ * via `ctx.locale.register(NS, { zh, en })` at plugin apply. The key union is
+ * merged into the ui-slots `LocaleNamespaceMap` so the framework synthesizes
+ * a typed `t` seat for the panel component (dictionary keys are checked
+ * against the union by `LocaleDictOf`).
+ *
+ * T2 (spec panel-zones §2, plan 20260810-panel-canvas-zones): the react-flow
+ * graph is replaced by the zone dashboard — the `graph.phase.*` /
+ * `graph.state.*` / react-flow `graph.legend.*` key families are gone with
+ * the graph library; only `graph.pass` / `graph.fail` remain (the
+ * gate-verdict labels reused by the tabs-shell IterationTaskPage head), and
+ * the new `zone.*` family covers the three zone titles/placeholders + the
+ * zone-semantic legend. The `flow.*` key family (agent-flow event dock) is
+ * unchanged. The old footer's violations copy (`graph.violations` /
+ * `graph.no-violations`) is carried by the event-log plan — it adds its own
+ * dedicated keys when that page lands, NOT reserved in this union.
+ *
+ * T3 (spec panel-zones §3): the iteration zone is filled in — `zone.phase.*`
+ * (the 5 PHASE_IDS names, the `graph.phase.*` wording moved into the zone
+ * namespace), `zone.iteration.*` (Step N/5 label, Step N badge, step-state
+ * chips) and `zone.branches.*` (the branch panel
+ * moved from the sidebar). `zone.iteration.placeholder` is gone with the
+ * placeholder.
+ *
+ * T4 (spec panel-zones §3): the task board kanban is filled in —
+ * `zone.state.*` (the 5 PLAN_STATE_IDS column names — en is the raw status
+ * word, zh the localized name; `blocked-unknown` is the merged
+ * Blocked/unknown column, plan 20260813-panel-quick-fixes Task 1),
+ * `zone.tasks.total` (zone header plan total), `zone.tasks.no-plans` (the
+ * muted empty note), `zone.tasks.more` (the per-column `+N more` expand
+ * affordance) and `zone.tasks.collapse` (the 「收起」 collapse label).
+ * `zone.tasks.placeholder` is gone with the placeholder.
+ *
+ * T2 (spec panel-zones §4, plan 20260810-panel-agent-flow-zone): the agents
+ * zone is filled in — `zone.agents.summary` (`N executing · M pending`).
+ * `zone.agents.placeholder` is gone with the placeholder; the dashed
+ * "待执行" chip (`pending-label`) and the animated next-edge label (`next`)
+ * keys were removed with the AgentFlowZone in the agent-canvas QC wave
+ * (S-001 — the free canvas renders neither, so they had zero consumers).
+ *
+ * T3 (same plan): the dock is collapsible (the frame is a native <details>,
+ * header = <summary>) and the legend gains the entity-status swatches —
+ * `zone.legend.agent-running` / `zone.legend.agent-settled` (the status-dot
+ * treatments of the entity cards; the `zone.agents.*` family itself stays
+ * minimal — title/summary, both rendered by the canvas, so no
+ * `zone.agents.status.*` family is added: a status TEXT on the cards would be
+ * dead strings, the spec §4 card shows a status point, and reusing `flow.*`
+ * would conflate event status words (dispatched/settled ok) with entity
+ * status words).
+ *
+ * T1 (spec panel-tabs §2/§6.1, plan 20260811-panel-tabs-shell): the panel is
+ * re-laid-out as Tabs + Content — `tab.*` covers the 3 fixed MenuTab labels
+ * (任务迭代 / 代理执行 / 事件记录) and `page.*.placeholder` the muted
+ * placeholder copy for the agents/events tabs (the real pages land with the
+ * agent-canvas / event-log plans; Task 3 refines the placeholders).
+ *
+ * T2 (spec panel-tabs §3, plan 20260811-panel-tabs-shell Task 2): the
+ * IterationTaskPage head copy — `page.iteration.*` (the collapsed one-line
+ * "not started" note + the expand/collapse toggle hints). The head reuses the
+ * existing `zone.iteration.*` (step badge / Step n/5 label / step-state
+ * chips), `zone.phase.*` (the 5 PHASE_IDS names) and `zone.branches.*`
+ * (branch panel) keys; the kanban reuses `zone.tasks.*` / `zone.state.*`.
+ *
+ * T3 (spec panel-tabs §4, plan 20260811-panel-agent-canvas Task 3): the
+ * legend re-mounts on the agent canvas — `zone.legend.agent-idle` (the idle
+ * card treatment) joins the swatch family and the collaboration-edge labels
+ * (flow-expected / flow-actual / general) now describe the canvas rendering
+ * (dashed/solid lines + the general bucket — plan
+ * 20260811-panel-f3-agent-general replaced the former flow-unexpected entry)
+ * instead of the retired zone-dashboard stages; `flow.settle-only` is the
+ * distinct muted copy for the settle-only canvas note (review T2-Imp-2
+ * restored the old zone's separate anchor).
+ *
+ * T2 (plan 20260811-panel-f4-agent-view): the general bucket has NO column
+ * of its own anymore — `zone.agents.general` is REPURPOSED as the small
+ * in-bucket label on the general card (which sinks to the bottom of the
+ * `sdd-implement` column — the value stays the user-fixed literal 'general'
+ * in both locales); `zone.legend.general` rewords to the sink semantics
+ * (「general 位于 sdd-implement 桶内底部」).
+ *
+ * T2 (plan 20260812-panel-f5-agent-layout Task 2 — the layout rework
+ * supersedes the F4.2 sink): the general bucket moves to its OWN rightmost
+ * UNKNOWN column — `zone.agents.unknown` (the column label, 未知 / unknown);
+ * the in-bucket general tag is gone (the general card's title + the unknown
+ * column label carry it), so `zone.agents.general` is REMOVED. The
+ * `sdd-implement` column splits into sub-buckets — `zone.agents.bucket.*`
+ * (implementor / sdd-reviewer caption labels); `zone.agents.on-demand`
+ * re-keys as the on-demand BADGE (the implementor-sub-bucket roles, the
+ * standalone on-demand column is removed). The legend entries gain
+ * `zone.legend.sub-bucket` / `zone.legend.supervise` / `zone.legend.unknown`
+ * (the former 'general' entry is replaced by 'unknown'); `zone.legend.general`
+ * is REMOVED and `zone.legend.on-demand` rewords to the badge semantics.
+ *
+ * T5 (plan 20260812-panel-f5-design-system Task 5 — the 2026-08-12 edge
+ * rework supersedes the Task-2 unknown COLUMN): the standalone rightmost
+ * unknown column is REMOVED (user feedback #3 — FOUR columns total) — the
+ * general bucket sinks into an unknown SUB-PARTITION at the bottom of the
+ * LAST column, so `zone.agents.unknown` (the old column label) is REMOVED
+ * and `zone.agents.unknown-sub` (「unknown / 未匹配角色」) is the sub-partition
+ * caption. The legend drops the expected / next entries (both edges are
+ * REMOVED, design doc §2.2) and gains `zone.legend.port` (the hover-visible
+ * card ports, design doc §2.5); `zone.legend.flow-actual` / `supervise` /
+ * `unknown` reword to the bezier / port-anchored / side-gap / sub-partition
+ * semantics.
+ *
+ * T3 (plan 20260812-panel-f5-agent-layout Task 3): the no-harness branch
+ * renders a CENTERED inactive-state card (icon + title + hint, no tabs /
+ * no sidebar) instead of the left-aligned hint — `empty.no-harness-hint`
+ * is the explanatory secondary copy under the reused `empty.no-harness`
+ * title.
+ *
+ * T1 (plan 20260813-panel-agent-canvas-legend-layout Task 1 — 图例精简): the
+ * legend narrows to the 3 role-card status entries —
+ * `zone.legend.flow-actual` / `port` / `group` / `sub-bucket` / `supervise` /
+ * `on-demand` / `unknown` are REMOVED (the collaboration-edge / layout tech
+ * entries; the canvas itself keeps the edges / ports / partitions — only the
+ * legend copy drops them). `zone.legend.agent-running` / `agent-settled` /
+ * `agent-idle` remain.
+ */
+import type { LocaleDictOf } from '@deepseek-ai/dsh-client-ui-slots';
+/** Locale namespace id for the workflow-viz panel. */
+export declare const NS = "mstar-panel";
+/** Panel dictionary keys (union of every translatable string the panel renders). */
+export type PanelKey = 'view.mstar-workflow' | 'tab.tasks' | 'tab.agents' | 'tab.events' | 'page.iteration.not-started' | 'page.iteration.expand' | 'page.iteration.collapse' | 'event-log.section.events' | 'event-log.section.violations' | 'event-log.empty' | 'event-log.empty.events' | 'event-log.empty.violations' | 'event-log.field.role' | 'event-log.field.agent' | 'event-log.field.stage' | 'event-log.field.plan' | 'event-log.field.task' | 'event-log.field.category' | 'event-log.field.time' | 'event-log.field.kind' | 'event-log.field.status' | 'event-log.field.expected' | 'event-log.field.settled' | 'event-log.field.duration' | 'event-log.field.severity' | 'event-log.field.code' | 'event-log.field.message' | 'event-log.kind.dispatch' | 'event-log.kind.settle' | 'event-log.yes' | 'event-log.no' | 'empty.waiting' | 'empty.no-harness' | 'empty.no-harness-hint' | 'watermark.version' | 'watermark.harness' | 'watermark.none' | 'panel.unknown' | 'graph.pass' | 'graph.fail' | 'zone.legend.title' | 'zone.legend.agent-running' | 'zone.legend.agent-settled' | 'zone.legend.agent-idle' | 'zone.iteration.step-label' | 'zone.iteration.step-badge' | 'zone.iteration.step.current' | 'zone.iteration.step.next' | 'zone.iteration.step.done' | 'zone.iteration.step.idle' | 'zone.phase.iteration-start' | 'zone.phase.autonomous-execute' | 'zone.phase.iteration-close' | 'zone.phase.pr-delivery' | 'zone.phase.merge-ready' | 'zone.branches.title' | 'zone.branches.iteration-base' | 'zone.branches.target' | 'zone.branches.spec-integration' | 'zone.tasks.title' | 'zone.tasks.total' | 'zone.tasks.no-plans' | 'zone.tasks.more' | 'zone.tasks.collapse' | 'zone.state.Todo' | 'zone.state.InProgress' | 'zone.state.InReview' | 'zone.state.Done' | 'zone.state.blocked-unknown' | 'zone.agents.title' | 'zone.agents.summary' | 'zone.agents.on-demand' | 'zone.agents.unknown-sub' | 'zone.agents.bucket.implementor' | 'zone.agents.bucket.reviewer' | 'zone.agents.group.phase-1' | 'zone.agents.group.phase-2' | 'zone.agents.group.phase-n' | 'zone.agents.group.plan' | 'zone.agents.group.no-plan' | 'zone.agents.group.plan-more' | 'flow.empty' | 'flow.settle-only' | 'flow.degraded' | 'flow.unexpected' | 'flow.in-flight' | 'flow.settled-ok' | 'flow.error' | 'flow.advisory' | 'flow.denied' | 'state.title' | 'state.plans' | 'state.residuals' | 'state.policy' | 'state.leases' | 'state.knowledge' | 'state.direction' | 'state.none' | 'state.enforcement' | 'state.enforcement.hard' | 'state.enforcement.soft' | 'state.plans.more' | 'state.residual.more' | 'state.policy.push' | 'state.policy.worktree' | 'state.policy.control-worktree' | 'state.knowledge.docs' | 'freshness.last-updated' | 'freshness.refresh-note';
+declare module '@deepseek-ai/dsh-client-ui-slots' {
+    interface LocaleNamespaceMap {
+        'mstar-panel': PanelKey;
+    }
+}
+/** zh dictionary (repo bilingual convention; zh is the stub fallback locale). */
+export declare const zh: LocaleDictOf<'mstar-panel'>;
+/** en dictionary (default locale). */
+export declare const en: LocaleDictOf<'mstar-panel'>;