/**
 * Kanban → completed-work ledger bridge.
 *
 * Links the two evidence systems: when a task's verification report is
 * produced (verify_completion, the completion gate via mark_assignment, or a
 * managed Done transition), the session's completed-work ledger gets an entry
 * pointing back at the report. The kanban package cannot do this itself — it
 * has zero core dependency — so the bridge lives here in tools, which owns
 * both sides.
 *
 * Best-effort by contract: a ledger failure must never turn a successful
 * board mutation into an apparent task failure.
 */
import type { Context } from '@wrongstack/core/agent';
import type { KanbanVerificationReport } from '@wrongstack/kanban';
/** Stable dedupe key — re-verifying the same task updates the entry in place. */
export declare function kanbanEvidenceKey(boardId: string, taskId: string): string;
/** Parseable deep-link pointer to the persisted report. */
export declare function kanbanEvidencePointer(boardId: string, taskId: string): string;
export declare function recordKanbanVerificationEvidence(ctx: Context, report: KanbanVerificationReport): void;
//# sourceMappingURL=kanban-evidence-bridge.d.ts.map