@mstar-harness/dsh 3.8.0 → 3.8.2

package/dist/client/panel/mstar-glyph.d.ts

@@ -0,0 +1,22 @@
+/**
+ * The panel's own inline glyph (plan sidebar §L1.3): the icon the guide
+ * capsule draws before its title, and the chip title seat draws before the
+ * captured tab title. Deliberately NOT imported from
+ * `@deepseek-ai/dsh-client-ui-primitives` — dynamic client plugins may not
+ * import runtime values from other client plugins (types only), and the
+ * client bundle's purity gate rejects `@deepseek-ai/*` value imports — so the
+ * glyph is our own `<svg>` on `currentColor`, `IconProps`-shaped like the
+ * shipped `CompassGlyph`/`CubeGlyph`.
+ */
+import type { IconProps } from '@deepseek-ai/dsh-client-ui-primitives';
+/**
+ * The brand star on `currentColor` — the plugin's mark at guide and chip
+ * sizes (14–16px). `size` defaults to 16 (the guide-capsule size — the
+ * definition registers this component with no props); the chip title seat
+ * passes 14 explicitly. The geometry is the brand mark from the repo's
+ * `assets/` logos (`logo.svg` / `logo-dark.svg`): the star path reused
+ * verbatim (viewBox 512), the assets' colored rounded tile dropped — no
+ * tile, no hardcoded colors — `fill='currentColor'` so the host's chip/guide
+ * styling themes the mark.
+ */
+export declare function MstarGlyph({ size, className }: IconProps): import("react").JSX.Element;

package/dist/client/panel/pages/AgentListPage.d.ts

@@ -0,0 +1,71 @@
+/**
+ * AgentListPage (plan sidebar §L3) — the 代理执行 tab: a VERTICAL GROUPED
+ * LIST. Replaces the deleted absolutely-positioned agent canvas: every
+ * geometry concept (the coordinate-space content layer, the pointer pan, the
+ * stage columns, the card boxes, the SVG edge layer, the card ports) is
+ * gone — the flow itself is carried by the group/stage/sub-bucket headings
+ * in constant order, exactly as the column order did before.
+ *
+ * Grouping (plan sidebar §L3.2 — locked, PROJECTION-driven, never a render
+ * guess): two levels. The OUTER group is the phase of the entity's stage
+ * (`entity.stage.phase`, or `entity.zone` when `stage === null`), in the
+ * `EXPECTED_ROLE_FLOW`/`view.stages` constant order — Phase 1
+ * (iteration-start: the sequential review-edit-chain) then Phase 2
+ * (autonomous-execute: the iterative plan loop, annotated with the current
+ * `activePlanId`). The INNER group is the stage with the implementor stage
+ * split by the PROJECTED `entity.bucket`: the implementor partition above
+ * (flow roles in `SDD_BUCKET_ROLES.implementor` order, then the on-demand
+ * roles, carrying the on-demand badge) and the reviewer partition below —
+ * plus the「unknown / 未匹配角色」sub-bucket at the bottom of the LAST stage
+ * group for `zone: 'general'` entities, rendered only when it has members
+ * (the canvas's placement rule, unchanged). Every stage group always
+ * renders, because the projection always yields the full 14-role roster as
+ * cards (idle at minimum). The implementor-partition host stage is DERIVED
+ * from the projected skeleton (the stage whose expected roles intersect
+ * `SDD_BUCKET_ROLES.implementor`), so a phase/stage rename can never
+ * silently orphan the sub-buckets; absent that stage the LAST stage group is
+ * the total-function sink (never a throw).
+ *
+ * Card anatomy (plan sidebar §L3.3): each entity is a FULL-WIDTH FLOW ROW —
+ * no inline box style, no absolute positioning, no ports. The status point,
+ * done-✓ restriction (`status === 'settled' && emphasis !== 'off'`), the
+ * title rule, the ×N count, the role chip, the record line and the on-demand
+ * badge are all carried over unchanged.
+ *
+ * Emphasis tiers (design doc §3): the projected `data-agent-emphasis` tier
+ * fades the card CHROME only (chrome colors mix toward the layer background
+ * by tier — current 100% / next 75% / off 45%, theme-independent per
+ * `DESIGN.md` §3.5) — NEVER a whole-card opacity, so the status point and
+ * the ✓ never fade.
+ *
+ * Shared iteration section: the page renders the SAME `IterationInfoSection`
+ * the tasks tab uses, from the SAME `view.iteration` data — 两个 tab 显示同一
+ * 迭代信息块. The degradation note (degraded / empty / settle-only / link-only) is
+ * PROJECTED metadata, never inferred from the entity list, and the `Legend`
+ * (the 3 role-card status treatments) sits in flow BELOW the list.
+ *
+ * Scrolling (plan sidebar §L2.2): the page owns NO scroller — the rows grow
+ * the panel's single scroll body (`[data-mstar-scroll]`). The phase groups
+ * ride the shell's shared `.groupGrid` class (one column below the 720px
+ * container breakpoint, the two-column spread above it is that rule's).
+ */
+import * as React from 'react';
+import type { TranslateNS } from '@deepseek-ai/dsh-client-ui-slots';
+import type { ZoneView } from '../graph/project-graph.ts';
+export interface AgentListPageProps {
+    /** The projected agents zone (spec §6.2 — `ZoneView['agents']`). */
+    view: ZoneView['agents'];
+    /** The projected iteration zone (spec §3) — the SHARED iteration info
+     * block: BOTH the tasks tab and this page render the SAME
+     * `IterationInfoSection` from the SAME `view.iteration` data. */
+    iteration: ZoneView['iteration'];
+    t: TranslateNS<'mstar-panel'>;
+}
+/**
+ * The unknown sub-bucket id : `zone: 'general'` entities render in the
+ * 「unknown / 未匹配角色」sub-bucket at the bottom of the LAST stage group,
+ * marked `data-sub-bucket="unknown"`. The constant survives the canvas
+ * deletion — it names the sub-bucket VALUE, not a column.
+ */
+export declare const UNKNOWN_COLUMN = "unknown";
+export declare function AgentListPage({ view, iteration, t }: AgentListPageProps): React.JSX.Element;

package/dist/client/panel/pages/EventLogPage.d.ts

@@ -10,10 +10,13 @@
  * keyboard-accessible, SSR-stable) whose body shows the FULL catalog fields;
  * a missing field renders「—」— never a guessed value (spec §5/§8).
  *
- * Layout (user feedback「左右
- * 排两列 + 锁定一个高内部滚动」): the two partitions render side by side in a
- * locked-height two-column grid; the page never scrolls as a whole — each
- * partition pins its title and scrolls internally (`event-log.module.css`).
+ * Layout (plan sidebar §L2.5/§L4.1): the two partitions are FLOW ROWS in
+ * the panel's single scroll body (`[data-mstar-scroll]`) — the old
+ * locked-height two-column grid and both per-partition internal scrollers
+ * are retired; rows grow the scroll body instead of owning a scrollbar.
+ * The grid rides the shell's shared `.groupGrid` class, so the ≥720px
+ * container spread is the shell's one rule. The iteration head is NOT
+ * rendered in this section.
  *
  * Dock migration decision (spec §5 — 无双份日志): the AgentEventDock is
  * REMOVED, not degraded. The dock's content (row layout + status chips)

package/dist/client/panel/pages/IterationInfoSection.d.ts

@@ -2,9 +2,10 @@
  * IterationInfoSection (spec panel-tabs §3
  * — the SHARED iteration info block): the
  * Content Head — iteration summary (the collapsible toggle row) + the 5
- * horizontal iteration steps + the branches panel — rendered by BOTH tabs
+ * iteration steps stacked VERTICALLY + the branches panel — rendered by BOTH
+ * tabs
  * from the SAME `view.iteration` data (the tasks tab inside IterationTaskPage
- * above the kanban, the agents tab inside AgentCanvasPage above the canvas).
+ * above the board, the agents tab inside AgentListPage above the list).
  * One implementation, two mounts — 任务迭代与代理执行共用同一迭代信息块.
  *
  * The component is extracted VERBATIM from the former inline head of
@@ -13,18 +14,20 @@
  * - Content Head (spec §3): the iteration info (iterationId / gate verdict /
  *   status note) rides the summary row, which IS the toggle (a native button
  *   with aria-expanded + aria-controls pointing at the body). The
- *   expanded body renders the Steps HORIZONTALLY as 5 EQUAL full-width unit
- *   blocks (badge/phase/chip
- *   centered, --mstar-space-* gap; no connector bars) with the current step
- *   highlighted on the block itself (the same honesty as the zone stepper:
- *   no "completed" checkmarks) plus the branch panel (rendered ONLY while the
- *   iteration is active, spec §3). Plan (spec panel-f4 §2.3 R8/R9): the expanded body is a LEFT-RIGHT
- *   SPLIT — branches (small half, DOM-first) + steps (large half), with the
- *   `data-iteration-head-split` container present only while branches render;
+ *   expanded body renders the Steps as a VERTICAL 5-item stacked stepper
+ *   (one row per step: badge · phase · chip · verdict seat; plan sidebar
+ *   §L4.2 — the horizontal row cannot fit the 300px column) with the current
+ *   step highlighted on the block itself (the same honesty as the zone
+ *   stepper: no "completed" checkmarks) plus the branch panel (rendered ONLY
+ *   while the iteration is active, spec §3). Plan (spec panel-f4 §2.3
+ *   R8/R9, re-shaped by plan sidebar §L4.2): the expanded body STACKS —
+ *   branches (DOM-first) above the steps; the `data-iteration-head-split`
+ *   container is present only while branches render;
  *   each step reserves the fixed-height verdict seat (`data-step-verdict-seat`)
  *   and the PASS/FAIL badge renders only for a current step with a real gate
  *   verdict (`state === 'current' && verdict !== 'unknown'` — Phase 1 renders
- *   no badge), so the centered content groups align across steps.
+ *   no badge), so every step row has the SAME children (badge/phase/chip/seat)
+ *   and the rows align across steps.
  *
  * Collapse/expand (spec §3): a local `useState` defaulted to
  * the iteration state — `active === false` → collapsed to a one-line summary
@@ -68,9 +71,9 @@ export declare function nextExpandedOnActivation(prev: boolean, prevActive: bool
  * — exported pure for the render tests, the `nextExpandedOnActivation`
  * precedent): the `data-iteration-head-split` container renders ONLY while
  * the branch panel renders (`active && branches !== null`); otherwise the
- * expanded body renders the steps row ALONE — the expanded-inactive fallback
+ * expanded body renders the steps stack ALONE — the expanded-inactive fallback
  * (a user manually expands an inactive head → the 5-step idle skeleton
- * without the split). The `active + branches null` arm is projection-
+ * without the wrapper). The `active + branches null` arm is projection-
  * unreachable (branches are always projected non-null while active), but the
  * predicate keeps the decision a single, testable source of truth.
  */

package/dist/client/panel/pages/IterationTaskPage.d.ts

@@ -1,31 +1,30 @@
 /**
  * IterationTaskPage (spec panel-tabs §3
  * — the 任务迭代 tab: the SHARED IterationInfoSection (iteration
- * summary + the 5 horizontal iteration steps + branches — the same block the
+ * summary + the vertical 5-step stepper + branches — the same block the
  * agents tab renders, user
- * 2026-08-12 feedback #4) above the full-width standard kanban. Replaces the
+ * 2026-08-12 feedback #4) above the stacked plan board. Replaces the
  * WorkflowCanvas zone dashboard on the tasks tab (WorkflowCanvas is removed
  * by the plan close; its zone-level components stay untouched here).
  *
- * The head (collapse/expand, steps row, branches, verdict seats) lives in
- * `IterationInfoSection.tsx` — extracted from this page by Task 8 so BOTH
+ * The head (collapse/expand, vertical steps, branches, verdict seats) lives
+ * in `IterationInfoSection.tsx` — extracted from this page by Task 8 so BOTH
  * tabs render the SAME iteration info block from the SAME `view.iteration`
  * data (one implementation, two mounts; the anchor family `data-iteration-*`
  * is unchanged).
  *
- * Task area (spec §3/D2): the standard 5-column kanban (Todo / InProgress /
- * InReview / Done / blocked-unknown — Blocked + unknown merged) via the
- * REUSED TaskBoard
- * (`view.tasks`) — the Done overflow stays the projection's PLAN_CAP
- * handling (TaskBoard only surfaces the `+N more` hint). The page fills the
- * content region as a flex column: the head is flex:none (fixed), the tasks
- * area (`data-mstar-tasks-scroll`) is the page's independent vertical scroll
- * body (flex:1, min-height:0, overflow-y:auto) — the kanban spreads
- * full-width and is never compressed into a small box by a canvas height.
+ * Task area (plan sidebar §L4.2): the standard 5-group board (Todo /
+ * InProgress / InReview / Done / blocked-unknown — Blocked + unknown merged)
+ * via the REUSED TaskBoard (`view.tasks`) — the Done overflow stays the
+ * projection's PLAN_CAP handling (TaskBoard only surfaces the `+N more`
+ * hint). The page is FLOW CONTENT inside the panel's single scroll body
+ * (`[data-mstar-scroll]`, plan sidebar §L2.2 — the page-owned scroll body is
+ * retired): the board stacks as five groups, then the project rollup, then
+ * the in-flow digest.
  *
  * Degradation (spec §8): the projection never throws — an inactive/missing
  * iteration renders the collapsed muted summary; state/plans missing render
- * the muted 5-column kanban skeleton (TaskBoard) — never an orange warn box.
+ * the muted 5-group kanban skeleton (TaskBoard) — never an orange warn box.
  */
 import * as React from 'react';
 import type { TranslateNS } from '@deepseek-ai/dsh-client-ui-slots';

package/dist/client/panel/panel-store.d.ts

@@ -0,0 +1,28 @@
+/**
+ * The workflow panel's entry store (plan sidebar §L2.4): the selected
+ * internal section, keyed by the sidebar tab record's id.
+ *
+ * Why a slot store and not `useState`: a docked sidebar body is UNMOUNTED
+ * whenever another tab in the pane becomes active (and the sidebar layout is
+ * memory-only), so component state would silently reset the section on every
+ * glance at the file tree. The store instance is framework-cached per
+ * (entry, session) and survives the unmount by construction; keying inside
+ * the state by `tab.id` keeps two panes showing the panel independent. The
+ * registration passes the handle as the seat's `store` option, so the body
+ * receives `useStore` + the baked `select` action through its props share.
+ */
+/** The panel's three internal sections (one sidebar tab, three sections). */
+export type PanelSection = 'tasks' | 'agents' | 'events';
+/** The entry-store state: the selected section per sidebar tab record. */
+export interface PanelStoreState {
+    byTab: Record<string, PanelSection | undefined>;
+}
+/**
+ * The panel entry store handle. `undefined` reads as the `'tasks'` default —
+ * the body applies `?? 'tasks'` at the read site, so nothing writes the
+ * default into the state.
+ */
+export declare function createPanelStore(): import("@deepseek-ai/dsh-client-store").EngineStoreHandle<PanelStoreState, {
+    select(d: PanelStoreState, tabId: string, section: PanelSection): void;
+}>;
+export type PanelStore = ReturnType<typeof createPanelStore>;

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

@@ -1,17 +1,23 @@
 /**
- * Panel right sidebar (spec panel-zones §5): fixed 300px column, full height,
- * flex column — the workspace-state digest scrolls in its own region
- * (`flex: 1; min-height: 0; overflow-y: auto`), while the bottom meta dock
- * (version + harness dir) stays pinned and does NOT scroll with the digest.
+ * Workspace-state digest (plan sidebar §L2.1): the former 300px sidebar
+ * column, now IN FLOW at the end of the panel's scroll body — the digest is
+ * not a column any more, and its own nested scroller
+ * (`data-mstar-sidebar-scroll`) is retired: `[data-mstar-scroll]` is the
+ * panel's single scroller and this block is flow content inside it. The
+ * bottom meta dock moved to the shell's third zone (PanelView renders it
+ * directly), so this component renders ONLY the digest.
+ *
+ * `data-mstar-sidebar` stays on the digest block (anchor lineage).
  * Degradation: `state === null` renders the no-state note instead of the
- * digest (never a crash); the meta dock still renders from the source.
+ * digest (never a crash).
  */
 import * as React from 'react';
 import type { TranslateNS } from '@deepseek-ai/dsh-client-ui-slots';
 import type { MstarEngineStatusPayload, MstarHarnessState } from '../../types.ts';
-export interface SidebarProps {
+import { type MstarSelectionSeat } from './state-section.tsx';
+export interface SidebarProps extends MstarSelectionSeat {
     t: TranslateNS<'mstar-panel'>;
     state: MstarHarnessState | null;
     source: MstarEngineStatusPayload;
 }
-export declare function Sidebar({ t, state, source }: SidebarProps): React.JSX.Element;
+export declare function Sidebar({ t, state, source, selection, pick, select }: SidebarProps): React.JSX.Element;

package/dist/client/panel/state-section.d.ts

@@ -13,11 +13,33 @@
  */
 import * as React from 'react';
 import type { TranslateNS } from '@deepseek-ai/dsh-client-ui-slots';
-import type { MstarEngineStatusPayload, MstarHarnessState } from '../../types.ts';
-export interface StateSectionProps {
+import type { MstarEngineStatusPayload, MstarHarnessState, WorkflowSelectionView } from '../../types.ts';
+import type { MstarSelectionState } from './engine-status-client.ts';
+/**
+ * The picker seat (D4): the selection the panel SHOWS, this session's own
+ * commit state, and the commit seat itself. Handed down as one unit from the
+ * hook result to the section that renders it.
+ */
+export interface MstarSelectionSeat {
+    /**
+     * This session's CURRENT selection: the host's live control-state `binding`
+     * when the response carries one, else the last emission's own record
+     * (`state.selection`). `null` renders the unknown arm rather than throwing.
+     */
+    readonly selection: WorkflowSelectionView | null;
+    /** This session's picker state (control feedback, never a selection source). */
+    readonly pick: MstarSelectionState;
+    /**
+     * Commit a workflow pick for this session, or null when the panel cannot
+     * (no client / no session / unknown cwd). Null renders an error selection
+     * WITHOUT a picker: a row that cannot be committed must not look clickable.
+     */
+    readonly select: ((workflowId: string) => void) | null;
+}
+export interface StateSectionProps extends MstarSelectionSeat {
     t: TranslateNS<'mstar-panel'>;
     state: MstarHarnessState;
     /** Top-level enforcement flag (spec §2.1) — NOT part of the state digest. */
     enforcement: MstarEngineStatusPayload['enforcement'];
 }
-export declare function StateSection({ t, state, enforcement }: StateSectionProps): React.JSX.Element;
+export declare function StateSection({ t, state, enforcement, selection, pick, select }: StateSectionProps): React.JSX.Element;

package/dist/client/panel/use-mstar-engine-status.d.ts

@@ -1,16 +1,17 @@
 /**
  * Data hook for the workflow panel (spec §5): the panel's ONE data path.
  *
- * The persisted catalog row is an ANCHOR, not a data source: since the source
- * reduction the row carries exactly `{ kind: 'plugin', plugin:
- * 'mstar-engine-status', form: 'catalog' }`, and the structured payload lives
- * in the host's per-session snapshot store. So the hook
+ * The persisted catalog row is an ANCHOR, not a data source: rows are emitted
+ * as `{ kind: 'plugin', plugin: 'mstar-engine', form: 'catalog' }`, and the
+ * structured payload lives in the host's per-session snapshot store. So the
+ * hook
  *
  * 1. finds the LATEST anchor row in the active session's conversation log
  *    (`kind === 'context'` + `form === 'catalog'` + the first-party `plugin`
- *    arm with this plugin's identity) and takes its message time as the
- *    refresh key — a re-emission appends a new row, the snapshot bump re-runs
- *    this selection, and the newest anchor asks for the newest snapshot;
+ *    arm with one of this plugin's anchor identities) and takes its message
+ *    time as the refresh key — a re-emission appends a new row, the snapshot
+ *    bump re-runs this selection, and the newest anchor asks for the newest
+ *    snapshot;
  * 2. reads the session's workspace directory from the session standard kit's
  *    session feed (the host cross-checks the asserted `cwd` against the
  *    session AND the stored snapshot, so it must be the real one);
@@ -36,8 +37,8 @@ import type { ChatSnapshot } from '@deepseek-ai/dsh-client-ui-chat/client';
 import type { SnapshotSelectorHook } from '@deepseek-ai/dsh-client-ui-slots';
 import type { SessionListState } from '@deepseek-ai/dsh-api-session-controller/client';
 import type { SessionId } from '@deepseek-ai/dsh-session';
-import type { MstarEngineStatusPayload } from '../../types.ts';
-import type { MstarEngineStatusClient } from './engine-status-client.ts';
+import type { MstarEngineStatusPayload, WorkflowSelectionView } from '../../types.ts';
+import type { MstarEngineStatusClient, MstarSelectionState } from './engine-status-client.ts';
 /** Selector hook over the Host session list (the `useSessions` standard seat). */
 export type UseSessions = SnapshotSelectorHook<SessionListState>;
 /** The panel's render state — a closed set: no shape can be both data and empty. */
@@ -65,6 +66,12 @@ export type MstarEngineStatusView =
  * identity (`at` timestamp and the agent turn it was written for). Both are
  * the host's records of the stored entry, so the panel can name which
  * emission it is showing rather than implying it is the newest one.
+ *
+ * `binding` is the host's CURRENT control-state selection for this session
+ * (`null` when it served none), deliberately separate from
+ * `payload.state.selection` — which keeps recording the last MODEL EMISSION,
+ * so the picker's acknowledgement shows immediately while plans / Event Log
+ * stay on the last emitted snapshot.
  */
  | {
     readonly state: 'ok';
@@ -72,6 +79,7 @@ export type MstarEngineStatusView =
     readonly payload: MstarEngineStatusPayload;
     readonly at: string;
     readonly turn: number;
+    readonly binding: WorkflowSelectionView | null;
     readonly reason: null;
 }
 /** An explicit degraded answer — always WITH a reason, never silently empty. */
@@ -85,11 +93,11 @@ export type MstarEngineStatusView =
 };
 /** The seats the hook needs: the session standard kit + the plugin's client. */
 export interface MstarEngineStatusSeats {
-    /** Selector hook over the chat target snapshot (the `conversation.view` kit). */
+    /** Selector hook over the chat target snapshot (the session standard kit's chat face). */
     useChat: SnapshotSelectorHook<ChatSnapshot>;
     /**
      * Selector hook over the Host session list (the global standard seat). The
-     * view ring always hands it to a `conversation.view` entry; it stays
+     * session-scope slot dispatch always hands it to the panel; it stays
      * optional here because a program without the ui-session adapter does not
      * see the declaration merge (the panel then reports `session-cwd-unknown`).
      */
@@ -99,7 +107,22 @@ export interface MstarEngineStatusSeats {
     /** The plugin's engine-status client (absent in a composition without one). */
     engineStatus: MstarEngineStatusClient | undefined;
 }
-/** Latest `mstar-engine-status` anchor row in snapshot order, or null. */
+/**
+ * The panel hook's result: the render state plus this session's picker seat.
+ * `selection` is the served binding (absent until an `ok` render); `pick` is the
+ * local commit state for THIS session only; `select` is null exactly when no
+ * commit can be made (no client, no session, or unknown cwd).
+ */
+export interface MstarEngineStatusHook {
+    readonly view: MstarEngineStatusView;
+    /** The served selection of the rendered payload (null unless `view.state === 'ok'`). */
+    readonly selection: WorkflowSelectionView | null;
+    /** This session's picker state, `idle` until a pick is committed. */
+    readonly pick: MstarSelectionState;
+    /** Commit a pick for this session; null when the panel cannot commit one. */
+    readonly select: ((workflowId: string) => void) | null;
+}
+/** Latest engine-status anchor row (either accepted identity) in snapshot order, or null. */
 export declare function latestEngineStatusRow(nodes: readonly ConversationNode[]): ContextMessageNode | null;
 /** Anchor row message time, or null when the log carries no anchor row. */
 export declare function selectAnchorTime(snapshot: ChatSnapshot): number | null;
@@ -109,6 +132,8 @@ export declare function selectSessionCwd(sessionId: SessionId | undefined): (sta
  * The panel's data hook (spec §5).
  *
  * @param seats - the session standard kit + the plugin's engine-status client.
- * @returns the explicit render state (never a throw, never a half-parsed view).
+ * @returns the explicit render state (never a throw, never a half-parsed view)
+ *   plus this session's picker triple: the served `selection`, the local commit
+ *   `pick`, and `select` (null when no pick can be committed).
  */
-export declare function useMstarEngineStatus(seats: MstarEngineStatusSeats): MstarEngineStatusView;
+export declare function useMstarEngineStatus(seats: MstarEngineStatusSeats): MstarEngineStatusHook;

package/dist/client/panel/zones/Legend.d.ts

@@ -1,8 +1,10 @@
 /**
  * Legend (spec panel-tabs §4/§6.2):
- * mounted on the AgentCanvasPage (the zone-dashboard footer legend is gone
- * with the WorkflowCanvas — spec §6.1). Describes ONLY the role-card status
- * treatments of the agent canvas — plan
+ * mounted on the AgentListPage, IN FLOW below the grouped list (the
+ * zone-dashboard footer legend is gone with the WorkflowCanvas — spec §6.1;
+ * the list page keeps the legend placement the canvas page established,
+ * after the content). Describes ONLY the role-card status
+ * treatments of the agent rows — plan
  *  Task 1 (图例精简): the 7
  * collaboration-edge / layout entries (flow-actual / port / group /
  * sub-bucket / supervise / on-demand / unknown) are REMOVED — the legend is

package/dist/client/panel/zones/TaskBoard.d.ts

@@ -1,13 +1,17 @@
 /**
  * TaskBoard  — the tasks-zone kanban: the 5
- * PLAN_STATE_IDS columns (Todo / InProgress / InReview / Done /
- * blocked-unknown, in the projection's constant order), each with a localized
- * state-name header + count badge, plan cards (mono ellipsized id + status
- * chip — the `data-plan-id` / `data-plan-status` anchors shared with the
- * sidebar plan board), the dim inter-column flow arrows (spec §2.4:
- * Todo→InProgress→InReview→Done plus the InProgress↔Blocked back-edge, now
- * docking at the merged blocked-unknown column), the per-column 「更多」
- * expand affordance, and the muted "no plans" empty state.
+ * PLAN_STATE_IDS groups (Todo / InProgress / InReview / Done /
+ * blocked-unknown, in the projection's constant order) STACKED in flow (plan
+ * sidebar §L4.2 — the horizontal 5-column row cannot fit the 300px column),
+ * each with a header row carrying the flow glyph (the
+ * `data-kanban-arrow` labels + the `⇄` back-edge glyph: Todo→InProgress→
+ * InReview→Done plus the InProgress↔Blocked back-edge, docking at the merged
+ * blocked-unknown group), the localized state-name + count badge, plan cards
+ * (mono ellipsized id + status chip — the `data-plan-id` /
+ * `data-plan-status` anchors shared with the sidebar plan board), and the
+ * per-group 「更多」 expand affordance. The board rides the shell's shared
+ * `.groupGrid` class, so the ≥720px container spread reaches the groups
+ * (plan sidebar §L4.3 — one wide rule, not a second layout).
  *
  * The projection KEEPS every row (`column.plans` = the full column) and
  * reports `column.capped` (PLAN_CAP) when a column overflows. This render
@@ -19,7 +23,7 @@
  * keeps input order.
  *
  * Degradation (spec §8): state null / plans missing project to the same
- * 5-column skeleton with count 0 — the board renders it with a muted
+ * 5-group skeleton with count 0 — the board renders it with a muted
  * "no plans" note (`data-zone-empty="no-plans"`), NEVER an orange warn box.
  */
 import * as React from 'react';