@mstar-harness/dsh 3.6.3 → 3.7.0

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

@@ -10,7 +10,7 @@
  * 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)
+ * `compassStatus: 'active'` field
  * 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).
@@ -19,7 +19,7 @@
 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-unknown` catch-all (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];
@@ -32,7 +32,7 @@ export interface PhaseEdge {
 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 ⇄). */
+ *  Task 1 — the merged column docks the Blocked ⇄). */
 export declare const PLAN_STATE_EDGES: {
     source: PlanStateId;
     target: PlanStateId;
@@ -62,29 +62,27 @@ export declare const TRANSITION_TO_PHASE: Readonly<Record<string, PhaseId>>;
  * - 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
+ * Off-pipeline roles  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
+ * dimensions, see
  * SDD_BUCKET_ROLES). The single `general` bucket (plan
- * 20260811-panel-f3-agent-general) collects every unmatched / anonymous
+ * 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
+ * General-bucket PLACEMENT: 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
+ * render places them in that rightmost column. The earlier
  * placement (BOTTOM INSIDE the `sdd-implement` column bucket) is
- * superseded by the F5 user decision; the former SDD implement ↔ review
+ * superseded by the F5; 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
+ * stays REMOVED from the projection ; 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
@@ -103,15 +101,14 @@ export interface ExpectedRoleStage {
     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
+ * §2.3; — `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 sub-bucket membership : 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
@@ -132,7 +129,7 @@ export declare const SDD_BUCKET_ROLES: {
 };
 /**
  * The known-agent roster (spec §4 / §6.2 / decision point D3 + plan
- * 20260811-panel-f3-agent-general + plan 20260812-panel-f5-agent-layout Task
+ *  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`
@@ -142,13 +139,13 @@ export declare const SDD_BUCKET_ROLES: {
  * 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
+ * : 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
+ *  Item 2): 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.
@@ -160,16 +157,14 @@ export declare const SDD_BUCKET_ROLES: {
  * 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
+ * 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
+ *. *
+ * General-bucket placement : 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).
+ * zone VALUE is unchanged — placement is a render-layer decision).
  */
-/** The general-bucket id (plan 20260811-panel-f3-agent-general): the single
+/** The general-bucket id : 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 '' +
@@ -178,24 +173,23 @@ export declare const SDD_BUCKET_ROLES: {
  * 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):
+ * Placement:
  * the bucket gets its OWN rightmost UNKNOWN canvas column — the render
- * (Task 2) places `zone: 'general'` entities there; the former F4.2
+ * places `zone: 'general'` entities there; the former
  * 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),
+ * Agent-entity column zone : `'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.
+ * REMOVED ) or `'general'` (the general bucket). Placement
+ * semantics ( decision): `'general'` renders in its OWN
+ * rightmost UNKNOWN column . The zone VALUE is projection-owned and
+ * unchanged; only the render layout  changes.
  */
 export type AgentZone = 'flow' | 'on-demand' | 'general';
 export interface KnownAgent {
@@ -208,17 +202,17 @@ export interface KnownAgent {
         phase: PhaseId;
         stage: string;
     } | null;
-    /** Off-pipeline zone (plan 20260811-panel-f3-agent-general): 'on-demand'
+    /** Off-pipeline zone : '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
+     * ), '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). */
+ * excluded; `code-reviewer` added by
+ * — upstream v2.1.1 roles.ts is the semantic SSOT). */
 export declare const KNOWN_AGENTS: readonly KnownAgent[];

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

@@ -5,41 +5,41 @@
  * 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
+ * (spec panel-zones §2): 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
+ * gate-verdict labels reused by the 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.*`
+ * (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 —
+ * (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),
+ * Blocked/unknown column),
  * `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
+ * (spec panel-zones §4): 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).
+ * keys were removed with the AgentFlowZone (the free canvas renders neither,
+ * so they had zero consumers).
  *
- * T3 (same plan): the dock is collapsible (the frame is a native <details>,
+ * (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
@@ -49,38 +49,38 @@
  * 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
+ * (spec panel-tabs §2/§6.1): 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
+ * (spec panel-tabs §3): 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
+ * (spec panel-tabs §4): 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)
+ *  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
+ * T2 : 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
+ * (the layout rework
+ * supersedes the earlier 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
@@ -92,7 +92,7 @@
  * (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
+ * (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
@@ -104,13 +104,13 @@
  * `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
+ * T3 : 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
+ * (图例精简): 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

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

@@ -1,7 +1,7 @@
 /**
- * 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
+ * AgentCanvasPage (spec panel-tabs §4/§6.2
+ * — the 代理执行 tab: a DRAGGABLE agent canvas. Replaces the muted
+ * placeholder page  and the stage-column AgentFlowZone
  * (deleted by this plan — the free canvas supersedes it).
  *
  * Canvas contract (spec §6.2 — zero third-party deps):
@@ -29,28 +29,28 @@
  * `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:
+ * standalone GREEN DONE FRAME + green ✓ (
  * `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
+ * Shared iteration section : 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
+ * Edges (spec §4 — 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
+ *  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
+ * animated `next` edge are REMOVED ( — 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
@@ -58,22 +58,17 @@
  * 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
+ * cross-column edges  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
+ * Layout : 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
+ * total (: 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
+ * — 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
@@ -87,9 +82,9 @@
  * 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
+ * partition. The former "general sinks to the bottom of
+ * the sdd-implement column" placement is superseded, as is the
+ * rightmost unknown column; the former
  * sdd-implement → general SDD loop back-edge stays REMOVED (the render
  * draws no loop branch).
  *
@@ -97,10 +92,9 @@
  * 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
+ * old zone's distinct settle-only anchor; 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).
+ * (idle / collaboration swatches) sits BELOW the viewport.
  * `initialPan` is a deterministic SSR/test seed — the live page starts at the
  * origin.
  */
@@ -112,8 +106,7 @@ 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
+     * 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'>;
@@ -151,10 +144,7 @@ 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
+ * One PHASE group of the canvas : 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
@@ -180,7 +170,7 @@ export interface CanvasGroup {
     };
     /** The stage column ids of this group, stage order. */
     columnIds: readonly string[];
-    /** Current-plan annotation host (design doc §1.2 — user feedback #2):
+    /** Current-plan annotation host (design doc §1.2 —):
      * true for the `autonomous-execute` phase group (the iterative plan loop)
      * only. */
     planNote: boolean;
@@ -191,34 +181,31 @@ export interface CanvasLayout {
     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
+    /** Sub-bucket geometry per column id (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:
+     *  Task 5 —:
      * `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
+    /** The Phase groups (user
      * 2026-08-12 feedback #2; plan
-     * 20260813-panel-agent-canvas-legend-layout Task 2): Phase 1 leftmost /
+     * 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
+/** The unknown sub-partition id : `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
+ *  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'
+ * 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 {
@@ -234,15 +221,14 @@ export interface SubBucketPartition {
      * line skip). */
     band: CanvasBox | null;
 }
-/** The sub-bucket geometry of one column (plan f5 Task 2): implementor +
+/** The sub-bucket geometry of one column : 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
+/** The unknown sub-partition of the LAST column : 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 {
@@ -258,19 +244,18 @@ export interface UnknownSubPartition {
     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
+ * Deterministic canvas layout (spec §4
+ * + Task 8 + plan
+ *  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
+ * total, laid out in TWO SIDE-BY-SIDE PHASE GROUPS (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
+ * column is REMOVED ). 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
@@ -300,7 +285,7 @@ export type PortId = 'north' | 'south' | 'west' | 'east';
 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
+     * polyline for col-skip cross-column edges . 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;
@@ -310,19 +295,18 @@ export interface EdgeGeometry {
     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
+ * One edge's SVG bezier geometry ; 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
+ * EAST; same column → the vertical flow (direction-aware. 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
+ * Direction-aware vertical endpoints : 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
@@ -344,13 +328,11 @@ export interface EdgeGeometry {
  * 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 →
+ * Inter-phase flows : 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
+ * the cards. The CARD-AWARE guard : 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

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

@@ -1,16 +1,16 @@
 /**
- * EventLogPage (spec panel-tabs §5, plan 20260811-panel-event-log Task 2) —
+ * EventLogPage (spec panel-tabs §5) —
  * 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 违规记录
+  * 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「左右
+ * 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`).
@@ -18,11 +18,11 @@
  * 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
+ * is gone — 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 完成判据).
+ * Zero `data-agent-event-dock` anchors remain repo-wide
  *
- * Row data: `eventLogEntries(view)` (Task 1 — pure assembly; every field
+ * Row data: `eventLogEntries(view)` (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: