/** * The worktree (S2) card of the ledger view: the research process rendered * as a git-like working tree — lanes (branches) grouped mainline-first, * then open, then merged (✓), then dead ends (✗, each with its documented * No: the reason and the days since the lane's last touch at close). The * three structural writes are the user's own declarations (the mainline ref * move, the derivation edge, the close); the system never infers or ranks. * All reads and writes flow through the injected controller verbs; this * component owns only the close-reason draft and the per-lane busy state. * @module dsh-client-ui-mimir/client/WorktreeView */ import type { ResearchWorktreeSlice, ResearchFailureView } from './controller.ts'; import type { ResearchT } from './view-common.ts'; /** * @param props - the worktree slice, the controller verbs, and copy. * @returns the worktree card (banner + grouped lanes + counts). */ export declare function WorktreeView({ worktree, refreshWorktree, setMainline, setIdeaParent, adoptIdea, closeIdea, refreshLedger, t, }: { readonly worktree: ResearchWorktreeSlice; readonly refreshWorktree: () => void; readonly setMainline: (lineId: string) => Promise; readonly setIdeaParent: (ideaId: string, parentIdeaId: string | null) => Promise; readonly adoptIdea: (ideaId: string) => Promise; readonly closeIdea: (ideaId: string, reason: string) => Promise; /** Refresh the ledger timeline (a documented No lands as a ledger event too). */ readonly refreshLedger: () => void; readonly t: ResearchT; }): import("react").JSX.Element; //# sourceMappingURL=WorktreeView.d.ts.map