@linxin666/dsh-client-ui-task-board 0.4.4 → 0.4.6

package/lib/types/core/tasks.d.ts

@@ -5,7 +5,9 @@
  * unit-testable in isolation.
  */
 import type { FreezeSnapshot } from './freeze-snapshot.ts';
+import type { ExecutionVerification } from './verification.ts';
 import type { TaskHandover, TaskHandoverInput } from './handover.ts';
+import { type TaskBoardExtensionPayload } from './extension.ts';
 /** Task lifecycle status, one per kanban column. */
 export type TaskStatus = 'backlog' | 'todo' | 'running' | 'done' | 'failed';
 /** Settled outcome of one execution attempt. */
@@ -32,8 +34,23 @@ export interface ExecutionRecord {
      * Session id of the DSH session that issued the run/rerun action (issue #6
      * audit origin). Client-asserted, not a trust boundary; absent when the run
      * was triggered by cron (source unknown).
+     *
+     * On an EXTERNAL record (issue #1826) this names the agent that completed the
+     * work outside the Host instead, which is what makes the history readable.
      */
     initiatedBy?: string;
+    /**
+     * True when this outcome was recorded from outside the Host by
+     * `record-external-outcome` rather than observed from a DSH session
+     * (issue #1826).
+     *
+     * The board never manufactures one of these itself: every Host-side path
+     * (`run`, `settle`, cascade folding, restart recovery) writes an execution
+     * without it, so `external` is the single field separating work this Host ran
+     * from work an outside agent reported. Such a record never carries a
+     * `sessionId` and never claims a verdict the Host observed.
+     */
+    external?: boolean;
     /** Freeze instant captured from the card snapshot when the run opened. */
     frozenAt?: number;
     /** Freeze source session captured from the card snapshot when the run opened. */
@@ -52,6 +69,14 @@ export interface ExecutionRecord {
     ownResult?: ExecutionOutcome;
     /** Human failure text that arrived with {@link ownResult}. */
     ownError?: string;
+    /**
+     * Goal acceptance state of this execution (task-board goal verification).
+     * Fixed when the execution starts and never rewritten from later settings:
+     * the contract is frozen here, the attempts accrue here, and the settlement
+     * rule reads the pass record here. Absent on an execution that started
+     * before the feature existed, which keeps it on the historical verdict.
+     */
+    verification?: ExecutionVerification;
 }
 /**
  * Maximum number of execution records retained per task. Older settled runs
@@ -66,17 +91,69 @@ export declare const EXECUTION_HISTORY_LIMIT = 20;
  * cannot start a new run while one is still open.
  */
 export declare function retainRecentExecutions(executions: readonly ExecutionRecord[]): ExecutionRecord[];
+/**
+ * How a rule produces its triggers: a recurring cron rule, or one single
+ * planned instant. The distinction is stored rather than inferred so a
+ * one-shot is never represented as a date-restricted cron expression.
+ */
+export type ScheduleMode = 'cron' | 'once';
+/**
+ * Why a due occurrence produced no run, or why a rule stopped on its own.
+ *
+ * These are stable codes, not display text: the board renders them through its
+ * locale dictionary, so the ledger never carries a translated string.
+ */
+export type ScheduleStopReason = 
+/** The single planned instant produced its run. */
+'fired'
+/** The recurring rule reached its run budget. */
+ | 'limit'
+/** The plan has no reachable instant any more (an impossible cron). */
+ | 'no-target'
+/** The instant passed while the board was not running through it. */
+ | 'missed'
+/** The task already had an open execution, so this occurrence was skipped. */
+ | 'busy'
+/** An above-default permission was still unconfirmed, so this occurrence was skipped. */
+ | 'permission'
+/**
+ * A scheduled launch failed before any session existed, so the occurrence
+ * created no execution and its run was refunded rather than spent.
+ */
+ | 'launch-failed';
+/** Every stop reason this build understands; the repair and wire gates share it. */
+export declare const SCHEDULE_STOP_REASONS: readonly ScheduleStopReason[];
 /**
  * A scheduled-run rule attached to a task. The Host scheduler triggers the
  * task when `nextRunAt` is due and persists the rule in the Host ledger.
+ *
+ * A rule is either `cron` (the historical shape: a 5-field expression with an
+ * explicit IANA zone, optionally capped by `maxRuns`) or `once` (one planned
+ * instant, `at`, with an implicit budget of one run). Both modes count the
+ * executions the scheduler actually started in `runCount`; a rule that reaches
+ * its budget stops itself in the ledger (`enabled: false` + `endedReason`)
+ * instead of relying on the execution agent to disable it.
  */
 export interface ScheduleRule {
     /** Whether the schedule is armed. */
     enabled: boolean;
-    /** 5-field cron expression: `分 时 日 月 周`. */
-    cron: string;
     /**
-     * IANA zone the cron wall clock is read in (issue #1722). Absent means the
+     * Which kind of plan this rule carries. A rule loaded from a ledger written
+     * before the field existed normalizes to `cron` (its `cron` is the plan).
+     */
+    mode: ScheduleMode;
+    /**
+     * 5-field cron expression: `分 时 日 月 周`. Present on a `cron` rule and
+     * absent on a `once` rule.
+     */
+    cron?: string;
+    /**
+     * The instant a `once` rule executes (ms epoch). Kept after the run so the
+     * detail view can still show the planned time once the rule has ended.
+     */
+    at?: number;
+    /**
+     * IANA zone the wall clock is read in (issue #1722). Absent means the
      * Host process zone, which is what a rule written before zones were
      * persisted keeps using; the Host stamps its own zone at ledger migration so
      * a later `TZ` change cannot silently move an existing rule.
@@ -86,7 +163,51 @@ export interface ScheduleRule {
     nextRunAt: number | undefined;
     /** Instant of the latest scheduled trigger (ms epoch). */
     lastTriggeredAt: number | undefined;
+    /**
+     * Scheduled executions the Host has created under this rule. This is the
+     * run budget's counter: it counts executions that were successfully opened
+     * (whatever their later outcome), never completions, and a manual run never
+     * touches it. A skipped occurrence (busy / permission / missed / no target)
+     * creates no execution and therefore consumes nothing.
+     */
+    runCount: number;
+    /**
+     * Maximum scheduled executions for a `cron` rule; absent means unlimited
+     * (the historical behavior). A `once` rule has an implicit budget of one and
+     * stores no `maxRuns`.
+     */
+    maxRuns?: number;
+    /** Instant the rule stopped itself (ms epoch); absent while it may still fire. */
+    endedAt?: number;
+    /** Why the rule stopped itself; present with `endedAt`. */
+    endedReason?: ScheduleStopReason;
+    /** Instant of the latest occurrence that produced no run. */
+    skippedAt?: number;
+    /** Why that occurrence produced no run; present with `skippedAt`. */
+    skippedReason?: ScheduleStopReason;
 }
+/**
+ * The rule's total run budget: one for a one-shot, the stored cap for a
+ * recurring rule, and undefined when the rule is unlimited.
+ * @param rule - the schedule rule.
+ * @returns the budget, or undefined for an uncapped rule.
+ */
+export declare function scheduleRunBudget(rule: ScheduleRule): number | undefined;
+/**
+ * Whether a rule has no runs left. The scheduler refuses to open another
+ * execution for an exhausted rule, which is what makes the budget terminal
+ * regardless of restarts or repeated timer fires.
+ * @param rule - the schedule rule.
+ * @returns true when the run budget is spent.
+ */
+export declare function scheduleExhausted(rule: ScheduleRule): boolean;
+/**
+ * The instant a rule plans to fire next, for display, whatever its mode: the
+ * planned `at` of a one-shot, or the stored `nextRunAt` of a recurring rule.
+ * @param rule - the schedule rule.
+ * @returns the planned instant, or undefined when the rule carries none.
+ */
+export declare function schedulePlannedAt(rule: ScheduleRule): number | undefined;
 /**
  * Frozen context snapshot carried by a continuation card (issue #4): the
  * goal/progress/next text (already sanitized by the freeze gates) plus the
@@ -226,11 +347,27 @@ export interface TaskRecord {
      * armed with the composed execution prompt as its objective. The session then
      * keeps working automatic continuation rounds until the agent marks the goal
      * complete, and this board settles the execution on the goal's own end
-     * instead of at the first turn end. Absent means ON — the option is checked
-     * by default, so only an explicit `false` runs the task as a single plain
-     * turn. A session whose `/goal` command is refused still runs the prompt.
+     * instead of at the first turn end. Absent means OFF — the option is
+     * unchecked by default, so only an explicit `true` joins the goal run and
+     * every card that never touched it (including every card written before the
+     * field existed) runs one plain turn. A session whose `/goal` command is
+     * refused still runs the prompt.
      */
     goalRun?: boolean;
+    /**
+     * Run this task's goal executions WITHOUT the board's acceptance gate.
+     *
+     * Absent means INHERIT: the execution's applicability is decided by the
+     * board-wide `goalVerification` switch frozen at start, exactly as a card
+     * that never touched this option behaves. Only an explicit `true` opts the
+     * card out, and the execution records `applicability: 'disabled'` so the
+     * report says plainly that nothing certified this run.
+     *
+     * The opt-out is per execution, not per run: flipping it never rewrites the
+     * verdict rule of an execution already open, and a rerun or a scheduled
+     * occurrence reads the card's current value when it freezes its contract.
+     */
+    skipVerification?: boolean;
     /**
      * Frozen context snapshot for a continuation card; absent on plain tasks.
      * Sanitized before it enters the ledger (redaction, slash-command taint,
@@ -262,6 +399,20 @@ export interface TaskRecord {
      * absent means on-board.
      */
     archivedAt?: number;
+    /**
+     * Opaque external-provider metadata, keyed by extension id; optional and
+     * additive so existing tasks require no ledger migration. The board stores
+     * and forwards it without interpreting the keys — each provider owns the
+     * shape and validation of its own entry.
+     */
+    integrations?: Record<string, TaskBoardExtensionPayload>;
+    /**
+     * Whether the card is held off the board: it exists in the ledger (and its
+     * execution history is intact) but no column ever renders it. Providers
+     * create hidden cards for work they materialize but do not want displayed;
+     * absent means on-board.
+     */
+    hidden?: boolean;
 }
 /**
  * Statuses a task may be archived from: every status but `running`, whose
@@ -287,7 +438,7 @@ export interface NewTaskInput {
      * inherits the parent's unset execution targets.
      */
     parentId?: string;
-    /** Workspace the execution must run in; empty/absent = the recent workspace. */
+    /** Workspace the execution must run in; empty/absent = the creating session's workspace for a root task, else the recent workspace at execution time. */
     workspaceId?: string;
     /** Agent preset the execution session must be composed from; empty/absent = deployment default. */
     mode?: string;
@@ -300,20 +451,31 @@ export interface NewTaskInput {
     /** Run the subtree as an Agent Team (Team Lead session plus one teammate per direct subtask). */
     teamRun?: boolean;
     /**
-     * Start the execution with dsh's built-in `/goal`. Absent/true keeps the
-     * default (goal run); an explicit false requests a single plain turn.
+     * Start the execution with dsh's built-in `/goal`. Absent means the default
+     * (one plain turn); only an explicit true joins the goal run.
      */
     goalRun?: boolean;
     /**
-     * Optional scheduled-run rule requested at creation time (the new-task
-     * dialog): an enable flag, a 5-field cron expression, and the IANA zone its
-     * wall clock is read in (absent means the Host zone). The create use case
-     * arms it only when enabled and the expression is valid.
+     * Run this task's goal executions without the acceptance gate; absent
+     * inherits the board-wide `goalVerification` switch.
+     */
+    skipVerification?: boolean;
+    /**
+     * Optional scheduling rule requested at creation time (the new-task
+     * dialog): an enable flag, the kind of plan (a recurring 5-field cron
+     * expression, or one planned instant for a one-shot), an optional run cap,
+     * and the IANA zone its wall clock is read in (absent means the Host zone).
+     * The create use case arms it only when enabled and the plan is valid.
      */
     schedule?: {
         enabled: boolean;
-        cron: string;
+        mode?: ScheduleMode;
+        cron?: string;
+        /** Planned instant of a one-shot rule (ms epoch). */
+        at?: number;
         timeZone?: string;
+        /** Run cap of a recurring rule; absent means unlimited. */
+        maxRuns?: number;
     };
     /**
      * Optional frozen context snapshot (goal/progress/next, sanitized by the
@@ -333,13 +495,31 @@ export interface NewTaskInput {
      * ahead of the execution prompt; a bare name changes nothing at run time.
      */
     tags?: TaskTag[];
+    /** Opaque external-provider metadata keyed by extension id. */
+    integrations?: Record<string, TaskBoardExtensionPayload>;
+    /** Column the created card opens in; absent means the board default (todo). */
+    status?: TaskStatus;
+    /** Create the card off-board (held in the ledger, never rendered). */
+    hidden?: boolean;
 }
 /** The five kanban columns, in display order. */
 export declare const COLUMNS: readonly {
     status: TaskStatus;
     label: string;
 }[];
-/** Statuses a user may move a card to manually (execution states are owned by the runner). */
+/**
+ * Statuses a card may be moved to by hand: every column. The board UI and the
+ * agent tool surface share this one list, so no column can be manual on one
+ * surface and locked on the other.
+ *
+ * The column is a board statement, not a claim about a run. A hand-written
+ * `done`/`failed` declares that the work finished (or failed) outside a
+ * Host-run execution — human hands, an external system — and a hand-written
+ * `running` says the work is under way without a tracked session. None of them
+ * creates an {@link ExecutionRecord}, which is what keeps a declaration
+ * distinguishable from a recorded outcome in the card's execution history; the
+ * next settled run overwrites the column with the real one.
+ */
 export declare const MANUAL_STATUSES: readonly TaskStatus[];
 /** Statuses the runner may move a card to from 'running'. */
 export declare const RUNNER_SETTLE_STATUSES: readonly TaskStatus[];
@@ -347,8 +527,28 @@ export declare const RUNNER_SETTLE_STATUSES: readonly TaskStatus[];
 export declare const ALL_STATUSES: readonly TaskStatus[];
 /** Brand an unknown string as a status; undefined when it is not one. */
 export declare function isTaskStatus(value: unknown): value is TaskStatus;
-/** Whether a manual move target is allowed from the given status. */
+/**
+ * Whether the manual move `from` -> `to` is a legal *column* change: any
+ * column, and never the one the card already shows.
+ *
+ * Whether the card may be moved at all is a separate question. The lock an
+ * executing card carries belongs to its open execution, never to the column
+ * text, so it is {@link canMoveTask} — not this predicate — that expresses it.
+ */
 export declare function canMoveManually(from: TaskStatus, to: TaskStatus): boolean;
+/**
+ * Whether the board may move `task` to `to` by hand: the card is on-board,
+ * holds no open execution, and the target is a legal column change. The ledger,
+ * the detail view's status buttons and the board's drop handler all decide
+ * through this one predicate, so no two surfaces can disagree about a card.
+ */
+export declare function canMoveTask(task: TaskRecord, to: TaskStatus): boolean;
+/**
+ * Whether the task still has an execution the runner has not settled. This —
+ * not the `running` column — is what "the runner owns this card" means: a card
+ * parked in `running` by hand has no session and stays fully movable.
+ */
+export declare function hasOpenExecution(task: TaskRecord): boolean;
 /** Normalize one optional execution-target string: trim; blank collapses to undefined. */
 export declare function normalizeTargetId(value: string | undefined): string | undefined;
 /**
@@ -367,7 +567,8 @@ export declare function withStatus(task: TaskRecord, status: TaskStatus, now: nu
  * Merge a schedule patch into a task's schedule rule (creating it when
  * absent), with a fresh updatedAt. Keys present in the patch overwrite the
  * current value — including explicit `undefined`, which clears a field (used
- * to disarm `nextRunAt`); absent keys keep their current value.
+ * to disarm `nextRunAt` or to drop an ended/skip record); absent keys keep
+ * their current value.
  */
 export declare function withSchedule(task: TaskRecord, patch: Partial<ScheduleRule>, now: number): TaskRecord;
 /**
@@ -380,6 +581,16 @@ export declare function startExecution(task: TaskRecord, now: number, executionI
     task: TaskRecord;
     execution: ExecutionRecord;
 };
+/**
+ * The column a settled outcome puts a card in. The ONE derivation shared by
+ * every settlement path (issue #1826): a Host-run execution and an outcome an
+ * outside agent reported both land in the same column from the same rule, so
+ * the column never becomes a second, independent piece of state.
+ @param task - the card being settled.
+ @param outcome - the settled outcome.
+ @returns the status the card shows afterwards.
+ */
+export declare function settledStatus(task: TaskRecord, outcome: ExecutionOutcome): TaskStatus;
 /**
  * Settle a running execution: record the outcome and move the task into the
  * matching column. No-op (returns the input task) when the execution is not

package/lib/types/core/use-cases/task-schedule.d.ts

@@ -1,23 +1,37 @@
-import { type TaskRecord } from '../tasks.ts';
+import { type ScheduleMode, type ScheduleStopReason, type TaskRecord } from '../tasks.ts';
 /** Fields the schedule use case may change on a rule. */
 export interface SetSchedulePatch {
     enabled?: boolean;
+    /** Which kind of plan to write; an absent key keeps the current mode. */
+    mode?: ScheduleMode;
+    /** 5-field cron expression of a recurring rule. */
     cron?: string;
-    /** IANA zone for the cron wall clock; `null` clears it back to the Host zone. */
+    /** Planned instant of a one-shot rule (ms epoch). */
+    at?: number;
+    /** IANA zone for the wall clock; `null` clears it back to the Host zone. */
     timeZone?: string | null;
+    /** Run cap of a recurring rule; `null` clears it back to unlimited. */
+    maxRuns?: number | null;
 }
 /** Result of arming/disarming a rule. */
 export interface SetScheduleResult {
     /** The next ledger; unchanged reference when rejected. */
     tasks: readonly TaskRecord[];
-    /** Whether the rule was applied (false on unknown task / invalid cron). */
+    /** Whether the rule was applied (false on unknown task / invalid plan). */
     applied: boolean;
 }
 /**
- * Set an on-board task's schedule rule. A blank or invalid cron, an unknown or
- * archived task, or an unusable zone is rejected (state untouched); an enabled
- * rule computes the next run instant immediately in the rule's own zone, a
- * disabled one carries no next-run instant.
+ * Set an on-board task's scheduling rule. An unknown or archived task, an
+ * unusable zone, a blank or invalid cron, a one-shot with no usable instant,
+ * a one-shot armed in the past, and a run cap that is not a positive integer
+ * are all rejected (state untouched). An enabled rule computes its next run
+ * instant immediately — a one-shot's next instant IS its planned instant — and
+ * a disabled rule carries none.
+ *
+ * Arming a rule that was not enabled, or switching its kind, starts a fresh
+ * budget: the run counter and any previous stop/skip record are cleared. Edits
+ * to a live rule (expression, zone, cap) keep the consumed count, so an
+ * already-spent budget can never silently reset and overrun.
  * @param tasks - current ledger.
  * @param id - the task to schedule.
  * @param patch - rule fields to change (absent fields keep their current value).
@@ -26,9 +40,8 @@ export interface SetScheduleResult {
  */
 export declare function applySetSchedule(tasks: readonly TaskRecord[], id: string, patch: SetSchedulePatch, now: number, hostTimeZone: string): SetScheduleResult;
 /**
- * Roll a task's schedule rule forward (scheduler callback): persist the next
- * due instant and the trigger instant. No-op for tasks without a rule (deleted
- * mid-tick, for example).
+ * Roll a task's schedule rule forward (legacy pure-controller seam): persist
+ * the next due instant and the trigger instant. No-op for tasks without a rule.
  * @param tasks - current ledger.
  * @param id - the task to roll forward.
  * @param nextRunAt - next due instant (may be undefined to clear).
@@ -36,3 +49,48 @@ export declare function applySetSchedule(tasks: readonly TaskRecord[], id: strin
  * @param now - clock instant (ms epoch).
  */
 export declare function applyScheduleNextRun(tasks: readonly TaskRecord[], id: string, nextRunAt: number | undefined, lastTriggeredAt: number | undefined, now: number): readonly TaskRecord[];
+/**
+ * The effect one due occurrence has on its rule, applied by the Host ledger.
+ */
+export interface ScheduleProgress {
+    /** Executions this occurrence actually opened (0 or 1), added to the counter. */
+    consumed: number;
+    /** Next due instant; absent stops the rule. */
+    nextRunAt?: number;
+    /** Trigger instant recorded as `lastTriggeredAt` (a consumed run only). */
+    lastTriggeredAt?: number;
+    /** Terminal reason when the rule stops itself (disarms it). */
+    endedReason?: ScheduleStopReason;
+    /** Why this occurrence produced no run, when it did not. */
+    skippedReason?: ScheduleStopReason;
+}
+/**
+ * Refund the one scheduled run an occurrence consumed before its launch failed
+ * without ever creating a session. Nothing ran, so the run budget is restored
+ * and the rule is left able to serve its next occurrence — a launch failure
+ * must never silently spend the user's limited budget.
+ *
+ * A recurring rule keeps its already-rolled-forward target; a fire that ended
+ * the rule at its cap (no target left) is restored and re-armed at the next
+ * occurrence, so a failed launch consumes nothing. A one-shot has no later
+ * occurrence, so it is left stopped with `launch-failed` and its run returned.
+ * A rule the user disabled in the meantime is not resurrected.
+ * @param tasks - current ledger.
+ * @param id - the task whose occurrence is being refunded.
+ * @param now - clock instant (ms epoch).
+ * @param hostTimeZone - zone a rule with no stored zone follows.
+ * @returns the next ledger.
+ */
+export declare function applyScheduleRefund(tasks: readonly TaskRecord[], id: string, now: number, hostTimeZone: string): readonly TaskRecord[];
+/**
+ * Record what a due occurrence did to a task's rule: advance the run counter
+ * by the executions it opened, set the next target (or stop the rule), and
+ * note a terminal reason or a skipped occurrence. Nothing is written for a
+ * task that has no rule or has been archived mid-tick.
+ * @param tasks - current ledger.
+ * @param id - the task whose rule fired.
+ * @param progress - the occurrence's effect.
+ * @param now - clock instant (ms epoch).
+ * @returns the next ledger.
+ */
+export declare function applyScheduleProgress(tasks: readonly TaskRecord[], id: string, progress: ScheduleProgress, now: number): readonly TaskRecord[];

package/lib/types/core/use-cases/task-tag.d.ts

@@ -0,0 +1,48 @@
+/**
+ * Label-management use cases (issue: labels could not be cleaned up).
+ *
+ * A label lives on every task that carries it, so renaming or removing one is a
+ * ledger-wide edit, not a task edit: the board's label row is the union of the
+ * labels in use, and without these two transitions a label created by an
+ * afternoon experiment stayed on the board forever.
+ *
+ * Both transitions are pure ledger rewrites (no persistence, no notify — the
+ * controller and the Host ledger orchestrate those), and both are idempotent:
+ * a label that no task carries changes nothing and reports no error for the
+ * delete path (the desired end state already holds), while a rename from an
+ * unknown label is refused so a stale tab cannot silently do nothing.
+ *
+ * Renaming onto a name that is already in use MERGES the two: a task carrying
+ * both keeps the row it already had (with its execution hint) and loses the
+ * duplicate, which is the only reading that cannot lose a hint the user typed.
+ */
+import { type TaskRecord } from '../tasks.ts';
+/** Outcome of one ledger-wide label edit. */
+export interface TagEditResult {
+    /** The ledger after the edit, or the input unchanged when nothing applied. */
+    tasks: readonly TaskRecord[];
+    /** Whether any task actually changed (drives whether the caller persists). */
+    changed: boolean;
+    /** Refusal reason; the ledger is unchanged when set. */
+    error?: string;
+}
+/**
+ * Rename one label everywhere, merging into an existing label of the target
+ * name. Every touched task gets a fresh updatedAt; untouched tasks keep theirs.
+ * @param tasks - current ledger.
+ * @param from - the label to rename.
+ * @param to - the new name (an existing name merges the two labels).
+ * @param now - clock instant (ms epoch).
+ * @returns the rewritten ledger, or a refusal.
+ */
+export declare function applyRenameTag(tasks: readonly TaskRecord[], from: string, to: string, now: number): TagEditResult;
+/**
+ * Remove one label from every task that carries it. Archived cards are included:
+ * the board's label row draws from the whole ledger, so a label left on an
+ * archived card would come straight back into the filter.
+ * @param tasks - current ledger.
+ * @param name - the label to remove.
+ * @param now - clock instant (ms epoch).
+ * @returns the rewritten ledger.
+ */
+export declare function applyDeleteTag(tasks: readonly TaskRecord[], name: string, now: number): TagEditResult;

package/lib/types/core/use-cases/task-update.d.ts

@@ -15,7 +15,7 @@ import type { TaskHandoverInput } from '../handover.ts';
  * Editable fields on a task (the update patch surface). `freeze` replaces the
  * continuation-card snapshot (restamping frozenAt); an explicit null clears it.
  */
-export type TaskUpdatePatch = Partial<Pick<TaskRecord, 'title' | 'description' | 'prompt' | 'workspaceId' | 'mode' | 'permission' | 'model' | 'reuseSession' | 'teamRun' | 'goalRun'>> & {
+export type TaskUpdatePatch = Partial<Pick<TaskRecord, 'title' | 'description' | 'prompt' | 'workspaceId' | 'mode' | 'permission' | 'model' | 'reuseSession' | 'teamRun' | 'goalRun' | 'skipVerification'>> & {
     freeze?: FreezeSnapshot & {
         redacted?: boolean;
     } | null;
@@ -39,8 +39,10 @@ export declare const TASK_CONTENT_FIELDS: readonly ["title", "description", "pro
 export declare function hasContentPatch(patch: TaskUpdatePatch): boolean;
 /**
  * Whether a task's content may still be edited: the task must be on-board
- * (not archived) and must never have started executing. Fail-closed: a
- * running, settled, or cancelled-before-launch task keeps its content fixed.
+ * (not archived) and must never have started executing. Fail-closed: a task
+ * with any execution record — running, settled, or cancelled before launch —
+ * keeps its content fixed. The run, not the column, is the trigger: a card
+ * parked in 'running' by hand has nothing recorded yet and stays editable.
  */
 export declare function canEditTaskContent(task: TaskRecord): boolean;
 /**

package/lib/types/core/verification-budget.d.ts

@@ -0,0 +1,52 @@
+/** Judge calls one acceptance issues: every criterion, every round. */
+export declare const ACCEPTANCE_JUDGE_CALLS: number;
+/**
+ * Per-judge-call ceiling used when the row names none: two and a half minutes
+ * for a reasoning model reading an 80,000 character trace with a 16,384 token
+ * output cap. The former 120s constant was tight enough that a slow but healthy
+ * route produced a wall of per-call timeouts, and every one of them was charged
+ * as an acceptance anomaly against a budget that then failed the card.
+ */
+export declare const DEFAULT_VERIFICATION_CALL_TIMEOUT_SECONDS = 150;
+/** Shortest accepted per-call ceiling: below this no useful judge answers. */
+export declare const VERIFICATION_CALL_TIMEOUT_MIN_SECONDS = 30;
+/** Longest accepted per-call ceiling, ten minutes. */
+export declare const VERIFICATION_CALL_TIMEOUT_MAX_SECONDS = 600;
+/**
+ * Total ceiling of one acceptance attempt, covering evidence rendering and
+ * every judge call including retries. Derived from the per-call default rather
+ * than pinned, because a total budget smaller than
+ * {@link ACCEPTANCE_JUDGE_CALLS} times the per-call ceiling guarantees that no
+ * acceptance can ever finish.
+ */
+export declare const DEFAULT_VERIFICATION_BUDGET_SECONDS: number;
+/** Shortest accepted total budget: long enough for at least one judge call. */
+export declare const VERIFICATION_BUDGET_MIN_SECONDS = 120;
+/** Longest accepted total budget, thirty minutes. */
+export declare const VERIFICATION_BUDGET_MAX_SECONDS = 1800;
+/** The default total budget in milliseconds, the face the abort timer takes. */
+export declare const DEFAULT_VERIFICATION_BUDGET_MS: number;
+/**
+ * The effective per-judge-call ceiling.
+ * @param seconds - configured seconds, or undefined for the default.
+ * @returns the effective ceiling in seconds.
+ */
+export declare function normalizeVerificationCallTimeoutSeconds(seconds: number | undefined): number;
+/**
+ * The effective per-judge-call ceiling the timer face takes.
+ * @param seconds - configured seconds, or undefined for the default.
+ * @returns the effective ceiling in milliseconds.
+ */
+export declare function verificationCallTimeoutMs(seconds: number | undefined): number;
+/**
+ * The effective total budget of one acceptance attempt.
+ * @param seconds - configured seconds, or undefined for the default.
+ * @returns the effective budget in seconds.
+ */
+export declare function normalizeVerificationBudgetSeconds(seconds: number | undefined): number;
+/**
+ * The effective total budget the abort face takes.
+ * @param seconds - configured seconds, or undefined for the default.
+ * @returns the effective budget in milliseconds.
+ */
+export declare function verificationBudgetMs(seconds: number | undefined): number;