@mstar-harness/dsh 2.1.1

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

@@ -0,0 +1,363 @@
+/**
+ * AgentCanvasPage (spec panel-tabs §4/§6.2, plan 20260811-panel-agent-canvas
+ * Task 2) — the 代理执行 tab: a DRAGGABLE agent canvas. Replaces the muted
+ * placeholder page (tabs-shell Task 3) and the stage-column AgentFlowZone
+ * (deleted by this plan — the free canvas supersedes it).
+ *
+ * Canvas contract (spec §6.2 — zero third-party deps):
+ * - pan ONLY (translate, no zoom / pinch / rotate) via native pointer events
+ *   (pointerdown / pointermove / pointerup + setPointerCapture) on the
+ *   viewport; `touch-action: none` + `preventDefault` on pointerdown stop
+ *   native scroll / text selection; during capture the entity cards never
+ *   receive the pointer (no click-through); no pan bounds (free pan).
+ * - forced capture loss (window blur / alt-tab / element removal mid-gesture)
+ *   fires `lostpointercapture` without pointerup — it binds the same end
+ *   handler so `dragRef` never goes stale (review S-002).
+ * - the content layer carries `data-canvas-pan` and exposes the pan state as
+ *   `transform: translate(xpx, ypx)`; the grid background moves WITH the
+ *   content. Pan is instant (no animation), so `prefers-reduced-motion`
+ *   needs no pan-specific handling; the next-edge dash flow and the running
+ *   card pulse are CSS animations killed by the panel root's reduced-motion
+ *   rule (`* { animation: none !important }`).
+ * - pan state `{ x, y }` is LOCAL useState; the drag math is extracted into
+ *   the exported pure helpers (`panDragStart` / `panDragMove` / `panTransform`)
+ *   so the pointer-event sequence is unit-testable without a DOM.
+ *
+ * Entities (spec §4/§6.2): every KNOWN_AGENTS roster member renders a card —
+ * title = the AGENT NAME (role id, or displayName for idle cards via
+ * `entity.name`); the session id / task tag are AUXILIARY record fields on
+ * `data-agent-record` (never the title). Idle (no dispatch evidence) cards
+ * are muted (`data-agent-idle`); lit cards follow the projection's status
+ * priority (running/settled/error/denied/advisory). Settled cards get a
+ * standalone GREEN DONE FRAME + green ✓ (Task 8 — user feedback #1/#3:
+ * `data-agent-done="true"`, the frame is a full-strength success ring on the
+ * rounded card body) ONLY when `emphasis !== 'off'` — an off-tier role
+ * (already-passed / stage-less on-demand + general) never shows the
+ * completion marker (the v3 leak: the ✓ survived the off-tier low
+ * transparency).
+ *
+ * Shared iteration section (Task 8 — user feedback #4): the page renders the
+ * SAME `IterationInfoSection` the tasks tab uses, from the SAME
+ * `view.iteration` data — 两个 tab 显示同一迭代信息块.
+ *
+ * Edges (spec §4 + plan 20260812-panel-f5-design-system Task 5 — the
+ * finalized 2026-08-12 line semantics, design doc §2): ONLY the actual
+ * handoffs (business entity→entity — role-keyed, general endpoints
+ * filtered, one edge per pair) and the supervise line (plan
+ * 20260812-panel-f5-agent-layout Task 2 — the static bidirectional
+ * implementor ↔ sdd-reviewer sub-bucket line inside the `sdd-implement`
+ * column, dim dashed by default, lit business when the projected
+ * `evidenced` flag is true — never a fabricated activation) — all drawn as
+ * SVG bezier `C` paths (design doc §2.6) over the layout computed by the
+ * exported pure `layoutAgents`. The `expected` stage skeleton and the
+ * animated `next` edge are REMOVED (user feedback #1/#5 — the column order
+ * implies the flow, the running card glow + status point carry the
+ * position). Every line anchors to a CARD PORT (4 fixed edge-midpoint
+ * ports, design doc §2.5 — hover-visible dots, static-invisible) or the
+ * supervise side-gap anchors (card right edge + 18px); the arrow tip sits
+ * at the STANDOFF point 10px off the target port (arrow along the endpoint
+ * tangent — H1) and no line crosses text (H2: standoff + side-gap routing
+ * for caption-crossing same-column flows + column-gap crossings). Col-skip
+ * cross-column edges (plan QC tri R1 — a source/target pair whose columns
+ * are separated by an intermediate column, e.g. writing-specialist →
+ * qc-specialist) reroute via a multi-`L` side-gap DETOUR below the
+ * intermediate card band instead of a direct bezier through the card bodies
+ * (H1).
+ *
+ * Layout (plan 20260812-panel-f5-agent-layout Task 2 + plan
+ * 20260812-panel-f5-design-system Task 5 + Task 8 — the F5 rework; plan
+ * 20260813-panel-agent-canvas-legend-layout Task 2 — the left-right
+ * rework): deterministic columns per EXPECTED_ROLE_FLOW stage
+ * (review-edit-chain → sdd-implement → qc-tri → qa-gate) — FOUR columns
+ * total (user 2026-08-12 feedback #3: the standalone rightmost UNKNOWN
+ * column is REMOVED; `zone: 'general'` entities render in an "unknown /
+ * 未匹配角色" SUB-PARTITION at the bottom of the LAST column,
+ * `data-sub-bucket="unknown"`), laid out in TWO SIDE-BY-SIDE PHASE GROUPS
+ * (Task 8 — user feedback #2; Task 2 — user 2026-08-13 feedback #2): the
+ * Phase 1 group LEFTMOST (review-edit-chain — the sequential Review & Edit
+ * chain: product-manager → architect → writing-specialist) and the Phase 2
+ * group to its RIGHT (sdd-implement → qc-tri → qa-gate — the iterative plan
+ * loop, annotated with the current `activePlanId` from the projected
+ * `state.plans[]` InProgress rows), top-aligned on ONE label row, each with
+ * its group label (`data-canvas-group`). The
+ * `sdd-implement` column is split into sub-buckets by the PROJECTED
+ * `entity.bucket` (never a render guess): the implementor partition above —
+ * flow roles in the stage's original order, then the on-demand roles
+ * (ops-engineer / prompt-engineer, carrying the on-demand badge) — and the
+ * reviewer partition (code-reviewer, idle included) below, with the
+ * implementor / sdd-reviewer caption labels. `zone: 'on-demand'` entities
+ * have NO standalone column anymore — they live in the implementor
+ * partition. The former F4.2 "general sinks to the bottom of
+ * the sdd-implement column" placement is superseded (Task 2), as is the
+ * Task-2 rightmost unknown column (Task 5); the former
+ * sdd-implement → general SDD loop back-edge stays REMOVED (the render
+ * draws no loop branch).
+ *
+ * Degradation (spec §8 — never throws / never orange): the projection always
+ * yields the full idle roster, so the canvas renders it with the muted
+ * `data-canvas-note` (degraded = ledger missing; empty = no events;
+ * settle-only = events but no dispatch rows — review T2-Imp-2 restored the
+ * old zone's distinct settle-only anchor; F-002: the empty/settle-only note
+ * is PROJECTED metadata, never inferred from the entity list). The Legend
+ * (idle / collaboration swatches, plan Task 3) sits BELOW the viewport
+ * (plan 20260813-panel-quick-fixes Task 3 — user 2026-08-13 feedback).
+ * `initialPan` is a deterministic SSR/test seed — the live page starts at the
+ * origin.
+ */
+import * as React from 'react';
+import type { TranslateNS } from '@deepseek-ai/dsh-client-ui-slots';
+import type { AgentEdge, ZoneView } from '../graph/project-graph.ts';
+import { type PhaseId } from '../graph/schema.ts';
+export interface AgentCanvasPageProps {
+    /** The projected agents zone (spec §6.2 — `ZoneView['agents']`). */
+    view: ZoneView['agents'];
+    /** The projected iteration zone (spec §3) — the SHARED iteration info
+     * block (plan 20260812-panel-f5-design-system Task 8, user 2026-08-12
+     * feedback #4): BOTH the tasks tab and this page render the SAME
+     * `IterationInfoSection` from the SAME `view.iteration` data. */
+    iteration: ZoneView['iteration'];
+    t: TranslateNS<'mstar-panel'>;
+    /** Deterministic initial pan seed (SSR/tests); the live page starts at the origin. */
+    initialPan?: PanState;
+}
+/** Pan state: the content-layer translate (spec §6.2 — free pan, no bounds). */
+export interface PanState {
+    x: number;
+    y: number;
+}
+/** A live drag gesture: the pan at pointerdown + the pointer start position. */
+export interface PanDrag {
+    originX: number;
+    originY: number;
+    startX: number;
+    startY: number;
+}
+export declare const PAN_ORIGIN: PanState;
+/** Open a drag gesture: remember the pan at pointerdown and the pointer seat. */
+export declare function panDragStart(pan: PanState, x: number, y: number): PanDrag;
+/** Follow the pointer: pan = origin + (current − start) — free pan (spec §6.2). */
+export declare function panDragMove(drag: PanDrag, x: number, y: number): PanState;
+/** The `data-canvas-pan` transform string (spec §6.2 — translate only). */
+export declare function panTransform(pan: PanState): string;
+/** One positioned box in the canvas coordinate space. */
+export interface CanvasBox {
+    x: number;
+    y: number;
+    w: number;
+    h: number;
+}
+/** One stage column track (expected/next edge anchors + the column label). */
+export interface CanvasColumn extends CanvasBox {
+    id: string;
+}
+/**
+ * One PHASE group of the canvas (plan 20260812-panel-f5-design-system Task 8
+ * — user 2026-08-12 feedback #2; plan
+ * 20260813-panel-agent-canvas-legend-layout Task 2 — the left-right
+ * rework): the stage columns split into two SIDE-BY-SIDE groups by iteration
+ * phase — **Phase 1** (review-edit-chain, the sequential Review & Edit
+ * chain: product-manager → architect → writing-specialist) LEFTMOST,
+ * **Phase 2** (sdd-implement → qc-tri → qa-gate, the iterative plan loop) to
+ * its RIGHT — every group label row TOP-ALIGNED at PAD_Y; the Phase-2 row
+ * additionally annotates the CURRENT PLAN (the projected `activePlanId` —
+ * the first InProgress `state.plans[]` row, design doc §1.2). Group order =
+ * first occurrence in the projected stage order (PHASE_IDS-aligned) —
+ * derived, never literal, so a phase/stage rename can never orphan the
+ * groups.
+ */
+export interface CanvasGroup {
+    /** The group's iteration phase id. */
+    phase: PhaseId;
+    /** 1-based group ordinal in stage order (Phase 1 = 1, Phase 2 = 2). */
+    index: number;
+    /** The group label row seat (canvas coordinates; width = the group's
+     * content width — the Phase-2 current-plan chip rides the same row). */
+    label: {
+        x: number;
+        y: number;
+        w: number;
+        h: number;
+    };
+    /** The stage column ids of this group, stage order. */
+    columnIds: readonly string[];
+    /** Current-plan annotation host (design doc §1.2 — user feedback #2):
+     * true for the `autonomous-execute` phase group (the iterative plan loop)
+     * only. */
+    planNote: boolean;
+}
+/** The deterministic canvas geometry: stage columns + per-entity card boxes. */
+export interface CanvasLayout {
+    width: number;
+    height: number;
+    columns: readonly CanvasColumn[];
+    cards: ReadonlyMap<string, CanvasBox>;
+    /** Sub-bucket geometry per column id (plan 20260812-panel-f5-agent-layout
+     * Task 2): the `sdd-implement` column's implementor/reviewer caption seats
+     * + card bands — the supervise line anchors to the band edges (the
+     * inter-partition gap; QC W-001).
+     * Columns without sub-buckets are absent from the map. */
+    subBuckets: ReadonlyMap<string, SubBucketGeometry>;
+    /** The unknown sub-partition at the bottom of the LAST column (plan
+     * 20260812-panel-f5-design-system Task 5 — user 2026-08-12 feedback #3:
+     * `zone: 'general'` entities sink into a qa-gate-column-bottom sub-partition
+     * instead of a standalone fifth column). The caption seat + card band;
+     * null when the layout has no columns (total function — never a throw). */
+    unknown: UnknownSubPartition | null;
+    /** The Phase groups (plan 20260812-panel-f5-design-system Task 8 — user
+     * 2026-08-12 feedback #2; plan
+     * 20260813-panel-agent-canvas-legend-layout Task 2): Phase 1 leftmost /
+     * Phase 2 right, top-aligned, each with its label seat; empty when the
+     * layout has no columns. */
+    groups: readonly CanvasGroup[];
+}
+/** The unknown sub-partition id (plan 20260812-panel-f5-design-system Task 5
+ * — design doc §1.2): `zone: 'general'` entities render in a bottom
+ * sub-partition of the LAST column titled「unknown / 未匹配角色」and marked
+ * `data-sub-bucket="unknown"`. The former standalone rightmost UNKNOWN column
+ * (plan 20260812-panel-f5-agent-layout Task 2) is REMOVED — the constant
+ * value survives as the sub-partition bucket id. */
+export declare const UNKNOWN_COLUMN = "unknown";
+/** One sub-bucket partition inside the `sdd-implement` column (plan
+ * 20260812-panel-f5-agent-layout Task 2): the caption seat + the cards'
+ * band — the supervise line anchors to the band's edge (implementor:
+ * bottom edge; reviewer: top edge — the inter-partition gap; QC W-001). */
+export interface SubBucketPartition {
+    /** The caption row's top-left seat (canvas coordinates; width = the card
+     * row width so the dashed rule fills the row). */
+    label: {
+        x: number;
+        y: number;
+        w: number;
+    };
+    /** The bucket's card bounding band (canvas coordinates); null when the
+     * partition has no cards (total function — the caption and the supervise
+     * line skip). */
+    band: CanvasBox | null;
+}
+/** The sub-bucket geometry of one column (plan f5 Task 2): implementor +
+ * reviewer partitions. Present ONLY for the `sdd-implement` column — the
+ * supervise anchors read the bands. */
+export interface SubBucketGeometry {
+    implementor: SubBucketPartition;
+    reviewer: SubBucketPartition;
+}
+/** The unknown sub-partition of the LAST column (plan 20260812-panel-f5-design-system
+ * Task 5 — design doc §1.2): the caption seat + the general cards' band. The
+ * caption row (SUB_LABEL_H) sits ROW_GAP below the last flow card; the
+ * general cards follow SUB_GAP below it. */
+export interface UnknownSubPartition {
+    /** The caption row's top-left seat (canvas coordinates; width = the card
+     * row width so the dashed rule fills the row). */
+    label: {
+        x: number;
+        y: number;
+        w: number;
+    };
+    /** The unknown partition's card bounding band; null when the partition has
+     * no general card (total function — the caption renders only with cards). */
+    band: CanvasBox | null;
+}
+/**
+ * Deterministic canvas layout (spec §4 + plan 20260812-panel-f5-agent-layout
+ * Task 2 + plan 20260812-panel-f5-design-system Task 5 + Task 8 + plan
+ * 20260813-panel-agent-canvas-legend-layout Task 2 — the F5 rework + the
+ * left-right rework): one column per EXPECTED_ROLE_FLOW stage (view order:
+ * review-edit-chain → sdd-implement → qc-tri → qa-gate) — FOUR columns
+ * total, laid out in TWO SIDE-BY-SIDE PHASE GROUPS (Task 8, user 2026-08-12
+ * feedback #2; Task 2, user 2026-08-13 feedback #2): the **Phase 1 group
+ * LEFTMOST** (review-edit-chain — the sequential Review & Edit chain:
+ * product-manager → architect → writing-specialist) and the **Phase 2 group
+ * to its RIGHT** (sdd-implement → qc-tri → qa-gate — the iterative plan
+ * loop, annotated with the current `activePlanId`), every group label row
+ * TOP-ALIGNED at PAD_Y (design doc §1.2; the standalone rightmost unknown
+ * column is REMOVED — Task 5, user feedback #3). The `sdd-implement` column
+ * is split into sub-buckets by the
+ * PROJECTED `entity.bucket` (never a render-side guess): the implementor
+ * partition above — flow roles in the stage's original EXPECTED_ROLE_FLOW
+ * order, then the on-demand roles (ops-engineer / prompt-engineer — the
+ * standalone on-demand column is REMOVED) — and the reviewer partition
+ * (code-reviewer) below, with the implementor / sdd-reviewer caption seats +
+ * card bands recorded in `subBuckets` (the supervise-line anchors).
+ * `zone: 'general'` entities (the general bucket — unmatched / anonymous
+ * dispatches) render in the "unknown / 未匹配角色" SUB-PARTITION at the
+ * bottom of the LAST column (`layout.unknown` — design doc §1.2: caption row
+ * ROW_GAP below the last flow card, general cards SUB_GAP below it). The
+ * column bucket comes from the PROJECTED `entity.zone`: 'flow' → the
+ * entity's stage column, 'on-demand' → the sdd-implement column's implementor
+ * partition, 'general' → the last column's unknown partition. Total function —
+ * every entity gets a box; absent sdd-implement stage → on-demand falls back
+ * to the LAST column; unknown column ids fall back to the same sink; no
+ * stages → empty groups/columns; never a throw.
+ */
+export declare function layoutAgents(view: ZoneView['agents']): CanvasLayout;
+/** The fixed port points of a card box (design doc §2.5 — 4 edge-midpoint
+ * ports, no new tokens). */
+export type PortId = 'north' | 'south' | 'west' | 'east';
+/** One edge's bezier geometry (design doc §2.6): the `d` path + the
+ * endpoint coordinates (start = the source port, end = the target STANDOFF
+ * point — the arrow tip lands there, 10px off the card border H1). Null
+ * when an anchor is missing (total function). */
+export interface EdgeGeometry {
+    /** The SVG path `d` — a single `C` cubic-bezier command for the standard
+     * curves, or the multi-command `M … L … L … L … L … L …` side-gap detour
+     * polyline for col-skip cross-column edges (plan QC tri R1). The render
+     * passes `d` through verbatim; `marker-end orient="auto"` follows the
+     * FINAL segment, so the arrow always rides the endpoint tangent (H1). */
+    d: string;
+    x1: number;
+    y1: number;
+    x2: number;
+    y2: number;
+}
+/**
+ * One edge's SVG bezier geometry (plan 20260812-panel-f5-design-system Task
+ * 5 — design doc §2.5/§2.6); null when an anchor is missing (total
+ * function).
+ *
+ * Port selection (design doc §2.5 — lines connect ports only, never through
+ * a card): forward (source column < target column) → source EAST → target
+ * WEST; reverse (source column > target column) → source WEST → target
+ * EAST; same column → the vertical flow (direction-aware, QC W-001). The
+ * path END stands off STANDOFF px from the target port along the endpoint
+ * tangent (arrow tip off the card, H1); the source starts AT its port (no
+ * arrow there).
+ *
+ * Direction-aware vertical endpoints (plan QC tri qc3 W-001): a same-column
+ * (or side-gap) flow whose SOURCE sits BELOW the target — the implement →
+ * review → rework cycle collapses to `code-reviewer → fullstack-dev` (the
+ * projection pair-dedupe keeps the LATEST direction) — must approach the
+ * target's SOUTH port, not its north: the arrow tip lands `standoff` below
+ * the target's bottom edge pointing UP into it. The old code put the tip
+ * above the target (pointing AWAY) and the center-x line ran through both
+ * card bodies (H1/H2 violations). Forward (source above) keeps source SOUTH
+ * → target NORTH. The reverse side-gap detour below is direction-aware by
+ * construction (it enters the target from its RIGHT side gap and lands 10px
+ * off the EAST edge, tip pointing LEFT into the card).
+ *
+ * Same-column flows whose center-x vertical line would cross a sub-bucket
+ * CAPTION row (the implementor↔reviewer flow crosses the "sdd-reviewer"
+ * caption, the qa-gate↔unknown flow crosses the「unknown / 未匹配角色」
+ * caption) OR another CARD body (a handoff between non-adjacent cards, e.g.
+ * fullstack-dev → frontend-dev skips the idle fullstack-dev-2 — the
+ * 2026-08-13 "线穿过卡片" report) route in the column's LEFT side gap instead
+ * (design doc §2.0 绕行策略 ② — 同列关系线移到卡片列外侧的间隙带): the vertical
+ * bezier hangs at `card left edge − SIDE_GAP`, clear of every text (H2) and
+ * every card body (H1).
+ *
+ * Inter-phase flows (plan 20260812-panel-f5-design-system Task 8 + plan
+ * 20260813-panel-agent-canvas-legend-layout Task 2 — the left-right
+ * layout): a Phase 1 → Phase 2 handoff (e.g. writing-specialist →
+ * fullstack-dev — a real same-plan Review&Edit→implement transfer) is a
+ * normal FORWARD horizontal bezier (source east → target west) — the groups
+ * sit side-by-side at one top-aligned y band, so no label row lies between
+ * the cards. The CARD-AWARE guard (plan QC tri R1 — 绕行策略 ③): a
+ * cross-column edge whose columns SKIP an intermediate column (e.g.
+ * writing-specialist → qc-specialist — a real docs-only / inline / QA-gate
+ * ledger chain) would run its direct horizontal bezier THROUGH the
+ * intermediate column's card bodies; when the direct bbox intersects ANY
+ * card box other than the source/target cards, the edge reroutes via the
+ * side-gap DETOUR (see `sideGapDetour`) — a polyline below the intermediate
+ * band, clear of every card (H1) and text seat (H2).
+ */
+export declare function edgePath(edge: AgentEdge, layout: CanvasLayout): EdgeGeometry | null;
+export declare function AgentCanvasPage({ view, iteration, t, initialPan }: AgentCanvasPageProps): React.JSX.Element;

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

@@ -0,0 +1,48 @@
+/**
+ * EventLogPage (spec panel-tabs §5, plan 20260811-panel-event-log Task 2) —
+ * the 事件记录 tab: a NON-canvas log page. Two partitions (spec §5):
+ * Agent 流转事件 (`view.events` ≤50 latest-first — unexpected dispatches
+ * fold in via the `expected` flag, NEVER double-appended; the unexpected
+ * badge is DISPATCH-only — settle rows are completion records whose
+ * projected `expected` is always false, they never flag as unexpected,
+ * F-001) and 违规记录
+ * (`view.violations`). Every row is an expandable native `<details>` (no-JS,
+ * keyboard-accessible, SSR-stable) whose body shows the FULL catalog fields;
+ * a missing field renders「—」— never a guessed value (spec §5/§8).
+ *
+ * Layout (plan 20260811-panel-f3-agent-general Task 2 — 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`).
+ *
+ * Dock migration decision (spec §5 — 无双份日志): the AgentEventDock is
+ * REMOVED, not degraded. The dock's content (row layout + status chips)
+ * moved into this page, and its host (the WorkflowCanvas canvas-corner)
+ * died with the tabs-shell plan — a dock-side "jump to 事件记录" entry would
+ * only duplicate the header TabNav, which already IS the jump to this tab.
+ * Zero `data-agent-event-dock` anchors remain repo-wide (Task 2 完成判据).
+ *
+ * Row data: `eventLogEntries(view)` (Task 1 — pure assembly; every field
+ * degrades individually). The `<details>` body backfills the FULL source
+ * fields (planId / taskId / taskCategory — not carried by the floor
+ * `EventLogEntry`) through a one-time id → `FlowEventView` map (T1-Min-3:
+ * the assembly function stays pure/unchanged; an unmatched id degrades the
+ * backfilled fields to「—」like any missing value).
+ *
+ * Anchors (spec §6.4 — the `data-event-log-*` family): the page root
+ * `data-mstar-page="events"`; `data-event-log-section` (+ `-section-count`)
+ * for the partitions; `data-event-log-row-kind` / `-row-id` per row;
+ * `data-event-log-details` per expandable row; `data-event-log-field` (+
+ * `data-event-log-missing="true"`) per detail-body field; `data-event-log-empty`
+ * (both-empty) / `data-event-log-empty-section` (mixed empty) for the muted
+ * empty states — never an orange warn frame (spec §8).
+ */
+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 EventLogPageProps {
+    /** The projected zone view — the events/violations slices + source rows. */
+    view: ZoneView;
+    t: TranslateNS<'mstar-panel'>;
+}
+export declare function EventLogPage({ view, t }: EventLogPageProps): React.JSX.Element;

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

@@ -0,0 +1,80 @@
+/**
+ * IterationInfoSection (spec panel-tabs §3, plan 20260812-panel-f5-design-system
+ * Task 8 — the SHARED iteration info block, user 2026-08-12 feedback #4): the
+ * Content Head — iteration summary (the collapsible toggle row) + the 5
+ * horizontal iteration steps + 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).
+ * One implementation, two mounts — 任务迭代与代理执行共用同一迭代信息块.
+ *
+ * The component is extracted VERBATIM from the former inline head of
+ * IterationTaskPage (its history, contracts and anchors stay unchanged):
+ *
+ * - 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 — QC wave). The
+ *   expanded body renders the Steps HORIZONTALLY as 5 EQUAL full-width unit
+ *   blocks (plan 20260811-panel-f2-quickfix Item 1 — 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 20260811-panel-f4-iteration-zone
+ *   Task 2 (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;
+ *   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.
+ *
+ * Collapse/expand (spec §3 / Task 2 brief): a local `useState` defaulted to
+ * the iteration state — `active === false` → collapsed to a one-line summary
+ * (iterationId/verdict + the muted "not started" note, expandable to the idle
+ * 5-step skeleton); `active === true` → expanded. SSR-stable: the default is
+ * data-derived, so `renderToStaticMarkup` renders a deterministic state per
+ * row that tests can pin statically. Live re-sync (Task 2 review
+ * Important-1): a useEffect re-expands the head when the SAME mounted
+ * instance sees `active` flip false→true on a catalog update (started
+ * iterations must show the expanded steps, spec §3); the transition is
+ * one-way — user collapse while already active is never overridden.
+ *
+ * Degradation (spec §8): the projection never throws — an inactive/missing
+ * iteration renders the collapsed muted summary; the head is a pure render of
+ * the projected `iteration` object (never guesses values).
+ */
+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 IterationInfoSectionProps {
+    /** The projected iteration zone (spec §3 — the SAME data both tabs show). */
+    iteration: ZoneView['iteration'];
+    t: TranslateNS<'mstar-panel'>;
+}
+/**
+ * Activation re-sync (Task 2 review Important-1): the collapse/expand state
+ * must follow a LIVE `active` flip on the SAME mounted instance — spec §3
+ * says 启动迭代才展开 (an active iteration shows the expanded steps), and a
+ * fresh catalog row can flip `iteration.active` false→true without a remount.
+ * The transition is one-way: only the INACTIVE → ACTIVE edge forces expand;
+ * a user collapse while already active is never overridden, and a live
+ * true→false deactivation keeps the user's current view (the muted
+ * "not started" note + collapsed affordance still render per `active`).
+ *
+ * Pure transition (exported for the render-test transition table): the head
+ * expands iff the iteration just became active; otherwise the user's state
+ * wins.
+ */
+export declare function nextExpandedOnActivation(prev: boolean, prevActive: boolean, nextActive: boolean): boolean;
+/**
+ * The split-layout wrapper decision (spec panel-f4 §2.3 R8, plan f4.3 Task 2
+ * — 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
+ * (a user manually expands an inactive head → the 5-step idle skeleton
+ * without the split). 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.
+ */
+export declare function iterationSplitActive(active: boolean, branches: ZoneView['iteration']['branches']): boolean;
+export declare function IterationInfoSection({ iteration, t }: IterationInfoSectionProps): React.JSX.Element;

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

@@ -0,0 +1,37 @@
+/**
+ * IterationTaskPage (spec panel-tabs §3, plan 20260811-panel-tabs-shell
+ * Task 2) — the 任务迭代 tab: the SHARED IterationInfoSection (iteration
+ * summary + the 5 horizontal iteration steps + branches — the same block the
+ * agents tab renders, plan 20260812-panel-f5-design-system Task 8, user
+ * 2026-08-12 feedback #4) above the full-width standard kanban. 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
+ * 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.
+ *
+ * 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.
+ */
+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 IterationTaskPageProps {
+    view: ZoneView;
+    t: TranslateNS<'mstar-panel'>;
+}
+export declare function IterationTaskPage({ view, t }: IterationTaskPageProps): React.JSX.Element;

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

@@ -0,0 +1,18 @@
+/**
+ * Sidebar bottom meta dock (spec panel-zones §5): the durable identity line —
+ * mstar version + harness dir — in a small muted panel pinned below the
+ * scrolling digest (hairline-separated, does NOT scroll with the sidebar).
+ *
+ * The `watermark.*` locale values (reused from the removed header) render the
+ * two lines; `data-mstar-watermark` is preserved here so existing degradation
+ * anchors keep working. Degradation stays total: missing version → `unknown`,
+ * null harness dir → `none` (never a crash, never a guessed value).
+ */
+import * as React from 'react';
+import type { TranslateNS } from '@deepseek-ai/dsh-client-ui-slots';
+import type { MstarEngineStatusSource } from '../../types.ts';
+export interface PanelMetaProps {
+    t: TranslateNS<'mstar-panel'>;
+    source: MstarEngineStatusSource;
+}
+export declare function PanelMeta({ t, source }: PanelMetaProps): React.JSX.Element;

package/dist/client/panel/plan-sort.d.ts

@@ -0,0 +1,54 @@
+/**
+ * Sidebar / Done-column plan ordering (spec panel-zones §3): the hard-coded
+ * digitized sort keys shared by the sidebar plan board (this plan, Task 3)
+ * and the canvas Done column (plan 20260810-panel-canvas-zones reuses the
+ * same rule). Pure function — no rendering, no state.
+ *
+ * Keys, compared in order (all DESC):
+ *   1. `doneAt` matching /^\d{4}-\d{2}-\d{2}$/ → '.replaceAll('-','')'
+ *      digitized (e.g. '2026-08-08' → '20260808'); non-matching (missing /
+ *      garbage) → empty key (sorts last).
+ *   2. fallback: `id` first 8 chars when /^\d{8}/ → that 8-digit key, DESC.
+ *   3. tie-break: `id` lexicographic DESC (deterministic, testable).
+ */
+/** Sidebar plan cap (spec §5): show ≤5 rows + `+N more`. */
+export declare const PLAN_CAP = 5;
+/** Residual findings cap (spec §5): show ≤10 rows + overflow hint. */
+export declare const FINDINGS_CAP = 10;
+/**
+ * Spec §3 comparator (all keys DESC). The digitized keys are 8-digit strings,
+ * so plain string DESC comparison is numeric-correct; the id tie-break is
+ * plain lexicographic DESC.
+ */
+export declare function comparePlans(a: {
+    readonly id: string;
+    readonly doneAt: string | null;
+}, b: {
+    readonly id: string;
+    readonly doneAt: string | null;
+}): number;
+/**
+ * Sorted copy in spec §3 order (stable — input order preserved within equal
+ * keys, so the result is deterministic for any input).
+ */
+export declare function sortPlans<T extends {
+    readonly id: string;
+    readonly doneAt: string | null;
+}>(plans: readonly T[]): T[];
+/**
+ * The「最近一次迭代」recency comparator (plan 20260813-panel-quick-fixes Task
+ * 2 — shared by the current-iteration filter in `project-graph.ts`, which
+ * previously duplicated this order as a local `moreRecentPlan`). DIFFERENT
+ * key order from {@link comparePlans}: the 8-digit id-date prefix is PRIMARY,
+ * doneAt SECONDARY — the projection's former `moreRecentPlan` behavior, kept
+ * EXACTLY. All keys DESC: `< 0` means `a` is more recent than `b` (id-date
+ * prefix, then digitized doneAt, then id lexicographic DESC for
+ * determinism).
+ */
+export declare function comparePlansByIterationRecency(a: {
+    readonly id: string;
+    readonly doneAt: string | null;
+}, b: {
+    readonly id: string;
+    readonly doneAt: string | null;
+}): number;

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

@@ -0,0 +1,17 @@
+/**
+ * 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.
+ * Degradation: `state === null` renders the no-state note instead of the
+ * digest (never a crash); the meta dock still renders from the source.
+ */
+import * as React from 'react';
+import type { TranslateNS } from '@deepseek-ai/dsh-client-ui-slots';
+import type { MstarEngineStatusSource, MstarHarnessState } from '../../types.ts';
+export interface SidebarProps {
+    t: TranslateNS<'mstar-panel'>;
+    state: MstarHarnessState | null;
+    source: MstarEngineStatusSource;
+}
+export declare function Sidebar({ t, state, source }: SidebarProps): React.JSX.Element;

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

@@ -0,0 +1,23 @@
+/**
+ * Workspace-state section (spec panel-zones §5): plan board (≤5 in spec §3
+ * time-desc order + `+N more`), open residual findings (≤10 — R# + severity
+ * chip + title/planId + overflow hint), policy anchors with enforcement
+ * FIRST (from `source.enforcement` — top level, not state), lease anchors,
+ * knowledge digest and the direction one-liner. Pure render with per-field
+ * degradation — missing fields render `none` / `unknown`, empty lists render
+ * `none`, never crash.
+ *
+ * The branches block was removed from the sidebar in this task (moved to the
+ * iteration zone, plan 20260810-panel-canvas-zones); the branch anchor fields
+ * stay in the catalog source (the iteration zone consumes them).
+ */
+import * as React from 'react';
+import type { TranslateNS } from '@deepseek-ai/dsh-client-ui-slots';
+import type { MstarEngineStatusSource, MstarHarnessState } from '../../types.ts';
+export interface StateSectionProps {
+    t: TranslateNS<'mstar-panel'>;
+    state: MstarHarnessState;
+    /** Top-level enforcement flag (spec §2.1) — NOT part of the state digest. */
+    enforcement: MstarEngineStatusSource['enforcement'];
+}
+export declare function StateSection({ t, state, enforcement }: StateSectionProps): React.JSX.Element;