@mstar-harness/dsh 3.6.3 → 3.7.0

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

@@ -1,6 +1,6 @@
 /**
- * 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
+ * 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
  * from the SAME `view.iteration` data (the tasks tab inside IterationTaskPage
@@ -12,14 +12,13 @@
  *
  * - 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
+ *   with aria-expanded + aria-controls pointing at the body). The
  *   expanded body renders the Steps HORIZONTALLY as 5 EQUAL full-width unit
- *   blocks (plan 20260811-panel-f2-quickfix Item 1 — badge/phase/chip
+ *   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 20260811-panel-f4-iteration-zone
- *   Task 2 (spec panel-f4 §2.3 R8/R9): the expanded body is a LEFT-RIGHT
+ *   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;
  *   each step reserves the fixed-height verdict seat (`data-step-verdict-seat`)
@@ -27,13 +26,12 @@
  *   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
+ * Collapse/expand (spec §3): 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
+ * row that tests can pin statically. Live re-sync: 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.
@@ -51,7 +49,7 @@ export interface IterationInfoSectionProps {
     t: TranslateNS<'mstar-panel'>;
 }
 /**
- * Activation re-sync (Task 2 review Important-1): the collapse/expand state
+ * Activation re-sync: 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.
@@ -66,7 +64,7 @@ export interface IterationInfoSectionProps {
  */
 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
+ * The split-layout wrapper decision (spec panel-f4 §2.3 R8
  * — 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

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

@@ -1,8 +1,8 @@
 /**
- * IterationTaskPage (spec panel-tabs §3, plan 20260811-panel-tabs-shell
- * Task 2) — the 任务迭代 tab: the SHARED IterationInfoSection (iteration
+ * IterationTaskPage (spec panel-tabs §3
+ * — 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
+ * agents tab renders, 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).

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

@@ -1,8 +1,7 @@
 /**
  * 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.
+ * digitized sort keys shared by the sidebar plan board (this plan)
+ * and the canvas Done column . Pure function — no rendering, no state.
  *
  * Keys, compared in order (all DESC):
  *   1. `doneAt` matching /^\d{4}-\d{2}-\d{2}$/ → '.replaceAll('-','')'
@@ -36,9 +35,7 @@ export declare function sortPlans<T extends {
     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
+ * The「最近一次迭代」recency comparator . 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

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

@@ -8,7 +8,7 @@
  * `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
+ * iteration zone); the branch anchor fields
  * stay in the catalog source (the iteration zone consumes them).
  */
 import * as React from 'react';

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

@@ -1,9 +1,9 @@
 /**
- * Legend (spec panel-tabs §4/§6.2, plan 20260811-panel-agent-canvas Task 3):
+ * 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
- * 20260813-panel-agent-canvas-legend-layout Task 1 (图例精简): the 7
+ *  Task 1 (图例精简): the 7
  * collaboration-edge / layout entries (flow-actual / port / group /
  * sub-bucket / supervise / on-demand / unknown) are REMOVED — the legend is
  * the 3 entity card treatments (running glow, settled = the standalone GREEN

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

@@ -1,6 +1,5 @@
 /**
- * ProjectRollup (plan `20260819-workflow-dsh-viz` Task 3 — compass v3.0.0
- * AC-4/AC-P3): the ADDITIVE project rollup zone of the tasks page — roadmap
+ * ProjectRollup : the ADDITIVE project rollup zone of the tasks page — roadmap
  * milestones + open-residual severity counts from the project layer
  * (`state.project`, produced by the catalog from `projects/<id>/roadmap.md`
  * frontmatter `milestones[]` + `projects/<id>/residuals.json` registers).

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

@@ -1,6 +1,5 @@
 /**
- * TaskBoard (plan 20260810-panel-canvas-zones Task 4, spec panel-zones §3;
- * plan 20260813-panel-quick-fixes Task 1) — the tasks-zone kanban: the 5
+ * 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

package/dist/gates/_shared.d.ts

@@ -79,9 +79,7 @@ export interface Config {
     roleMap?: Record<string, string>;
     /**
      * mstar role id → persona text — the native persona channel's only
-     * payload source (plan `20260814-dsh-fallbacks-integration` Task 2;
-     * channel reworked onto the native `SubagentStartRequest.persona` slot by
-     * plan `20260831-dsh-alpha2-optional-fallbacks` Task 3). A role-matched
+     * payload source . A role-matched
      * one-shot start merges the persona into the request's native `persona`
      * slot — dsh composes it as the scoped shadowing `deployment:persona`
      * section on the child, persists it in the child descriptor, and reapplies
@@ -103,7 +101,7 @@ export interface Config {
      */
     rolePersonas?: Record<string, string>;
     /**
-     * Workflow/ralph gate mode (plan `20260815-dsh-workflow-gate` W-B3, AC-7):
+     * Workflow/ralph gate mode :
      * `off` disables the gate entirely (workflow/ralph calls pass through
      * untouched, NO verdict row); `warn` (default) logs an advisory for
      * policy-unknown fan-out without ever blocking; `ask` routes first-seen
@@ -120,7 +118,7 @@ export interface Config {
      */
     workflowNames?: string[];
     /**
-     * Goal-bridge round cap (plan `20260816-dsh-nb2-goal-bridge` Task 2): the
+     * Goal-bridge round cap : the
      * flat `maxGoalRounds` the goal bridge passes to the goals service when it
      * mirrors the active iteration objective (bounds autonomous Phase 2
      * loops — the service itself throws on resume past the cap). Absent →
@@ -147,7 +145,7 @@ export interface Config {
 export declare const PERSONA_INTERPOLATION_HAZARD: RegExp;
 /**
  * Screen ONE dynamic string before it is embedded into dsh system-prompt
- * section/context text (plan QC fix wave W-1): break every COMPLETE
+ * section/context text (): break every COMPLETE
  * `{{...}}` group (the renderer's STRICT `interpolate` throws on any `{{`
  * paired with a later `}}` — unknown variable, malformed group, undefined
  * value), while leaving a LONE `{{` without a later `}}` verbatim (upstream
@@ -169,7 +167,7 @@ export declare function formatViolation(violation: ValidationResult): string;
 export declare function asRecord(value: unknown): Record<string, unknown> | undefined;
 /**
  * Cap on the plan / lease rows joined into the `<mstar_engine_status>`
- * catalog state lines (plan `20260830-dsh-catalog-cap` D1): ONE catalog-owned
+ * catalog state lines : ONE catalog-owned
  * constant shared by the `plans:` and `leases:` joins so an oversized
  * workflow snapshot cannot balloon the single-line catalog state section.
  * Numeric precedent: `DIGEST_PLAN_CAP` in `system-prompt.ts` (digest-side,
@@ -188,7 +186,7 @@ export declare const CATALOG_STATE_JOIN_LIMIT = 8;
  * (`length === 0` → `none` / `none registered` / `none active`) — this
  * helper is never reached for empty arrays.
  *
- * Hoisted from `system-prompt.ts` (plan `20260830-dsh-catalog-cap` D3) so
+ * Hoisted from `system-prompt.ts`  so
  * the GLOBAL digest and the catalog state lines share ONE join-capping
  * implementation; `_shared.ts` imports no gates-local module, so no import
  * cycle is introduced.
@@ -240,8 +238,7 @@ export declare function packagedSkillsDir(): string | undefined;
 /**
  * Resolve the plugin package's own `harness-agents/` mirror (synced from the
  * repo root by `bundle-assets` at build time; gitignored) — the
- * zero-config role-persona default source (plan
- * `20260815-dsh-fallbacks-personas` Task 3). Same dual-depth probe semantics
+ * zero-config role-persona default source. Same dual-depth probe semantics
  * as {@link resolvePackagedSkillsDir}: `'../harness-agents'` (dist layout
  * candidate) then `'../../harness-agents'` (source-layout candidate);
  * `src/harness-agents` is non-canonical and skipped shallow-first.

package/dist/gates/adapter.d.ts

@@ -17,7 +17,7 @@ export interface DshHostAdapterOptions {
     readonly config: Config;
     /**
      * The apply-scoped agent-flow pairing store (plan
-     * `20260811-panel-f4-timeliness` Task 1 — created by the entry `apply`,
+     *   Task 1 — created by the entry `apply`,
      * shared with the settle listener): passed to `recordDispatch` so an
      * exec-bound dispatch registers `callId → dispatchRef` for the later
      * post-execute settle pairing. Absent (host-adapter tests / direct
@@ -25,8 +25,7 @@ export interface DshHostAdapterOptions {
      */
     readonly pairing?: AgentFlowPairing;
     /**
-     * The P-c first-seen ask cache (plan `20260815-dsh-workflow-gate`
-     * Task 2): workflow name → resolved decision, apply-scoped. Absent (the
+     * The P-c first-seen ask cache (plan  workflow name → resolved decision, apply-scoped. Absent (the
      * entry relies on this default — `index.ts` constructs the adapter
      * without it) → the constructor builds ONE cache per adapter per apply,
      * shared by the gate and any answerer integration via the readonly
@@ -80,8 +79,7 @@ export declare class DshHostAdapter extends Service implements HostAdapter {
     private readonly config;
     private readonly pairing;
     /**
-     * The P-c first-seen ask cache (plan `20260815-dsh-workflow-gate`
-     * Task 2) — apply-scoped with the adapter: the dispatch gate reads it
+     * The P-c first-seen ask cache (apply-scoped with the adapter: the dispatch gate reads it
      * through `gateDispatch`, and tests/answerer integrations reach the same
      * instance via `ctx.dshHostAdapter.workflowAskCache`. Dies with the
      * fiber (no module-level reference — an HMR reload starts a fresh cache).
@@ -121,15 +119,14 @@ export declare class DshHostAdapter extends Service implements HostAdapter {
      * context and covers the field/branch/anti-recursion/worktree path.
      * @param prompt - the Assignment text (engine header grammar).
      * @param exec - the in-flight delegation tool call (listener path only).
-     * @param hard - the caller's ONE `resolveDispatchHard` resolution (qc1
-     * F-002 / qc2 F-3 / qc3 F-002 fix-wave): passed in so the record block and
+     * @param hard - the caller's ONE `resolveDispatchHard` resolution): passed in so the record block and
      * the caller's enforcement decision share a single compass resolution;
      * when omitted (external callers) the adapter resolves it itself.
      */
     dispatchGate(prompt: string, exec?: ToolExecution, hard?: boolean): GateResult;
     /**
      * Record one workflow/ralph gate verdict row (plan
-     * `20260815-dsh-workflow-gate` Task 4 — the durable ledger row for every
+     *   Task 4 — the durable ledger row for every
      * gated workflow/ralph call: verdict + metaName/objective + mode, via the
      * ledger plan's record path). `gateWorkflow` routes the record through
      * this adapter method so dispatch.ts stays free of a runtime agent-flow
@@ -171,7 +168,7 @@ export declare class DshHostAdapter extends Service implements HostAdapter {
     beforeDispatch(assignment: AssignmentFields | string): Promise<GateResult>;
     /**
      * `HostAdapter.beforeMerge` — reserve/validate the integration merge
-     * lease. v3 relocation (plan `20260819-workflow-dsh-viz` Task 3): the
+     * lease. v3 relocation : the
      * `integration_merge_lease` home is the ACTIVE workflow snapshot
      * (`workflows/<id>/snapshot.json` top-level — the v1 root-metadata home
      * is gone), so the hook READS the snapshot's current lease and validates

package/dist/gates/agent-flow.d.ts

@@ -8,7 +8,7 @@ export declare const AGENT_FLOW_MAX_EVENTS = 500;
 /** Default read limit (the catalog passes 50 per spec §2.2). */
 export declare const AGENT_FLOW_DEFAULT_LIMIT = 50;
 /**
- * The append size gate (qc2 F-1 / qc3 F-001/003 — fix-wave): the truncation
+ * The append size gate: the truncation
  * read-modify-write runs only when the file exceeds ~500 lines' typical
  * size (conservative ≈ 500 × 128 B average line); smaller files stay
  * append-only. The bound is therefore approximate ("~500 events") — a file
@@ -18,7 +18,7 @@ export declare const AGENT_FLOW_DEFAULT_LIMIT = 50;
  */
 export declare const AGENT_FLOW_SIZE_GATE_BYTES: number;
 /**
- * WORKFLOW field length caps (qc2 W-3 fix-wave) — ONE constant family at
+ * WORKFLOW field length caps  — ONE constant family at
  * the ledger boundary, enforced on BOTH the consumer (workflow-ledger
  * `rowOf`) and the read narrow (`eventFromUnknown`): a hostile or
  * model-controlled multi-MB string must never defeat the
@@ -43,8 +43,7 @@ export declare const WORKFLOW_LEDGER_MAX_SEQ: number;
  * through unchanged; longer values are truncated to `cap − marker` chars
  * plus the {@link WORKFLOW_LEDGER_TRUNCATION_MARKER} suffix (the marker
  * guarantees the truncation is visible in the panel — never a silent cut).
- * CODE-POINT gated AND sliced (plan QC fix wave — qc2 S-5; PR #97 finding
- * 2): `String.prototype.slice` operates on UTF-16 code units and can split
+ * CODE-POINT gated AND sliced : `String.prototype.slice` operates on UTF-16 code units and can split
  * a surrogate pair at the cap boundary (a lone surrogate renders as U+FFFD
  * in the log line), and a UTF-16 `.length` gate would false-positive
  * truncate astral-dense values (≤ cap code points but > cap UTF-16 units)
@@ -62,21 +61,19 @@ export declare const AGENT_FLOW_LOGGER = "mstar/agent-flow";
  * waterfall. VERIFIED to be dispatched by the real registry for every tool
  * call (`runPostExecute` → `postExecute`, upstream source; pinned by the
  * real-call probe in `tests/agent-flow.spec.ts`), so settles are no longer
- * host-emission-dependent (plan `20260811-panel-f4-timeliness` Task 1 — the
+ * host-emission-dependent (the
  * old "not part of the verified surface" assumption is obsolete).
  */
 export declare const SETTLE_SEAM = "tools/post-execute";
 /**
- * The once-per-apply settle-pairing trace (plan `20260811-panel-f4-timeliness`
- * Task 1). Historical name `SETTLE_SEAM_UNAVAILABLE_NOTE` (qc1 F-105 / qc2
- * N-002 fix-wave): the old name claimed the seam was UNAVAILABLE, which the
+ * The once-per-apply settle-pairing trace . Historical name `SETTLE_SEAM_UNAVAILABLE_NOTE`: the old name claimed the seam was UNAVAILABLE, which the
  * message itself refutes — the seam IS a verified part of the registry
  * surface, so the constant was renamed to the accurate `PAIRING` name. The
  * message states the VERIFIED pairing facts: the seam is emitted by the
  * registry; foreground dispatch calls settle via it, background subagents
  * settle via `ctx.jobs.onJobDone` pairing; only unpaired payloads stay
  * dispatch-only (never fabricated settlement). Logged ONCE per logger binding
- * (≈ once per apply — the same module-level flag, qc1 F-006) when the pairing
+ * (≈ once per apply — the same module-level flag) when the pairing
  * listener is registered.
  */
 export declare const SETTLE_SEAM_PAIRING_NOTE = "settle seam \"tools/post-execute\" IS part of the verified dsh-tools registry surface (runPostExecute dispatches it for every tool call) \u2014 foreground dispatch calls settle here, background subagents settle via ctx.jobs.onJobDone pairing; only UNPAIRED payloads (non-dispatch tools, calls outside the apply-scoped pairing window) stay dispatch-only \u2014 never a fabricated settle";
@@ -87,8 +84,7 @@ export type SettleOutcome = 'ok' | 'error' | 'denied';
 /** Workflow run terminal reason (`tool-workflow` vocabulary — `workflow/src/types.ts:63`). */
 export type WorkflowStopReason = 'completed' | 'cancelled' | 'error';
 /**
- * Workflow/ralph gate verdict vocabulary (plan `20260815-dsh-workflow-gate`
- * Task 4): the RESOLVED outcomes reuse the dispatch verdict vocabulary
+ * Workflow/ralph gate verdict vocabulary : the RESOLVED outcomes reuse the dispatch verdict vocabulary
  * (`ok`/`advisory`/`denied` — the plan interface "the workflow verdict
  * vocabulary"); `ask` is the PENDING-decision member — the first-seen ask
  * itself is a gated call, so its row carries `ask` until the approval
@@ -97,15 +93,15 @@ export type WorkflowStopReason = 'completed' | 'cancelled' | 'error';
 export type WorkflowVerdict = DispatchVerdict | 'ask';
 /**
  * The workflow/ralph gate mode (Config `workflowGate` — plan
- * `20260815-dsh-workflow-gate` Task 1), recorded on every verdict row.
+ * verdict rows), recorded on every verdict row.
  * `off` rows never exist: the gate short-circuits `off` BEFORE the policy,
  * so no verdict is produced.
  */
 export type WorkflowGateMode = 'off' | 'warn' | 'ask' | 'hard';
 /**
- * One v1 workflow ledger event (plan `20260815-dsh-workflow-ledger` Task 2 —
+ * One v1 workflow ledger event (the JSONL row —
  * the W-B2 schema). Produced from the durable `tool-workflow/*` session events
- * by the Task 3 consumer (`run-start` → `workflow-run`, `agent-start` →
+ * by the session-event consumer (`run-start` → `workflow-run`, `agent-start` →
  * `workflow-agent`, `run-end` → `workflow-run-end`; the upstream `agent-end`
  * member outcome has no ledger kind). Optional fields (`agent` / `phase`) are
  * OMITTED from the serialized line when absent (lossless-JSON discipline).
@@ -144,8 +140,8 @@ export type AgentFlowWorkflowEvent = {
     stopReason: WorkflowStopReason;
 };
 /**
- * One v1 ledger event (spec §2.1.3 + plan `20260815-dsh-workflow-ledger`
- * Task 2 — the JSONL line). Optional fields are OMITTED from the serialized
+ * One v1 ledger event (spec §2.1.3 +
+ * the JSONL line). Optional fields are OMITTED from the serialized
  * line when absent (Session.append's lossless JSON discipline starts at the
  * record boundary). The three `workflow-*` kinds are the W-B2 addition —
  * see {@link AgentFlowWorkflowEvent}.
@@ -177,8 +173,7 @@ export type AgentFlowEvent = {
     outcome: SettleOutcome;
     durationMs?: number;
     /**
-     * The PAIRED dispatch's identity (plan `20260811-panel-f4-timeliness`
-     * Task 1) — same field names + semantics as the dispatch event:
+     * The PAIRED dispatch's identity (plan  same field names + semantics as the dispatch event:
      * `role` is the Assignment `Execute as` ('' when missing), `planId` /
      * `taskId` the plan + `Task N` tags. Written for every paired settle;
      * ABSENT on unpaired (legacy) settles — the client pairs on identity
@@ -233,7 +228,7 @@ export interface AgentFlowDispatchRef {
     taskId?: string;
 }
 /**
- * The apply-scoped pairing store (plan `20260811-panel-f4-timeliness` Task 1,
+ * The apply-scoped pairing store (
  * decision D1 — created in the entry `apply`, same lifetime as the catalog
  * cache; an HMR restart resets it, and completions outside the window stay
  * unpaired → no settle, the documented honest degrade). Maps are keyed by
@@ -245,7 +240,7 @@ export interface AgentFlowPairing {
     /**
      * The agent-namespaced call key → the dispatch it recorded (populated by
      * `recordDispatch` when an exec is present). Key = `${sessionId}\u0000${callId}`
-     * (qc1 F-101 fix-wave): a raw `ToolExecution.callId` is NOT globally unique
+     * : a raw `ToolExecution.callId` is NOT globally unique
      * in one process — dsh runs many sessions concurrently and upstream mints
      * per-message ids (`call-${index}`), so the dispatching session id must
      * namespace the key or session B's same-id call could overwrite session A's
@@ -259,19 +254,18 @@ export interface AgentFlowPairing {
 /** Module-scoped log sink (bound to `mstar/agent-flow` by the entry at apply). */
 type AgentFlowLogSink = (level: 'info' | 'warn' | 'error', message: string) => void;
 /**
- * Module-scoped catalog-invalidation hook (plan `20260811-panel-f4-timeliness`
- * Task 1 — the `invalidateCatalog` 挂钩 that Task 2 consumes): called with
+ * Module-scoped catalog-invalidation hook : called with
  * the affected `{HARNESS_DIR}` after every SUCCESSFUL ledger record
  * (`recordDispatch` / `recordSettle`). The entry binds the real invalidation
- * closure at apply (Task 2 shipped the apply-scoped harnessDir → cache-key
+ * closure at apply (the apply-scoped harnessDir → cache-key
  * reverse-map closure in `index.ts` — see `createCatalogInvalidation`);
  * unbound → no-op. Never throws into the record path.
  */
 type AgentFlowInvalidator = (harnessDir: string) => void;
 /**
  * Bind the module's catalog-invalidation hook (plan
- * `20260811-panel-f4-timeliness` Task 1 — same pattern as
- * {@link setAgentFlowLogger}; the entry binds at apply; Task 2 shipped the
+ * the settle-pairing upgrade — same pattern as
+ * {@link setAgentFlowLogger}; the entry binds at apply; the apply-scoped
  * real binding — the apply-scoped harnessDir → cache-key reverse-map
  * closure in `index.ts`).
  * @param invalidate - the hook (`undefined` clears the binding).
@@ -293,10 +287,10 @@ export declare function setAgentFlowLogger(sink: AgentFlowLogSink | undefined):
  * (spec §2.1.1 — `taskIdOf`). The engine `assignmentHeaderRegion` boundary is
  * reused: only text AFTER the header region is scanned, so a `## Task N`
  * example quoted in the header never resolves a task id. Only a LEVEL-2
- * heading (`^## Task N`) matches (qc2 F-8: an example or sub-heading at
+ * heading (`^## Task N`) matches (an example or sub-heading at
  * another depth before the real task must not resolve — lower false-hit
  * surface); normalized to `T<n>` (matches the panel render `planId#taskId`,
- * e.g. `20260810-x#T2`).
+ * e.g.  #T2`).
  * @param prompt - the full Assignment text.
  */
 export declare function taskIdOf(prompt: string): string | undefined;
@@ -308,7 +302,7 @@ export declare function taskIdOf(prompt: string): string | undefined;
  * `workflows[]` MEMBERSHIP — non-terminal lifecycles (`running` AND
  * `paused`; terminal lifecycles are removed at terminal) — so a paused
  * lifecycle stays a valid append target (explicit decision, plan
- * `20260819-workflow-dsh-viz` Task 2).
+ * the workflow viz plan).
  *
  * No active entry → `null`: the record is SKIPPED with a one-time warn
  * (per sink binding) — never a silent write into the root v1 file, never a
@@ -320,7 +314,7 @@ export declare function taskIdOf(prompt: string): string | undefined;
  */
 export declare function resolveAgentFlowWriteDir(harnessDir: string): string | null;
 /**
- * Lock-directory name for the per-workflow write lock (qc3 W-1 fix-wave):
+ * Lock-directory name for the per-workflow write lock :
  * guards the ledger append + size-gated truncating read-modify-write AND
  * the workflow-ledger cursor sidecar read-modify-write against concurrent
  * dsh processes sharing one active lifecycle (compass ruling 3). The
@@ -330,8 +324,7 @@ export declare function resolveAgentFlowWriteDir(harnessDir: string): string | n
  */
 export declare const WORKFLOW_LEDGER_LOCKDIR = ".ledger-write.lockdir";
 /**
- * Run `fn` under the per-workflow inter-process write lock (qc3 W-1
- * fix-wave): atomic `mkdir` on `<workflowDir>/.ledger-write.lockdir/`
+ * Run `fn` under the per-workflow inter-process write lock: atomic `mkdir` on `<workflowDir>/.ledger-write.lockdir/`
  * acquires (success acquires; existing dir → another writer holds the
  * lock); while another writer holds it, wait up to
  * {@link WORKFLOW_LOCKER_TIMEOUT_MS} and then THROW (Blocked — the
@@ -375,21 +368,21 @@ export declare function withWorkflowDirLock<T>(workflowDir: string, fn: () => T,
  * identity derivation (role / planId / taskId / taskCategory) reuse the gate's
  * own parsers — one grammar.
  *
- * Pairing (plan `20260811-panel-f4-timeliness` Task 1): when the input
+ * Pairing: when the input
  * carries an `exec` AND the apply-scoped `pairing` store, the successful
  * record registers the agent-namespaced key `${sessionId}\u0000${callId}` →
  * dispatchRef (the full dispatch identity), so a later
  * `tools/post-execute` for the same call can settle with the SAME identity
- * (qc1 F-101 fix-wave: the session id namespaces the key — a raw callId is
+ * (the session id namespaces the key — a raw callId is
  * not globally unique across sessions in one process). The pairing registers
  * only after the ledger append SUCCEEDED — a failed record never pairs to a
  * phantom dispatch. An exec-less record (host-hook path) has no callId → no
- * pairing. The pairing sub-path has its OWN catch scope (qc1 F-106 / qc2
- * N-001 / qc3 F-006 fix-wave): a `Map.set` throw must not log "record
+ * pairing. The pairing sub-path has its OWN catch scope: a `Map.set` throw must not log "record
  * failed" after the dispatch was already appended.
- * @param input - harness dir + exec (agent id) + Assignment text + the gate's
- * violations + the hard-enforcement resolution + the apply-scoped pairing
- * store (the adapter passes its own; direct callers may omit it).
+ * @param input - the harness dir; the dispatching exec's agent id; the
+ * Assignment text; the gate's violations; the hard-enforcement resolution;
+ * the apply-scoped pairing store (the adapter passes its own; direct callers
+ * may omit it).
  */
 export declare function recordDispatch(input: {
     harnessDir: string;
@@ -425,9 +418,9 @@ export declare function recordSettle(input: {
     taskId?: string;
 }): void;
 /**
- * Record one workflow ledger event (plan `20260815-dsh-workflow-ledger` Task 2
+ * Record one workflow ledger event (the JSONL schema below
  * — the W-B2 schema). Fully try/catch-contained — NEVER throws into the
- * session-event consumer (Task 3 wires it); a failing record logs only
+ * session-event consumer wires it); a failing record logs only
  * (`mstar/agent-flow`), so a ledger write never crashes or alters a workflow
  * run (Global Constraint: observe-only events are never refusal channels).
  * The event is serialized lossless — optional fields (`agent` / `phase`) are
@@ -447,7 +440,7 @@ export declare function recordSettle(input: {
  * @returns `true` when the row was appended (the caller may durably advance
  *   its watermark); `false` on a contained append failure OR when no active
  *   lifecycle resolves — the caller must leave the cursor behind so the row
- *   is re-attempted at the next scan (qc3 R-401: advance-then-record made a
+ *   is re-attempted at the next scan (advance-then-record made a
  *   failed append permanent loss).
  */
 export declare function recordWorkflowEvent(input: {
@@ -457,7 +450,7 @@ export declare function recordWorkflowEvent(input: {
 }): boolean;
 /**
  * Input for {@link recordWorkflowVerdict} — one gated workflow/ralph call's
- * decision identity (plan `20260815-dsh-workflow-gate` Task 4: verdict +
+ * decision identity (verdict +
  * metaName/objective + mode).
  */
 export interface WorkflowVerdictInput {
@@ -479,9 +472,7 @@ export interface WorkflowVerdictInput {
     code?: string;
 }
 /**
- * Record one workflow/ralph gate verdict row (plan `20260815-dsh-workflow-gate`
- * Task 4 — "one ledger row per gated workflow/ralph call" via the ledger
- * plan's record path, the `workflow-verdict` kind). Fully
+ * Record one workflow/ralph gate verdict row . Fully
  * try/catch-contained — NEVER throws into the gate (`gateWorkflow` calls
  * this on EVERY policy decision); a failing record logs only
  * (`mstar/agent-flow`), so a ledger write never crashes or alters a
@@ -490,7 +481,7 @@ export interface WorkflowVerdictInput {
  * display identity fields (`workflow` / `objective`) are capped at the
  * ledger boundary (same discipline as the W-B2 name cap) and the ralph
  * `objective` is routed through the SHARED `normalizeWorkflowName` strip at
- * this write boundary (qc2 W-2 — control-char discipline parity with the
+ * this write boundary (— control-char discipline parity with the
  * name/label/phase fields; the gate already normalizes `workflow`). The
  * JSONL line is line-safe either way (`JSON.stringify` escapes), but the
  * panel view passes the objective through raw — a hostile objective
@@ -500,8 +491,8 @@ export interface WorkflowVerdictInput {
  */
 export declare function recordWorkflowVerdict(input: WorkflowVerdictInput): void;
 /**
- * Read the agent-flow ledger as the catalog view (spec §2.1.3 — fix-wave
- * qc1 F-001 / qc2 F-6): the latest events first (bounded by `limit`) plus
+ * Read the agent-flow ledger as the catalog view (spec §2.1.3): the latest
+ * events first (bounded by `limit`) plus
  * the role × outcome summary over the SAME window (so `by role` counts sum
  * to the event count). A MISSING ledger file returns the EMPTY view
  * `{ events: [], summary: [] }` — recording hasn't started (it begins at
@@ -515,7 +506,7 @@ export declare function recordWorkflowVerdict(input: WorkflowVerdictInput): void
  * (the catalog passes `join(harnessDir, selection.dir)`; the writer appends
  * there via `resolveAgentFlowWriteDir`).
  *
- * Large-file reads (plan `20260820-dsh-ledger-tail-read`): ledgers above
+ * Large-file reads : ledgers above
  * `AGENT_FLOW_TAIL_READ_THRESHOLD_BYTES` are read as a bounded latest-first
  * tail — seek from EOF, aligned to a line boundary, doubling backward until
  * the window holds `limit` complete lines — so the catalog pays O(window) at
@@ -528,30 +519,29 @@ export declare function recordWorkflowVerdict(input: WorkflowVerdictInput): void
  */
 export declare function readAgentFlow(workflowDir: string, limit?: number): AgentFlowView | null;
 /**
- * The `tools/post-execute` settle pairing (plan `20260811-panel-f4-timeliness`
- * Task 1 — replaces the old defensive payload probing): the VERIFIED
+ * The `tools/post-execute` settle pairing : the VERIFIED
  * dsh-tools registry dispatches this seam for every tool call
  * (`runPostExecute` → `postExecute`, upstream source), so the listener only
  * decides whether a completion signal exists for the PAIRED dispatch:
  *
  * - non-dispatch tool (`exec.name` ∉ Config `dispatchTools`) → nothing;
  * - dispatch tool whose agent-namespaced call key
- *   (`${sessionId}\u0000${callId}`, qc1 F-101 fix-wave) is not in the pairing
+ *   (the exact call identity) is not in the pairing
  *   store (HMR reset, host-hook dispatch, non-gate path) → nothing (warned
  *   once per registration — honest degrade, never fabricated settlement);
  * - `result.isError === true` OR an `error` payload present → settle `error`
- *   immediately (fabrication guard, qc2 F-001 / qc3 F-003a — the dispatch
+ *   immediately (fabrication guard — the dispatch
  *   call failed; a result carrying `error` without `isError` never settles ok);
  * - successful `result.value` shape `{ kind: 'background', taskId }` with a
  *   valid taskId → store `taskId → dispatchRef` (the real settle arrives via
  *   `ctx.jobs.onJobDone`); `{ kind: 'background' }` WITHOUT a valid taskId
- *   → nothing mappable (no settle, qc3 F-003b);
+ *   → nothing mappable (no settle);
  * - `{ kind: 'continuable', subagentId }` → no terminal signal this round →
  *   no settle (documented limit — the child owns its turns);
  * - any other successful value (foreground `{ kind: 'foreground', … }`
  *   included) → settle `ok` (the call completed synchronously).
  * The consumed `dispatchByCallId` entry is DELETED after the branch resolves
- * the call (map pruning, qc1 F-102 / qc2 F-002 / qc3 F-002 — each callId
+ * the call (map pruning — each callId
  * pairs exactly once; the map holds only in-flight calls).
  *
  * The waterfall MUST be delegated via `next()` on every path — returning
@@ -569,7 +559,7 @@ export declare function readAgentFlow(workflowDir: string, limit?: number): Agen
 export declare function registerSettleListener(ctx: Context, config: Config, pairing: AgentFlowPairing): void;
 /**
  * The structural read of the dsh-jobs terminal snapshot the pairing consumes
- * (plan `20260811-panel-f4-timeliness` Task 1). The `ctx.jobs.onJobDone`
+ * (the settle-pairing upgrade). The `ctx.jobs.onJobDone`
  * contract was verified against the upstream `@deepseek-ai/dsh-jobs`
  * `types.ts`: `JobDoneListener = (snapshot, owner) => …`, terminal
  * `snapshot.status` ∈ `completed | killed | failed`, `startedAt`/`finishedAt`
@@ -589,14 +579,14 @@ export interface TaskDoneSnapshot {
 }
 /**
  * Record the settle for one background-task terminal (plan
- * `20260811-panel-f4-timeliness` Task 1 — the `ctx.jobs.onJobDone` path):
+ * the `ctx.jobs.onJobDone` path):
  * the snapshot's task id must hit the pairing store's `dispatchByTaskId`
  * (populated by the post-execute background branch) — a miss records NOTHING
  * (honest degrade, never fabricated). Outcome mapping: `completed → ok` /
  * `killed → denied` / `failed → error`; `durationMs = finishedAt − startedAt`
  * when both are present. After a SUCCESSFUL settle the consumed
- * `dispatchByTaskId` entry is deleted (map pruning, qc1 F-102 / qc2 F-002 /
- * qc3 F-002 — the map holds only in-flight tasks; a contract-violating
+ * `dispatchByTaskId` entry is deleted (map pruning — the map holds only
+ * in-flight tasks; a contract-violating
  * non-terminal snapshot records nothing and KEEPS the entry so a later real
  * terminal can still settle). Fully contained — never throws into the task
  * registry's listener notification.

package/dist/gates/agent-personas.d.ts

@@ -35,8 +35,7 @@ export declare function personaFor(roleId: string, lookup: PersonaLookup, warn?:
  * The mstar role-id set for one mirror: the file stems of the shells
  * eligible as subagent role defaults (`mode` absent-or-`subagent` — a
  * `primary` shell like `project-manager` is excluded), sorted for
- * deterministic warn listings. The adoption advisory (plan
- * `20260815-dsh-fallbacks-personas` Task 4) derives its taxonomy reference
+ * deterministic warn listings. The adoption advisory derives its taxonomy reference
  * from here — never hardcoded. Reads the mirror directory + each shell's
  * frontmatter once per call (the advisory invokes it once per apply — no
  * cache needed). Returns `[]` for an unreadable/absent mirror directory.

package/dist/gates/catalog.d.ts

@@ -14,7 +14,7 @@ export interface CatalogCacheEntry {
 }
 /**
  * The apply-scoped `harnessDir → cache key` reverse map + invalidation
- * closure (plan `20260811-panel-f4-timeliness` Task 2, decision D3): the
+ * closure : the
  * catalog cache is keyed by {@link EXPLICIT_CACHE_KEY} or the session cwd,
  * while ledger records (dispatch/settle) identify the affected workspace by
  * `{HARNESS_DIR}` — the reverse map bridges the two so a ledger change
@@ -96,10 +96,7 @@ export declare function buildCatalogSources(ctx: Context, harnessDir: string | n
  * workspace root and TTL-refreshed — Config `catalogTtlMs`).
  * @param ttlMs - catalog refresh interval in milliseconds.
  * @param register - the apply-scoped `harnessDir → cache key` reverse-map
- * registration (plan `20260811-panel-f4-timeliness` Task 2 — keeps every
- * workspace's entry invalidatable by a ledger change; see
- * `createCatalogInvalidation`).
- * @param digests - per agent+workspace turn digests (last rendered text)
+ * registration. * @param digests - per agent+workspace turn digests (last rendered text)
  * for the digest-gated re-emission.
  * @param payload - the proposed step the loop is about to enter.
  * @param next - the remaining pre-step chain; its value is the delegated decision.