@mstar-harness/dsh 3.6.3 → 3.7.0

package/dist/gates/dispatch.d.ts

@@ -11,14 +11,13 @@ export declare const DISPATCH_LOGGER = "mstar/dispatch-gate";
  * default id + its fork sibling — roadmap §9 W-B1: fork dispatches carry the
  * same Assignment-shaped `{ description, prompt }` args and must be gated
  * like `subagent`). Exported SHARED with the agent-flow settle pairing
- * (`registerSettleListener` matches the same tool set — plan
- * `20260811-panel-f4-timeliness` Task 1) so the default cannot drift between
+ * (`registerSettleListener` matches the same tool set) so the default cannot drift between
  * the gate and the settle seam.
  */
 export declare const DEFAULT_DISPATCH_TOOLS: readonly ["subagent", "subagent_fork"];
 /**
  * The fixed workflow/ralph tool names the workflow gate matches (plan
- * `20260815-dsh-workflow-gate` — architect-verified): the workflow tool
+ *   — architect-verified): the workflow tool
  * registers under Config-default name `'workflow'` and is RENAMEABLE per
  * instance (`toolName`, `tool-workflow/src/index.ts:41`); `ralph` is a
  * fixed name (`tool-ralph/src/index.ts:413`). A renamed instance is out
@@ -51,7 +50,7 @@ export interface DispatchGateAdvisory {
  * stay silent — no false-positive warnings. Callers MUST pass the engine
  * `assignmentHeaderRegion` slice: a `## Assignment` heading or
  * field line quoted in the task body must not shape a non-assignment prompt.
- * Exported for the agent-flow ledger's shape guard (qc2 F-2 — the shared
+ * Exported for the agent-flow ledger's shape guard — the shared
  * `DshHostAdapter.dispatchGate` core applies the SAME guard on both dispatch
  * surfaces, so the exec-less host-hook path records nothing for
  * non-Assignment text either).
@@ -65,7 +64,7 @@ export declare function isAssignmentShaped(assignmentText: string): boolean;
  * frontmatter, else warn-only.
  */
 export declare function resolveDispatchHard(harnessDir: string | null, config: Config, assignmentText: string): boolean;
-/** A header value that means "no value" (placeholder conventions). Type guard so callers narrow to `string`. Shared with the agent-flow ledger (qc1 F-003 — one grammar, no copy-paste drift). */
+/** A header value that means "no value" (placeholder conventions). Type guard so callers narrow to `string`. Shared with the agent-flow ledger  (one grammar, no copy-paste drift). */
 export declare function isNaValue(value: string | undefined): value is undefined;
 /**
  * Resolve the target plan id from the Assignment HEADER region: `Plan Path`
@@ -95,7 +94,7 @@ export declare function sessionIdOf(exec: ToolExecution): string | undefined;
  * whose plan row is `InProgress`.
  *
  * Contract (status-and-residuals.md § Pre-dispatch re-verify; v3
- * relocation — plan `20260819-workflow-dsh-viz` Task 3): before any
+ * relocation —): before any
  * writable implement dispatch, reread the ACTIVE workflow snapshot
  * (`workflows/<id>/snapshot.json` — the v1 root `plans[]` home is gone; the
  * root v2 `status.json` supplies the active `workflows[]`) and confirm
@@ -150,8 +149,7 @@ export declare function dispatchGateCore(config: Config, harnessDir: string | nu
 };
 /**
  * The workflow-gate input composed from one `workflow`/`ralph` tool call
- * (plan `20260815-dsh-workflow-gate` Task 1 — consumed by the Task 2 P-a /
- * P-c and Task 3 P-b policies): the tool name + the structural reads of
+ * : the tool name + the structural reads of
  * `meta` (workflow) / `objective` (ralph) + the in-flight call.
  */
 export interface WorkflowGateInput {
@@ -164,7 +162,7 @@ export interface WorkflowGateInput {
     /** The in-flight tool call — Task 3 P-b lease attribution reads the calling agent/session off it. */
     exec: ToolExecution;
     /**
-     * P-b lease attribution (plan Task 3): the calling workspace's first
+     * P-b lease attribution: the calling workspace's first
      * `InProgress` plan lacking `execution_lease` coverage (computed by
      * {@link writableFanOutUncovered} from the status.json read through the
      * contained resolver path — `preExecuteListener` already resolved the
@@ -177,7 +175,7 @@ export interface WorkflowGateInput {
 /**
  * Compose the {@link WorkflowGateInput} from one workflow/ralph tool call's
  * arguments — structural reads, NEVER throws (plan
- * `20260815-dsh-workflow-gate` Task 1; args shapes architect-verified:
+ *   Task 1; args shapes architect-verified:
  * workflow `{ script, meta: { name, description, whenToUse?, phases? },
  * args? }` (`tool-workflow/src/index.ts:152-161`); ralph
  * `{ objective, maxRounds?, maxHandoffChars? }`
@@ -187,7 +185,7 @@ export interface WorkflowGateInput {
  *
  * `meta.name` is NORMALIZED through {@link normalizeWorkflowName} (control
  * chars stripped) BEFORE the empty check — the P-c cache-key congruence
- * fold-in (plan Task 5): the run-start observation (workflow-ledger.ts)
+ * fold-in: the run-start observation (workflow-ledger.ts)
  * keys the ask cache with the SAME normalized name, so a control-char name
  * (`au\u0000dit`) asks once and observes under one key instead of re-asking
  * forever. The length is NEVER capped here (the gate's identity axis is

package/dist/gates/fallbacks-advisory.d.ts

@@ -1,7 +1,6 @@
 /**
  * Warn-only adoption advisory for the OPTIONAL `dsh-llm-fallbacks` plugin
- * (plan `20260815-dsh-fallbacks-personas` Task 4 + `20260816-dsh-b4-seeds`
- * Task 3): when the capability is mounted, ONE advisory pass per apply
+ * (plan   Task 4 +  when the capability is mounted, ONE advisory pass per apply
  * reports the deployment's fallbacks taxonomy state (bounded: ≤1 warn per
  * category, logger `mstar/fallbacks-advisory`):
  *
@@ -54,7 +53,7 @@ export declare function setAdvisoryLogger(sink: AdvisoryLogSink): AdvisoryLogSin
 /**
  * Warn id-list cap: an id-list warn line lists at most this many ids before
  * the `… and K more` suffix — a huge registry (thousands of rows) must not
- * produce a multi-KB log line (plan QC fix wave S-cap). Exported for the
+ * produce a multi-KB log line (cap). Exported for the
  * suite's cap assertions; module surface only — the entry's frozen 47-name
  * export surface deliberately does not re-export it.
  */

package/dist/gates/fallbacks-probe.d.ts

@@ -1,6 +1,6 @@
 /**
  * Capability probes for the OPTIONAL `dsh-llm-fallbacks` plugin (plan
- * `20260814-dsh-fallbacks-integration` Task 1 — probe foundation).
+ *   Task 1 — probe foundation).
  *
  * The fallbacks plugin is an optional SEPARATE install (two-command
  * contract) and a dev-time-only dependency of this package: src carries
@@ -55,7 +55,7 @@ export declare function fallbacksService(ctx: Context): FallbacksServiceView | u
  * The fallbacks loader row when present and enabled (group rows skipped).
  * Unlike {@link fallbacksMounted}, NO live-fiber requirement: the entry is
  * declarative and `options.config` is set at entry creation, so the adoption
- * advisory (plan `20260815-dsh-fallbacks-personas` Task 4) can read the
+ * advisory  can read the
  * deployment's row config even during HMR/fiber-swap windows — the advisory
  * caller gates on `fallbacksMounted` first.
  */

package/dist/gates/fallbacks-seeds.d.ts

@@ -1,6 +1,6 @@
 /**
  * Zero-config seed declaration for the OPTIONAL `dsh-llm-fallbacks` plugin
- * (plan `20260816-dsh-b4-seeds` Task 2): when the `llm-fallbacks` service is
+ * : when the `llm-fallbacks` service is
  * applied, this module declares the 13 `mode: subagent` mstar roles into the
  * fallbacks seed registry — persona = mirror `description` (verbatim, the
  * SSOT stays `mstar-roles`) + one mandatory-load guide line.

package/dist/gates/fallbacks-structural.d.ts

@@ -1,6 +1,6 @@
 /**
  * Local structural mirrors of the consumed `dsh-llm-fallbacks` surface
- * (plan `20260831-dsh-alpha2-optional-fallbacks` Task 2). dsh natively
+ * . dsh natively
  * covers subagent customization, so the fallbacks
  * plugin is an OPTIONAL capability activated by the unchanged two-command
  * install contract — and a dev-time-only dependency of this package (type

package/dist/gates/goal-bridge.d.ts

@@ -4,7 +4,7 @@ import type { Config, HarnessResolver } from './_shared.ts';
 export declare const GOAL_BRIDGE_LOGGER = "mstar/goal-bridge";
 /**
  * Flat `maxGoalRounds` config fallback (architect decision — plan
- * `20260816-dsh-nb2-goal-bridge`): 256, aligned with the GoalService default
+ *  ): 256, aligned with the GoalService default
  * (`goal/src/index.ts:187`) and ralph `maxRounds` (`tool-ralph/src/index.ts:37`).
  */
 export declare const DEFAULT_MAX_GOAL_ROUNDS = 256;
@@ -46,8 +46,7 @@ export interface GoalView extends GoalRefView {
  * index.ts:244-257`); `complete` is a CAS by `{ id, revision }`
  * (`GOAL_STALE_REVISION` on stale). The drift path uses complete+create
  * (never `edit`) so each new iteration gets a FRESH goal with a clean
- * round budget (plan QC fix wave — qc2 W-1 / qc3 F-001/F-008).
- */
+ * round budget. */
 export interface GoalsServiceView {
     get(agent: unknown): GoalView | undefined;
     create(agent: unknown, request: {
@@ -74,8 +73,7 @@ export declare function iterationGoalObjective(iterationId: string): string;
  * `status` is `active` or `locked` — the directory name IS the iteration id
  * (plan-conventions `{ITERATION_DIR}/<id>/`). Completed/status-less/archived
  * compasses do not steer. Silent on any read failure (advisory degrade).
- * Shared with the planMode bridge via explicit no-barrel import (Task 4b —
- * the same "is an active iteration steering" read).
+ * Shared with the planMode bridge via explicit no-barrel import (the same "is an active iteration steering" read).
  * @param harnessDir - the resolved `{HARNESS_DIR}`.
  */
 export declare function steeringCompass(harnessDir: string): {
@@ -115,13 +113,12 @@ export declare function mirrorIterationGoal(agent: unknown, input: MirrorIterati
  * first root-like ancestor. `undefined` when unresolvable (fork lineage,
  * non-in-process provider, registry gap, or a cycle) — the decision point
  * then silently skips. Cycle guard: a `seen` set over visited session ids
- * (the upstream `liveLineage` guard — plan QC fix wave qc2 W-2 / qc3
- * F-003) breaks on ANY revisited id — a 1-hop self-loop, a 2+ hop cycle
+ * (the upstream `liveLineage` guard) breaks on ANY revisited id — a 1-hop self-loop, a 2+ hop cycle
  * (A→B→A), or a longer malformed lineage — instead of spinning forever on
  * the synchronous `subagent/start` decision-point listeners (reachable via
  * HMR remounts, resumed/forked sessions with stale headers, or a future
  * host change). Shared with the planMode bridge via explicit no-barrel
- * import (Task 4b — the same `subagent/start` decision-point root walk).
+ * import (the same `subagent/start` decision-point root walk).
  */
 export declare function rootAgentOf(agent: unknown, agents: AgentsView): unknown | undefined;
 /**
@@ -131,7 +128,7 @@ export declare function rootAgentOf(agent: unknown, agents: AgentsView): unknown
  * decision point — index.ts advisory slot), resolving the delegating ROOT
  * via the `parentSession` walk — the two mirror edges are idempotent (get +
  * compare when the mirror is in place — no churn) — plus a THIRD, advisory
- * listener on the `session/event` firehose (Task 3): a `goal/change`
+ * listener on the `session/event` firehose : a `goal/change`
  * envelope whose goal is blocked logs ONE warn (code + objective summary +
  * project-register residual pointer) with ZERO harness writes
  * (the one-way mirror; see {@link warnBlockedGoal}). The goals service is an

package/dist/gates/role-persona.d.ts

@@ -1,6 +1,5 @@
 /**
- * Native-first role-persona delivery (plan `20260831-dsh-alpha2-optional-fallbacks`
- * Task 3): a role-matched subagent start merges the persona into the request's
+ * Native-first role-persona delivery : a role-matched subagent start merges the persona into the request's
  * NATIVE `persona` slot (`@deepseek-ai/dsh-subagent`
  * `SubagentStartRequest.persona`) — the additive `mstar:role-persona`
  * system-prompt section is gone. Native semantics: the request persona
@@ -37,7 +36,7 @@
  * parsers the dispatch gate uses (`assignmentHeaderRegion` +
  * `parseAssignmentFields`) — over the start request's prompt text (the
  * `ContentBlock[]` the child receives as its first user message). Persona
- * lookup (plan `20260815-dsh-fallbacks-personas` Task 3) is the single
+ * lookup  is the single
  * {@link personaFor} surface — `Config.rolePersonas[executeAs]` →
  * `harness-agents/` mirror default → skip (never gated on `roleMap` or on
  * the fallbacks mounted state: persona delivery is fallbacks-independent).

package/dist/gates/skill-lint.d.ts

@@ -56,9 +56,21 @@ export declare class SkillLintVetoError extends Error {
  * CLI `mstar skill lint` combination plus the ephemeral-citation gate;
  * violation codes `lint.frontmatter.*` / `skill-authoring.five-question.*`
  * / `skill.ephemeral.*`). Pure: no enforcement, no I/O.
+ *
+ * Five-question profile (spec A4): the shared Engine classifier
+ * (`classifySkillLint`) selects the mode from `options.skillId` — the
+ * trusted resolved skill-target basename passed by the fs-intent path and
+ * `lintSkillWrite`. A doc-only call (no `skillId`) stays strict authoring —
+ * the greenfield default is never loosened by an unparented document. The
+ * frontmatter and ephemeral-citation checks run in every profile; `core`
+ * (exact `mstar-harness-core`) skips only the five-question check.
  * @param doc - the full SKILL.md text.
+ * @param options - `skillId`: the resolved skill-target directory basename
+ * (trusted boundary identity — never the doc's YAML `name` alone).
  */
-export declare function lintSkillDoc(doc: string): GateResult;
+export declare function lintSkillDoc(doc: string, options?: {
+    skillId?: string;
+}): GateResult;
 /**
  * Enforce the skill-authoring lints over a KNOWN document (the brief's
  * "incoming doc when available" branch): `Enforcement: hard` + violations →
@@ -68,8 +80,13 @@ export declare function lintSkillDoc(doc: string): GateResult;
  * needed on this branch. The content-blind listener path (where the
  * incoming doc is never visible) routes through {@link gateSkillIntent}
  * instead, which applies the status-gate repair-escape decision.
+ *
+ * The lint profile is classified from the trusted resolved skill-target
+ * basename (spec A4): `basename(dirname(resolve(options.target)))` — the
+ * write's own target, never the document's YAML `name`.
  * @param doc - the document about to be written (the write's content).
- * @param options - target display path (veto message) + resolved hard flag.
+ * @param options - target display path (veto message + profile identity) +
+ * resolved hard flag.
  */
 export declare function lintSkillWrite(doc: string, options: {
     target: string;

package/dist/gates/system-prompt.d.ts

@@ -1,11 +1,8 @@
 /**
- * Harness-rules system-prompt injection (plan `20260816-dsh-nb1-systemprompt`
- * Task 2): the root session's ONE `mstar:harness-rules` pointer section plus
- * the `mstar:engine-status` runtime-context summary, both registered on the
- * GLOBAL prompt layer — visible to the root session AND every dispatched
+ * Harness-rules system-prompt injection (visible to the root session AND every dispatched
  * child — on their own names and layers (the child persona rides the NATIVE
  * subagent persona channel since plan
- * `20260831-dsh-alpha2-optional-fallbacks` Task 3 — no child-scoped
+ *   Task 3 — no child-scoped
  * `mstar:role-persona` section exists anymore; duplicate-name throws remain
  * per name per layer, verified `scope/src/store.ts`).
  *
@@ -18,13 +15,13 @@
  *   interpolation and throws on unknown/malformed/undefined references
  *   (`interpolate` in `@deepseek-ai/dsh-system-prompt`), so every injected
  *   string must carry no complete group. The mechanism is LIVE, not static
- *   (plan QC fix wave W-1): every operator-controlled value embedded below
+ *   : every operator-controlled value embedded below
  *   (harness dir, plan ids, iteration id, lease fields, direction prose)
  *   is passed through `stripInterpolationHazard` — complete `{{…}}` groups
  *   are screened so a hostile value can never break prompt assembly, while
  *   a lone `{{` stays literal prose.
  * - The harness dir is resolved PER ASSEMBLY from the assembly context's
- *   agent (plan QC fix wave W-2 — the catalog pre-step precedent): the
+ *   agent : the
  *   session cwd of the agent whose prompt is being assembled, via
  *   `resolver.forAgent`, with the boot value (`forWorkspace(undefined)`,
  *   the explicit config or null) as the fallback when the assembly carries
@@ -39,13 +36,12 @@
  *   re-registration, in zero-config and explicit-config deployments alike.
  * - The context provider reuses the catalog's unified machine-summary
  *   source (`buildCatalogSources` — the SAME builder the engine-status
- *   pre-step catalog row uses) and projects the SLIM digest (plan
- *   `20260820-dsh-engine-status-slim` Task 2): the version watermark
+ *   pre-step catalog row uses) and projects the SLIM digest: the version watermark
  *   ALWAYS, plus ONE `workflow … | plans: …` line only when the active set
  *   selects a lifecycle (`state.selection.kind === 'active'`). Harness dir
  *   and enforcement live in `mstar:harness-rules`; residuals / leases /
  *   direction / iteration-gate detail stay exclusive to the pre-step row.
- *   v3 (plan `20260819-workflow-dsh-viz` Task 3): the
+ *   v3 : the
  *   digest reads ONLY the catalog row (`state` — itself aggregated from the
  *   SELECTED workflow snapshot + project registers) — no direct
  *   status.json / snapshot file reads to change. The build is TTL-memoized
@@ -64,7 +60,7 @@
  * - Registration is deferred through `ctx.inject(['systemPrompt'], …)`
  *   (HMR-safe re-apply): the `section()`/`context()` calls run on the
  *   inject child, and the exact disposers they return are collected on
- *   that child via `systemPromptCtx.effect` (plan QC fix wave W-HMR) — the
+ *   that child via `systemPromptCtx.effect`  — the
  *   registrations therefore unwind with THIS plugin's apply by explicit
  *   ownership, so a re-apply disposes the old registrations before
  *   registering fresh ones (no duplicate-name throw, no stale closure from

package/dist/gates/tools.d.ts

@@ -18,7 +18,7 @@ import { HarnessResolver } from './_shared.ts';
 export declare function registerSddIterationTools(ctx: Context, resolver: HarnessResolver): void;
 /**
  * Register the on-demand seam validation tools (
- * 20260808-dsh-seams-bundle): `mstar design-md validate` / `mstar compound
+ * : `mstar design-md validate` / `mstar compound
  * validate` CLI mirrors plus the audit / roles validators — thin wrappers
  * running the engine in-app. The registrations are deferred with
  * `ctx.inject(['tools'], …)` (same optional-unit pattern as the sdd tools),

package/dist/gates/workflow-ledger.d.ts

@@ -1,7 +1,5 @@
 /**
- * Workflow-ledger session-event consumer (plan `20260815-dsh-workflow-ledger`
- * Task 3 — the W-B2 producer half).
- *
+ * Workflow-ledger session-event consumer. *
  * Source of record: the durable `tool-workflow/*` session events appended
  * into the CALLING PARENT session's log (top-level runs only — nested
  * transport calls record nothing upstream; Task 1 seam notes §4). The
@@ -19,9 +17,8 @@
  *     forked conversation — `session/created` fires after the seed enters
  *     the log, upstream `session/src/index.ts:961-995`) gets its snapshot
  *     cold-scanned ONCE on the creation announcement, closing the
- *     late-seeded-session gap (qc3 S-304 / qc2 W-1a).
- *
- * DEDUPE (qc2 W-1 / qc3 F-301 fix-wave): ONE DURABLE per-session watermark —
+ *     late-seeded-session gap. *
+ * DEDUPE : ONE DURABLE per-session watermark —
  * the next expected envelope `seq` (session-log position) — persisted to
  * `{HARNESS_DIR}/workflows/<id>/workflow-ledger-cursors.json` (a small
  * bounded sidecar next to the workflow-dir `agent-flow.jsonl`, written
@@ -31,17 +28,16 @@
  * created-backfill / live): envelopes with `seq` below it were already
  * recorded — across cold+live overlap AND across plugin re-applies (a
  * re-registration no longer re-records the same live sessions). The
- * watermark advances only AFTER the ledger row appended successfully (qc3
- * R-401 — a failing append leaves the cursor behind, so the row is
- * re-attempted at the next scan, never permanently lost). The in-memory
+ * watermark advances only AFTER the ledger row appended successfully (a failing append leaves the cursor behind, so the
+ * row is re-attempted at the next scan, never permanently lost). The in-memory
  * Map is the durable file's mirror (module-level cache keyed by WORKFLOW
  * DIR, bounded by the session cap AND by a workflow-dir count cap — qc3
  * S-4 — so a long-lived process across many workflow ids never grows the
  * cache unbounded); a failed durable write keeps the in-memory mirror
- * advanced (in-process dedupe — qc3 S-6) with one warn — a ledger row is
+ * advanced (in-process dedupe —) with one warn — a ledger row is
  * never lost and the workflow run is never affected.
  *
- * INTER-PROCESS SERIALIZATION (qc3 W-1 fix-wave): the watermark
+ * INTER-PROCESS SERIALIZATION : the watermark
  * read-modify-write (load fresh → mutate → whole-map save) runs inside the
  * per-workflow write lock shared with the ledger append
  * (`withWorkflowDirLock` from agent-flow.ts — the same lockdir pattern as
@@ -52,16 +48,15 @@
  * process's just-advanced cursor (the duplicate-row regression mode). The
  * lock is held only around the bounded cursor update, never across scans.
  *
- * Mapping (Task 2 schema): `tool-workflow/run-start` → `workflow-run`
+ * Mapping: `tool-workflow/run-start` → `workflow-run`
  * (`agent` = the carrying parent session id), `tool-workflow/agent-start` →
  * `workflow-agent` (`childId` preserved), `tool-workflow/run-end` →
  * `workflow-run-end`. `tool-workflow/agent-end` is upstream MEMBER
- * bookkeeping with no ledger kind (Task 2 handoff + plan Interfaces — the
+ * bookkeeping with no ledger kind (the
  * member `outcome` is intentionally not persisted) and is filtered out.
  * `ts` takes the envelope's `time`.
  *
- * P-c answer observation (plan `20260815-dsh-workflow-gate` Task 4 fold-in —
- * the Task-2 Important handoff): the workflow GATE cannot observe the ask
+ * P-c answer observation : the workflow GATE cannot observe the ask
  * outcome — the tool registry's `serviceAsk` consumes the approval result
  * internally, and the gate invents no answerer. The run-start observation
  * IS the answer seam: when the approval waterfall ALLOWS a workflow call,
@@ -69,7 +64,7 @@
  * (name carried) lands in the parent session log — the consumer maps it to
  * the `workflow-run` row AND records `allow` for the run name into the
  * apply-scoped {@link WorkflowAskCache} (`registerWorkflowLedger`'s third
- * parameter — the host adapter's instance). W-1 (qc2 fix-wave): the record
+ * parameter — the host adapter's instance). the record
  * fires ONLY for names the policy marked asked in this apply
  * (`WorkflowAskCache.markAsked` on every ask verdict; the observation
  * promotes via `wasAsked`) — a run observed without a prior ask (P-b
@@ -107,8 +102,8 @@ import type { WorkflowAskCache } from './workflow-policy.ts';
 /** Logger label for the workflow-ledger consumer (dsh logger naming: `<scope>/<subject>`). */
 export declare const WORKFLOW_LEDGER_LOGGER = "mstar/workflow-ledger";
 /**
- * The durable watermark file name under the WORKFLOW dir (qc2 W-1 / qc3
- * F-301 fix-wave): `{ "v": 1, "cursors": { "<sessionId>": <nextSeq> } }` —
+ * The durable watermark file name under the WORKFLOW dir (/ qc3
+ * F-301 : `{ "v": 1, "cursors": { "<sessionId>": <nextSeq> } }` —
  * the next expected envelope seq per session id. Written atomically
  * (temp-file + rename) after every recorded workflow row; read lazily per
  * workflow dir (module-level cache). v3 layout: the sidecar lives in the
@@ -126,8 +121,7 @@ export declare const WORKFLOW_LEDGER_WATERMARK_FILE = "workflow-ledger-cursors.j
  */
 export declare const WORKFLOW_LEDGER_WATERMARK_MAX_SESSIONS = 256;
 /**
- * Workflow-dir count cap for the module-level watermark cache (qc3 S-4
- * fix-wave): a long-lived process can touch many workflow ids over its
+ * Workflow-dir count cap for the module-level watermark cache: a long-lived process can touch many workflow ids over its
  * lifetime (each iteration lifecycle creates a new workflow dir) — the
  * cache evicts the OLDEST cached dir when it exceeds this cap. The file is
  * the durable store; the cache is only a mirror, so an evicted dir is
@@ -144,12 +138,11 @@ export type WorkflowLedgerLogSink = (level: WorkflowLedgerLogLevel, message: str
  * can restore it (test pattern: agent-flow `setAgentFlowLogger`).
  */
 export declare function setWorkflowLedgerLogger(sink: WorkflowLedgerLogSink): WorkflowLedgerLogSink;
-/** The number of workflow dirs currently mirrored in the module-level watermark cache (qc3 S-4 observability). */
-export declare function workflowLedgerWatermarkCacheSize(): number;
+/** The number of workflow dirs currently mirrored in the module-level watermark cache */ export declare function workflowLedgerWatermarkCacheSize(): number;
 /**
  * Advance one session's watermark entry to `nextSeq` and persist. Runs the
  * whole read-modify-write under the per-workflow inter-process lock
- * (qc3 W-1 fix-wave — same lock as the ledger append): the fresh load
+ * (same lock as the ledger append): the fresh load
  * starts from the latest durable cursors, so two processes sharing one
  * lifecycle never clobber each other's advances; the session entry is
  * monotonic (`Math.max` — a stale concurrent advance never regresses an
@@ -161,7 +154,7 @@ export declare function workflowLedgerWatermarkCacheSize(): number;
  * evicted session re-records) is bounded by the cap and documented in the
  * README.
  *
- * DEGRADED PATH (qc3 S-6 fix-wave): a lock timeout (another writer stuck
+ * DEGRADED PATH : a lock timeout (another writer stuck
  * for the full timeout — a crashed/stuck peer), a reentrancy error, or a
  * throwing critical section leaves the durable file untouched, but the
  * in-memory mirror is STILL advanced (the same monotonic `Math.max`;
@@ -189,7 +182,7 @@ export declare function advanceWatermark(workflowDir: string, sid: string, nextS
 }): void;
 /**
  * Register the workflow-ledger consumer: (1) a `session/created` backfill
- * listener (registered FIRST — qc3 S-305 — so no apply-time window exists
+ * listener (registered FIRST — — so no apply-time window exists
  * between the snapshot and the attach); (2) a bounded cold scan over
  * `ctx.sessions.list()` reading each session's `events` snapshot for
  * `tool-workflow/*` rows (covers pre-restart runs — constructor-seeded
@@ -199,10 +192,10 @@ export declare function advanceWatermark(workflowDir: string, sid: string, nextS
  * persisted to `{HARNESS_DIR}/workflows/<id>/workflow-ledger-cursors.json` —
  * the ACTIVE workflow dir, never the root) — re-applies
  * never duplicate; no other cache. The watermark advances only AFTER a
- * successful ledger append (qc3 R-401 — a failing append leaves the cursor
+ * successful ledger append (a failing append leaves the cursor
  * behind so the row is re-attempted at the next scan, never lost). Every
  * read/append is try/catch-contained — including `sessions.list()` itself
- * (qc2 S-7: one warn, the cold scan skipped, the consumer stays live); the
+ * (one warn, the cold scan skipped, the consumer stays live); the
  * `sessions` service absent → one debug log + consumer disabled (composition
  * without dsh-session). All appends go through `recordWorkflowEvent` (itself
  * fully contained — a failing ledger write never crashes or alters a
@@ -212,7 +205,7 @@ export declare function advanceWatermark(workflowDir: string, sid: string, nextS
  * @param resolver - the shared per-workspace `{HARNESS_DIR}` resolver
  *   (harnessDir attribution from the carrying session's `header.cwd`).
  * @param workflowAskCache - the apply-scoped P-c ask cache (plan
- *   `20260815-dsh-workflow-gate` Task 4 fold-in — the host adapter's
+ *     Task 4 fold-in — the host adapter's
  *   instance; see the module doc "P-c answer observation"). Absent → the
  *   observation hook is disabled (W-B2 tests / compositions without the
  *   workflow gate).

package/dist/gates/workflow-policy.d.ts

@@ -1,10 +1,9 @@
 /**
  * Workflow/ralph gate policy — the P-a name allowlist + P-b lease
- * attribution + P-c first-seen ask (plan `20260815-dsh-workflow-gate`
- * Tasks 2–3, W-B3). The policy is the SINGLE
+ * attribution + P-c first-seen ask . The policy is the SINGLE
  * decision point for the four-tier `workflowGate` mode semantics
  * (`off | warn | ask | hard`, default `warn`): it turns one composed
- * {@link WorkflowGateInput} (Task 1) into `allow | warn | ask | deny` + a
+ * {@link WorkflowGateInput}  into `allow | warn | ask | deny` + a
  * reason. The dispatch-gate listener maps the verdict to the
  * `tools/pre-execute` refusal vocabulary (`PreToolDecision`) — this module
  * NEVER throws and NEVER builds an approval path: an `ask` verdict flows
@@ -21,7 +20,7 @@
  * | ralph (no `meta.name`), covered/read-only | any | allow — P-a/P-c NEVER apply to ralph (no allowlist identity); P-b applies |
  * | workflow, name ∈ `workflowNames` (non-empty list), covered | any | allow — the allowlist passes under every mode |
  * | workflow, unknown (empty/absent list ⇒ EVERY name unknown), covered | `off` | allow — the gate short-circuits `off` before the policy; kept here for a total policy |
- * | workflow, unknown, covered | `warn` | warn — advisory + one warn (Task 1 behavior, now centralized) |
+ * | workflow, unknown, covered | `warn` | warn — advisory + one warn (centralized) |
  * | workflow, unknown, covered | `hard` | deny — reason names the workflow name, veto before any child starts |
  * | workflow, unknown, covered, first-seen (no cached decision) | `ask` | ask — `{kind:'ask'}` through the approval waterfall + the name is marked asked (W-1 — the run-start observation promotes only asked names to allow) |
  * | workflow, unknown, covered, cached allow | `ask` | allow — cached decision, NO re-ask |
@@ -34,8 +33,7 @@
  * and a fresh apply starts with an empty cache. The cache records only
  * RESOLVED decisions (`allow` | `deny`) keyed by workflow name.
  *
- * Cache-key normalization (Task 5 fold-in — the Task-4 Important congruence
- * fix): every key — the gate's `metaName` (composed through
+ * Cache-key normalization (the congruence fix): every key — the gate's `metaName` (composed through
  * {@link normalizeWorkflowName} in dispatch.ts `workflowGateInputOf`), the
  * run-start observation's `runName` (workflow-ledger.ts), and the explicit
  * `record()` / `markAsked()` APIs (which normalize internally, F-302) — is
@@ -50,15 +48,14 @@
  * `serviceAsk` consumes the approval result internally (`deepseek-harness
  * packages/core/tools/src/index.ts`, `prepareExecution`/`serviceAsk`) — so
  * the ANSWER reaches the cache through the workflow-ledger consumer's
- * run-start observation (plan `20260815-dsh-workflow-gate` Task 4 fold-in —
- * the Task-2 Important handoff): an ALLOWED ask executes the call, the
+ * run-start observation : an ALLOWED ask executes the call, the
  * durable `tool-workflow/run-start` session event carries the run name, and
  * the consumer records `allow` for it (`workflow-ledger.ts`). The policy
  * marks every name that received an `ask` verdict in this apply
  * (`markAsked`, at the single ask point), and the observation promotes ONLY
  * marked names to `allow` — a run observed WITHOUT a prior ask (a P-b
  * advisory under `ask` mode, a `warn`/`off`-mode run) is NOT an approval
- * resolution and never pre-authorizes the name (qc2 W-1). A DENIED answer
+ * resolution and never pre-authorizes the name . A DENIED answer
  * produces no run → no observation → the next same-name call re-asks
  * (fail-closed — no grant evidence, never an invented allow). The explicit
  * `record()` API stays the general seam — an answerer integration or the
@@ -69,7 +66,7 @@
  * (`WorkflowGateInput` — erased at runtime, no cycle); dispatch.ts imports
  * the policy/cache values from here. The P-a vocabulary
  * (`workflowNameUnknown`, `WORKFLOW_NAME_UNKNOWN_CODE`) centralized HERE from
- * Task 1's dispatch.ts.
+ * 's dispatch.ts.
  */
 import type { Config } from './_shared.ts';
 import type { WorkflowGateInput } from './dispatch.ts';
@@ -81,16 +78,15 @@ import type { WorkflowGateInput } from './dispatch.ts';
 export declare const WORKFLOW_NAME_UNKNOWN_CODE = "workflow.name.unknown";
 /**
  * The workflow-gate advisory/deny violation code for P-b lease attribution
- * (Task 3): the calling workspace has an `InProgress` plan without
+ * : the calling workspace has an `InProgress` plan without
  * `execution_lease` coverage (warn-mode advisory / hard-mode veto reason —
  * the reason cites the uncovered plan id).
  */
 export declare const WORKFLOW_LEASE_UNCOVERED_CODE = "workflow.lease.uncovered";
 /**
  * Strip ASCII control characters (newlines / tabs / CR — the log-forging
- * surface, qc2 S-1) from one workflow name. THE shared P-c cache-key
- * normalization (plan `20260815-dsh-workflow-gate` Task 5 fold-in — the
- * Task-4 Important congruence fix): the gate's `metaName` (composed in
+ * surface( from one workflow name. THE shared P-c cache-key
+ * normalization : the gate's `metaName` (composed in
  * dispatch.ts `workflowGateInputOf`) and the run-start observation's
  * `runName` (workflow-ledger.ts) MUST key the ask cache through the SAME
  * function — a raw-vs-stripped mismatch (e.g. `au\u0000dit` gating under
@@ -108,7 +104,7 @@ export declare function normalizeWorkflowName(value: string): string;
  * `meta.name` — P-a never applies to them (callers guard on
  * `input.metaName !== undefined` first).
  *
- * Comparison boundary (qc1-S2): entries are normalized through
+ * Comparison boundary: entries are normalized through
  * {@link normalizeWorkflowName} BEFORE the comparison — the gate's
  * `metaName` is already stripped, so an operator-pasted control-char
  * variant (trailing newline, copied config value) matches the same
@@ -124,7 +120,7 @@ export type WorkflowAskCacheDecision = 'allow' | 'deny';
  * see the module doc for the lifecycle). Records ONLY resolved decisions; a
  * miss means first-seen (or an unanswered ask) → the policy asks again.
  *
- * W-1 (qc2 fix-wave): the cache ALSO tracks which names received an `ask`
+ * The cache ALSO tracks which names received an `ask`
  * verdict in this apply ({@link markAsked} — the gate marks EVERY ask
  * decision at the policy's single ask point). The run-start observation
  * (workflow-ledger.ts) records `allow` ONLY for names marked-asked — a run
@@ -132,7 +128,7 @@ export type WorkflowAskCacheDecision = 'allow' | 'deny';
  * `warn`/`off`-mode run) is NOT an approval resolution and must not
  * pre-authorize the name.
  *
- * F-302 (qc3 fix-wave): the WRITE seams ({@link record} / {@link markAsked})
+ * The WRITE seams ({@link record} / {@link markAsked})
  * normalize their keys internally — the "ONE shared normalization" contract
  * holds even for a caller that passes a raw spelling (today's production
  * callers already normalize before calling; this is defense-in-depth for the
@@ -163,7 +159,7 @@ export declare class WorkflowAskCache {
     /** Whether `name` received an `ask` verdict in this apply (the observation's promote gate). Normalizes internally. */
     wasAsked(name: string): boolean;
 }
-/** The four-tier policy decision vocabulary (plan W-B3, Task 2). */
+/** The four-tier policy decision vocabulary (plan W-B3). */
 export type WorkflowPolicyDecision = 'allow' | 'warn' | 'ask' | 'deny';
 /**
  * One policy verdict: the decision + a human-readable reason + the violation
@@ -181,7 +177,7 @@ export type WorkflowPolicyVerdict = {
 };
 /**
  * The workflow/ralph gate policy — P-a name allowlist + P-c first-seen ask
- * (plan `20260815-dsh-workflow-gate` Task 2). `config` + cache + composed
+ * . `config` + cache + composed
  * input → verdict; the caller (dispatch gate) maps the verdict to the
  * `PreToolDecision` refusal vocabulary and owns the advisory emit/log
  * infrastructure. The ONE cache write is contained: an `ask` verdict marks

package/dist/gates/workflow-selection.d.ts

@@ -2,7 +2,7 @@ import type { WorkflowSelectionView } from '../types.ts';
 /** The active-set resolver result: the first active lifecycle or a clear error. */
 export type ActiveWorkflowSelection = WorkflowSelectionView;
 /**
- * Test-only observability hook (plan 20260822-gate-fixes Task 3 / f12):
+ * Test-only observability hook :
  * whether a snapshot path is still cached. Production code never calls
  * this — the eviction contract (delete → key gone) is asserted by the
  * workflow-selection spec.
@@ -15,8 +15,8 @@ export declare function _terminalStatusCacheHas(snapshotPath: string): boolean;
  * entry → a clear error, never a terminal snapshot and never the root v1
  * file.
  *
- * Active-set definition (explicit decision, plan `20260819-workflow-dsh-viz`
- * Task 2): membership in `workflows[]` — the engine lifecycle enum's
+ * Active-set definition (explicit decision,
+ * membership in `workflows[]` — the engine lifecycle enum's
  * non-terminal states are `running` AND `paused` (terminal lifecycles are
  * removed from the list at terminal). A PAUSED lifecycle therefore stays in
  * the active set and the agent-flow writer / ledger append to its workflow