/** * task Command - Inspect execution contracts and their outcomes * Issue #1545 (Phase 2-1) * * `task list` answers "what was this worktree asked to do", `task show` answers * "what did the gates say about it" — the two halves of a contract that used to * exist only inside the message text. */ import { Command } from 'commander'; import type { RelayCountsResponse } from '../types/api-responses'; /** * The relay counts for the session this task ran in, or null (Issue #2377). * * Scoped to the task's own worktree AND instance, because that is the session a * relay would have been opened by or against — a worktree-wide count would put * another agent's delegations on this task's page. * * Best effort: a daemon with no relay ledger is one that answers 404 here, which * must not fail `task show`. */ /** * What {@link readTaskRelayCounts} answers (Issue #4082): the per-state counts * and, apart from them, the payloads held as `uncertain` now. `held` is null * when the server did not say (older than #4082) — never 0 then. */ export interface TaskRelaySummary { counts: RelayCountsResponse; held: number | null; } /** The `RELAYS:` line of `task show` (Issue #2377; held count Issue #4082). */ export declare function formatTaskRelayLine(summary: TaskRelaySummary): string; export declare function createTaskCommand(): Command; //# sourceMappingURL=task.d.ts.map