toolroll 0.9.103 → 0.9.105

package/dist/chat-messages.d.ts

@@ -1,338 +0,0 @@
-import { ChatCore } from "./chat-core.js";
-import { type ChatMessageOutcome } from "./chat-message-states.js";
-import type { Notification, NotificationReceipt, Run, TelegramAction, TelegramBinding, TelegramConversation, TelegramConversationPart, TelegramConversationPartPlan, TelegramDelivery, TelegramDigest, TelegramFlowAction, TelegramFlowChoice, TelegramFlowPrompt, TelegramProposalAction } from "./store.js";
-/** v83: a notification for another person, settled for this destination without sending. */
-export declare const TELEGRAM_SKIPPED_ELSEWHERE = "skipped:for-another-person";
-/** A met promise the lead made on another chat: reported there, settled here without sending. */
-export declare const TELEGRAM_SKIPPED_OTHER_CHAT = "skipped:for-another-chat";
-/** A fact this person is not messaged about: the lead's work, their own act, or a project they muted. */
-export declare const TELEGRAM_SKIPPED_QUIET = "skipped:quiet";
-/** A destination receipt (`d` = notification_delivery) that still owes a
- * send: not delivered, and not explicitly skipped as pre-pairing history.
- * Every reader of Telegram receipts that means "undelivered" uses this, so
- * a skip settles the row without ever pretending to be a delivery. */
-export declare const TELEGRAM_UNSETTLED = "d.delivered_at IS NULL AND (d.receipt IS NULL OR d.receipt NOT LIKE 'skipped:%')";
-/**
- * Why the store itself holds a Telegram delivery back: authority,
- * provenance, ordering, a switched-off channel, or a wait it imposed. A
- * row held for one of these is waiting on policy, not failing on the wire.
- * Every other error recorded on a receipt came from an actual send, and
- * THAT is delivery trouble (`pendingForAttention`). One table, so the
- * fences and the tally can never disagree about the words.
- */
-export declare const TELEGRAM_HOLD_REASONS: Readonly<{
-    authority: "Telegram pairing or actor authorization changed";
-    destination: "Telegram destination changed";
-    claim: "Telegram delivery claim expired or changed";
-    rateLimit: "Telegram rate limit is still active";
-    resolved: "Notification no longer needs delivery";
-    provenance: "Notification has no trusted project provenance";
-    installation: "Installation notification requires instance access";
-    project: "Notification project is not currently authorized and enrolled";
-    task: "Notification task provenance changed";
-    order: "Earlier task notification is still undelivered";
-    disabled: "Telegram delivery is disabled";
-}>;
-/** A note draft's states: `pending` and `armed` are live; the other three are final. */
-export type NoteDraftState = "pending" | "armed" | "superseded" | "consumed" | "discarded";
-export declare class ChatMessages extends ChatCore {
-    createDecisionAction(action: {
-        token: string;
-        binding: number;
-        decision: number;
-        optionId: string;
-        phase: "choose" | "confirm" | "cancel";
-        chatId: string;
-        messageId?: string;
-        ttlMs?: number;
-        /** Binds an irreversible confirmation to the EXACT note it showed. */
-        noteDigest?: string;
-    }, now: Date): void;
-    /** Which decision an outbound Telegram message carried. Recorded after the
-     * send returns its id; a send whose record was lost routes nothing. */
-    recordDecisionMessage(binding: number, chatId: string, messageId: string, decision: number, now: Date): void;
-    /** The decision behind an exact replied-to message, or nothing. Never "the latest". */
-    decisionForMessage(binding: number, chatId: string, messageId: string): number | null;
-    /** The one live, unexpired draft for a decision, if any. */
-    liveNoteDraft(binding: number, decision: number, now: Date): {
-        id: number;
-        note: string;
-        updateId: number;
-        state: string;
-    } | null;
-    /**
-     * Persist a validated note as the live draft. A newer update SUPERSEDES
-     * the old draft — drafts are immutable, and only a GREATER update_id may
-     * replace one, so out-of-order delivery cannot resurrect an older note
-     * (Codex free-text review, state machine). Returns false when an older
-     * or equal update tried.
-     */
-    saveNoteDraft(draft: {
-        binding: number;
-        decision: number;
-        updateId: number;
-        messageId: string;
-        replyTo: string;
-        note: string;
-    }, now: Date, ttlMs?: number): boolean;
-    /** Move a draft to `to`, only from one of the states in `from` (the check and the write are one statement). True when
-     * it moved; false when the draft was in none of them. The caller owns the transaction story. */
-    setNoteDraftState(id: number, from: readonly NoteDraftState[], to: NoteDraftState): boolean;
-    createFlowActions(at: {
-        binding: number;
-        chatId: string;
-        card: number;
-        entry: number;
-    }, actions: readonly {
-        token: string;
-        action: TelegramFlowAction["action"];
-    }[], now: Date, days?: number): void;
-    flowAction(token: string): TelegramFlowAction | null;
-    placeFlowActions(tokens: readonly string[], messageId: string): void;
-    /** Retire every button (and prompt) for one visit of a card, in every chat app: it was decided, or its draft replaced. */
-    retireFlowVisit(card: number, entry: number, now: Date): void;
-    recordFlowPrompt(prompt: TelegramFlowPrompt, now: Date, hours?: number): void;
-    /** The live prompt a message replies to, if any. */
-    flowPrompt(chatId: string, messageId: string, now: Date): TelegramFlowPrompt | null;
-    createFlowChoices(at: {
-        binding: number;
-        chatId: string;
-        card: number;
-        entry: number;
-    }, choices: readonly {
-        token: string;
-        choice: number;
-        label: string;
-    }[], now: Date, days?: number): void;
-    flowChoice(token: string): TelegramFlowChoice | null;
-    placeFlowChoices(tokens: readonly string[], messageId: string): void;
-    createQuestionActions(at: {
-        binding: number;
-        chatId: string;
-        question: number;
-    }, choices: readonly {
-        token: string;
-        choice: string | null;
-    }[], now: Date, days?: number): void;
-    questionAction(token: string): {
-        token: string;
-        binding: number;
-        question: number;
-        choice: string | null;
-        chatId: string;
-        messageId: string | null;
-        expiresAt: string;
-        consumedAt: string | null;
-    } | null;
-    placeQuestionActions(tokens: readonly string[], messageId: string): void;
-    /** Retire every button and prompt for a question, in every chat app: it was answered (anywhere). */
-    retireQuestion(question: number, now: Date): void;
-    recordQuestionPrompt(prompt: {
-        chatId: string;
-        messageId: string;
-        binding: number;
-        question: number;
-    }, now: Date, hours?: number): void;
-    questionPrompt(chatId: string, messageId: string, now: Date): {
-        chatId: string;
-        messageId: string;
-        binding: number;
-        question: number;
-    } | null;
-    decisionAction(token: string): TelegramAction | null;
-    /**
-     * Kill every live confirm/cancel challenge on a decision. Cancel means
-     * cancelled: a confirm that survived its own cancellation would be an
-     * irreversible choice still armed after the person said stop.
-     */
-    consumeChallenges(decision: number, now: Date): void;
-    /** Consume once. False means somebody already did, or it expired — either way, no. */
-    consumeDecisionAction(token: string, now: Date): boolean;
-    /** Stamp the message a choose-action's keyboard actually landed on. */
-    placeDecisionActions(tokens: readonly string[], messageId: string): void;
-    /** A Telegram message this bot sent that showed one task (v79): a reply to
-     * it is about that task (and that result, when it showed one). A message
-     * edited to show something else forgets it. */
-    recordTaskMessage(binding: TelegramBinding, messageId: string, taskId: string | null, run: number | null, now: Date): void;
-    /** v98: an update Telegram pushed, kept (queued, with its body) until the bridge applies it; false when it's already kept or applied. */
-    queueUpdate(botId: string, updateId: number, payload: string, now: Date): boolean;
-    /** v98: pushed updates waiting for the bridge, oldest first. */
-    inbox(botId: string, limit: number): {
-        updateId: number;
-        payload: string;
-    }[];
-    /** A pushed update the bridge is done with: applied (then its receipt stays), or unreadable (then it is gone). */
-    dropInbox(updateId: number): void;
-    /** True if this update has not been applied before. The (provider, id) key is the idempotency; a pushed update waiting
-     * in the inbox is applied in place. A receipt names only its update, as it always has. */
-    markUpdateApplied(updateId: number, result: string, now: Date): boolean;
-    /** Persist one ordinary message before its update is acknowledged (event m<update id>). The caller's transaction also marks the update applied. */
-    enqueueMessage(row: {
-        binding: TelegramBinding;
-        updateId: number;
-        messageId: string;
-        replyTo: string | null;
-        request: string;
-        text: string;
-        context: string | null;
-        taskId: string | null;
-        sourceRun: number | null;
-    }, now: Date): number;
-    /** How many of this chat's messages wait for, or are being answered by, the lead (the lead queue's bound per chat). */
-    messagesWaiting(binding: number): number;
-    /** Whether a message from this chat is already waiting on, or being answered from, this bot message (a tapped question). */
-    messageWaitingOn(binding: number, messageId: string): boolean;
-    getMessage(id: number): TelegramConversation | null;
-    listMessages(botId: string): TelegramConversation[];
-    /**
-     * Claim the oldest message that still needs a turn: queued, or running
-     * under a claim that lapsed (a crash mid-turn), and not deferred past now.
-     * One at a time per bot — the lead runs one turn per approver anyway.
-     */
-    claimMessage(botId: string, owner: string, ttlMs: number, now: Date, only?: "turns" | "replies"): TelegramConversation | null;
-    /** Extend a held claim; false means it lapsed and somebody else may hold the row. */
-    renewMessage(id: number, owner: string, ttlMs: number, now: Date): boolean;
-    /**
-     * Bind the session a turn is about to be dispatched under, BEFORE the
-     * dispatch: the engine receipts the request inside that session, so a
-     * later attempt — after a crash, even after the session was ended and
-     * replaced from the console — reads the receipt where it was written
-     * instead of resolving today's session and finding nothing there.
-     */
-    bindMessageSession(id: number, owner: string, session: number): boolean;
-    /** Bind the admitted turn to its row as soon as the engine's receipt names it. */
-    bindMessageTurn(id: number, owner: string, session: number, turn: number): boolean;
-    /**
-     * Settle a claimed row: done or failed with its outcome word, or back to
-     * queued for a later attempt (a busy engine). Only the claim holder may;
-     * a lapsed claim settles nothing, so a reclaimer's outcome stands.
-     * Telegram writes done here only once every part of the reply was sent
-     * or dropped; what done means on each app is in chat-message-states.ts.
-     */
-    finishMessage(id: number, owner: string, result: {
-        state: "done" | "failed";
-        outcome: ChatMessageOutcome;
-        replyMessageId?: string | null;
-    } | {
-        state: "queued";
-        outcome: ChatMessageOutcome;
-        nextAttemptAt: string;
-    }, now: Date): boolean;
-    /**
-     * Replies the assistant wrote that still have not reached the person
-     * `since` ago or longer (status and the console show them with a Retry):
-     * the message's row, whose it is, when the oldest unsent part was
-     * written, and the last send error.
-     */
-    unsentReplies(botId: string | null, approver: string | null, since: Date): {
-        conversation: number;
-        approver: string;
-        since: string;
-        error: string | null;
-    }[];
-    /** Send unsent replies on the next bridge pass instead of waiting out their backoff; returns how many. */
-    retryReplies(approver: string | null, now: Date): number;
-    /**
-     * Persist the whole outbound half of a turn — every reply part and every
-     * card, with the cards' tokens already minted — in one transaction, BEFORE
-     * any send. Only the claim holder may, and only once: a row that already
-     * has parts keeps them (a retry resumes, never re-plans). The turn's
-     * identity rides the row too, so the parts answer to exactly that turn.
-     */
-    planReplyParts(id: number, owner: string, turn: {
-        session: number;
-        turn: number;
-    }, parts: readonly TelegramConversationPartPlan[], now: Date): boolean;
-    replyParts(conversation: number): TelegramConversationPart[];
-    /**
-     * Settle one send attempt under the row's claim. A confirmed message id
-     * is the only success: the part is sent, and a reply part's id becomes
-     * the row's reply id. Anything else leaves the part pending with its
-     * attempt counted, its error named, its next attempt scheduled, and —
-     * when the answer was lost rather than refused — its uncertainty counted.
-     * A lapsed claim settles nothing, so a reclaimer's outcome stands.
-     */
-    settleReplyPart(conversation: number, ordinal: number, owner: string, outcome: {
-        ok: true;
-        messageId: string;
-    } | {
-        ok: false;
-        error: string;
-        uncertain: boolean;
-        retryAt: string;
-    }, now: Date): boolean;
-    /** A card whose proposal no longer waits (confirmed or dismissed from another surface, or gone) is moot: dropped with the reason, never sent. */
-    dropReplyPart(conversation: number, ordinal: number, owner: string, reason: string, now: Date): boolean;
-    /** The exact task/run bindings of one outbound message this bot sent: a
-     * plain fact names one, a digest part may name several, (v64) a confirmed
-     * result image names its exact task and run, the lead's reply names the
-     * task its turn was about, a card names its task, and (v79) a status
-     * message names the task it showed. */
-    messageBindings(binding: TelegramBinding, messageId: string): {
-        taskId: string | null;
-        taskRef: number | null;
-        run: number | null;
-        project: string | null;
-        image?: {
-            run: number;
-            artifact: number;
-            sha256: string;
-        };
-    }[];
-    createProposalAction(action: {
-        token: string;
-        binding: number;
-        proposal: number;
-        phase: TelegramProposalAction["phase"];
-        chatId: string;
-        messageId?: string;
-        ttlMs?: number;
-    }, now: Date): void;
-    proposalAction(token: string): TelegramProposalAction | null;
-    /** Consume once. False means somebody already did, or it expired. */
-    consumeProposalAction(token: string, now: Date): boolean;
-    /** Kill every live token on a proposal — after it resolves, or when a challenge is cancelled. */
-    consumeProposalActions(proposal: number, now: Date, phases?: readonly TelegramProposalAction["phase"][]): void;
-    /** Stamp the message a card's keyboard actually landed on. */
-    placeProposalActions(tokens: readonly string[], messageId: string): void;
-    destination(binding: TelegramBinding): string;
-    /** A progress card belongs to one builder result, including its root review.
-     * Do not combine planners, correction children, or separate build attempts. */
-    progressRun(row: Pick<Notification, "taskRef" | "run">): Run | null;
-    /** Reuse a confirmed message in this exact destination. A mixed digest,
-     * decision, image, or message naming another attempt is never editable. The
-     * outbound history survives a restart even if the final receipt was lost. */
-    progressMessage(binding: TelegramBinding, result: Run): string | null;
-    /** The existing outbox, with a separate receipt for this exact pairing. */
-    claimDeliveries(binding: TelegramBinding, owner: string, ttlMs: number, now: Date, only?: "all" | "urgent"): TelegramDelivery[];
-    /** Synchronous final fence, called AFTER each asynchronous enrollment read. */
-    deliveryProblem(row: TelegramDelivery, binding: TelegramBinding, owner: string, projects: readonly string[], now: Date, batch?: readonly number[]): string | null;
-    /**
-     * The watch at the final fence (cockpit §3, R11): right before the network, a person who has since opened the
-     * agent this ping is about holds it — the claim is released with the watch's end as its next attempt, no attempt
-     * spent — and news about a finished run they have now seen settles quietly. "send": nothing changed.
-     */
-    watchFence(row: TelegramDelivery, binding: TelegramBinding, owner: string, now: Date): "send" | "held" | "skipped";
-    claimHeld(row: TelegramDelivery, owner: string, now: Date): boolean;
-    /** A confirmed network message remains history even if authority changed
-     * while it was in flight. It only binds the OLD destination, never new work. */
-    recordMessage(row: TelegramDelivery, binding: TelegramBinding, messageId: string, now: Date): void;
-    /** The newest confirmed message this notification became at one destination, if any. */
-    messageOf(notification: number, destination: string): string | null;
-    finalizeDelivery(row: TelegramDelivery, binding: TelegramBinding, owner: string, outcome: {
-        ok: true;
-        receipt: string | null;
-    } | {
-        ok: false;
-        error: string;
-        retryAt?: string;
-    }, now: Date): boolean;
-    /** The notifications this pairing holds, each with its delivery state there. */
-    deliveries(binding: TelegramBinding): NotificationReceipt[];
-    /** The digest cadence: null everyMs = off. */
-    digest(): TelegramDigest;
-    /** Set (or clear, with null) the cadence. Turning it on starts the
-     * window NOW — nothing held before the choice is dumped at once. */
-    setDigest(everyMs: number | null, by: string, now: Date): void;
-    markDigestSent(now: Date): void;
-}

package/dist/chat-migration.d.ts

@@ -1,30 +0,0 @@
-import type { Database } from "./store.js";
-export type LegacyChatApp = "slack" | "discord" | "teams";
-export declare const LEGACY_CHAT_APPS: readonly LegacyChatApp[];
-/** One app's old tables, as an older database has (or should have had) them. */
-export declare const legacyAppSchema: (app: LegacyChatApp) => string;
-/** One app's 16 old tables, parents first. */
-export declare const legacyAppTables: (app: LegacyChatApp) => string[];
-/** Telegram's own tables (v1-v114) and the bridge's lease, kept verbatim. */
-export declare const LEGACY_TELEGRAM_SCHEMA = "\nCREATE TABLE IF NOT EXISTS telegram_flow_choice (\n  token       TEXT PRIMARY KEY,\n  binding     INTEGER NOT NULL REFERENCES telegram_binding(id) ON DELETE RESTRICT,\n  card        INTEGER NOT NULL REFERENCES flow_card(id),\n  entry       INTEGER NOT NULL,\n  choice      INTEGER NOT NULL,\n  label       TEXT NOT NULL,\n  chat_id     TEXT NOT NULL,\n  message_id  TEXT,\n  created_at  TEXT NOT NULL,\n  expires_at  TEXT NOT NULL,\n  consumed_at TEXT\n);\nCREATE INDEX IF NOT EXISTS telegram_flow_choice_visit ON telegram_flow_choice (card, entry);\n\n-- v79: a Telegram message that showed one task (a /task status, a task\n-- picked from /tasks): a reply to it is about that task. Like chat_focus,\n-- a pointer and never an authority \u2014 the turn re-proves the task.\nCREATE TABLE IF NOT EXISTS telegram_task_message (\n  binding    INTEGER NOT NULL,\n  chat_id    TEXT NOT NULL,\n  message_id TEXT NOT NULL,\n  task_id    TEXT NOT NULL,\n  source_run INTEGER,\n  created_at TEXT NOT NULL,\n  PRIMARY KEY (binding, chat_id, message_id)\n);\n\n\n-- Away mode (v34, mate arc \u00A710): the Telegram bridge's digest cadence.\n-- One row. every_ms NULL = off (every fact pages as it lands); set, the\n-- bridge holds ROUTINE rows unclaimed until the window elapses and sends\n-- them as one message \u2014 decisions and attention-class facts still page\n-- singly. last_sent_at anchors the window; it never deletes a row.\nCREATE TABLE IF NOT EXISTS telegram_digest (\n  id           INTEGER PRIMARY KEY CHECK (id = 1),\n  every_ms     INTEGER,\n  set_by       TEXT,\n  set_at       TEXT,\n  last_sent_at TEXT\n);\nINSERT OR IGNORE INTO telegram_digest (id, every_ms) VALUES (1, NULL);\n\n\n-- One Telegram chat speaking as one approver. Bindings are never deleted:\n-- revocation is a stamp, because \"who could answer as whom, when\" is an\n-- audit question a DELETE cannot answer. The partial unique index (v72) is\n-- the rule that one Telegram user has one live binding per bot: several\n-- teammates pair their own private chats with the same bot.\nCREATE TABLE IF NOT EXISTS telegram_binding (\n  id                  INTEGER PRIMARY KEY AUTOINCREMENT,\n  bot_id              TEXT NOT NULL,\n  chat_id             TEXT NOT NULL,\n  user_id             TEXT NOT NULL,\n  approver            TEXT NOT NULL REFERENCES approver(name) ON DELETE RESTRICT,\n  approver_generation INTEGER NOT NULL,\n  paired_at           TEXT NOT NULL,\n  paired_by           TEXT NOT NULL,\n  pair_update_id      INTEGER,\n  revoked_at          TEXT,\n  revoked_by          TEXT\n);\nCREATE UNIQUE INDEX IF NOT EXISTS telegram_binding_live_user\n  ON telegram_binding (bot_id, user_id) WHERE revoked_at IS NULL;\n\n-- v72: a Telegram chat's place in the shared team conversations. A group\n-- follows exactly one team conversation (and a conversation has at most one\n-- group); a private chat may select one conversation to talk in instead of\n-- its personal assistant. The cursor is the last conversation message this\n-- chat received. Rows are revoked, never deleted.\nCREATE TABLE IF NOT EXISTS telegram_team_chat (\n  id           INTEGER PRIMARY KEY AUTOINCREMENT,\n  bot_id       TEXT NOT NULL,\n  chat_id      TEXT NOT NULL,\n  binding      INTEGER NOT NULL REFERENCES telegram_binding(id) ON DELETE RESTRICT,\n  kind         TEXT NOT NULL CHECK (kind IN ('group','private')),\n  conversation TEXT NOT NULL REFERENCES team_conversation(id) ON DELETE RESTRICT,\n  bound_by     TEXT NOT NULL,\n  bound_at     TEXT NOT NULL,\n  cursor       INTEGER NOT NULL DEFAULT 0,\n  revoked_at   TEXT,\n  revoked_by   TEXT\n);\nCREATE UNIQUE INDEX IF NOT EXISTS telegram_team_chat_live\n  ON telegram_team_chat (bot_id, chat_id) WHERE revoked_at IS NULL;\nCREATE UNIQUE INDEX IF NOT EXISTS telegram_team_chat_group\n  ON telegram_team_chat (conversation) WHERE revoked_at IS NULL AND kind = 'group';\n\n\nCREATE TABLE IF NOT EXISTS telegram_outbound_message (\n  binding INTEGER NOT NULL REFERENCES telegram_binding(id) ON DELETE RESTRICT,\n  bot_id TEXT NOT NULL,\n  chat_id TEXT NOT NULL,\n  message_id TEXT NOT NULL,\n  notification INTEGER NOT NULL REFERENCES notification(id) ON DELETE RESTRICT,\n  destination TEXT NOT NULL,\n  project TEXT,\n  task_ref INTEGER REFERENCES task_ref(id),\n  task_id TEXT,\n  source_run INTEGER REFERENCES run(id),\n  created_at TEXT NOT NULL,\n  PRIMARY KEY (binding, chat_id, message_id, notification)\n);\nCREATE TABLE IF NOT EXISTS telegram_retry (\n  bot_id TEXT PRIMARY KEY,\n  next_attempt_at TEXT NOT NULL\n);\n\n-- One-time pairing codes, hashed like every other credential, consumed in\n-- one transaction with the binding they create.\nCREATE TABLE IF NOT EXISTS telegram_pairing (\n  code_hash       TEXT PRIMARY KEY,\n  approver        TEXT NOT NULL REFERENCES approver(name) ON DELETE RESTRICT,\n  approver_generation INTEGER NOT NULL,\n  created_at      TEXT NOT NULL,\n  created_by      TEXT NOT NULL,\n  expires_at      TEXT NOT NULL,\n  consumed_at     TEXT,\n  consumed_chat   TEXT,\n  consumed_user   TEXT,\n  consumed_update INTEGER\n);\n\n-- Every Telegram update this installation has applied, exactly once. The\n-- PRIMARY KEY is the idempotency: a replayed batch re-applies nothing.\nCREATE TABLE IF NOT EXISTS telegram_update (\n  update_id  INTEGER PRIMARY KEY,\n  applied_at TEXT NOT NULL,\n  result     TEXT NOT NULL\n);\n\n-- Opaque one-tap actions. callback_data carries only the random token; what\n-- the tap MEANS \u2014 which binding, decision, option, and phase \u2014 lives here,\n-- where a stolen bot token cannot read or forge it. Confirm challenges are\n-- short-lived rows in the same table, consumed exactly once.\nCREATE TABLE IF NOT EXISTS telegram_action (\n  token       TEXT PRIMARY KEY,\n  binding     INTEGER NOT NULL REFERENCES telegram_binding(id) ON DELETE RESTRICT,\n  decision    INTEGER NOT NULL REFERENCES decision(id) ON DELETE CASCADE,\n  option_id   TEXT NOT NULL,\n  phase       TEXT NOT NULL CHECK (phase IN ('choose','confirm','cancel')),\n  chat_id     TEXT NOT NULL,\n  message_id  TEXT,\n  created_at  TEXT NOT NULL,\n  expires_at  TEXT,\n  consumed_at TEXT\n);\nCREATE INDEX IF NOT EXISTS telegram_action_by_decision ON telegram_action (decision);\n\n-- v86: a flow card waiting at a \"Person decides\" zone reaches the decider on\n-- Telegram with Approve / Edit / Send back. Each button is one opaque token\n-- for one visit of one card (card, entry), placed on the message it rides so\n-- a tap on any other message proves itself stale. Edit and Send back ask\n-- for a reply to a prompt: telegram_flow_prompt names which prompt means\n-- what, so the reply becomes the new draft or the note.\nCREATE TABLE IF NOT EXISTS telegram_flow_action (\n  token       TEXT PRIMARY KEY,\n  binding     INTEGER NOT NULL REFERENCES telegram_binding(id) ON DELETE RESTRICT,\n  card        INTEGER NOT NULL REFERENCES flow_card(id),\n  entry       INTEGER NOT NULL,\n  action      TEXT NOT NULL CHECK (action IN ('approve','edit','send-back')),\n  chat_id     TEXT NOT NULL,\n  message_id  TEXT,\n  created_at  TEXT NOT NULL,\n  expires_at  TEXT NOT NULL,\n  consumed_at TEXT\n);\nCREATE INDEX IF NOT EXISTS telegram_flow_action_visit ON telegram_flow_action (card, entry);\n-- v93: a subagent's question on Telegram. One button per option (choice)\n-- and one to reply in words (choice NULL), placed on the message it rides;\n-- a reply to the prompt the Reply button sends is the answer.\nCREATE TABLE IF NOT EXISTS telegram_question_action (\n  token       TEXT PRIMARY KEY,\n  binding     INTEGER NOT NULL REFERENCES telegram_binding(id) ON DELETE RESTRICT,\n  question    INTEGER NOT NULL REFERENCES subagent_question(id),\n  choice      TEXT,\n  chat_id     TEXT NOT NULL,\n  message_id  TEXT,\n  created_at  TEXT NOT NULL,\n  expires_at  TEXT NOT NULL,\n  consumed_at TEXT\n);\nCREATE TABLE IF NOT EXISTS telegram_question_prompt (\n  chat_id     TEXT NOT NULL,\n  message_id  TEXT NOT NULL,\n  binding     INTEGER NOT NULL REFERENCES telegram_binding(id) ON DELETE RESTRICT,\n  question    INTEGER NOT NULL REFERENCES subagent_question(id),\n  created_at  TEXT NOT NULL,\n  expires_at  TEXT NOT NULL,\n  consumed_at TEXT,\n  PRIMARY KEY (chat_id, message_id)\n);\nCREATE TABLE IF NOT EXISTS telegram_flow_prompt (\n  chat_id     TEXT NOT NULL,\n  message_id  TEXT NOT NULL,\n  binding     INTEGER NOT NULL REFERENCES telegram_binding(id) ON DELETE RESTRICT,\n  card        INTEGER NOT NULL REFERENCES flow_card(id),\n  entry       INTEGER NOT NULL,\n  mode        TEXT NOT NULL CHECK (mode IN ('edit','send-back')),\n  created_at  TEXT NOT NULL,\n  expires_at  TEXT NOT NULL,\n  consumed_at TEXT,\n  PRIMARY KEY (chat_id, message_id)\n);\n\n-- Which outbound Telegram message carries which decision (v10). A free-text\n-- reply is routed through the EXACT message it replies to \u2014 never \"the\n-- latest decision\", never \"the only open one\" (Codex free-text review,\n-- finding 1). Losing the send/record race fails closed: an unrecorded\n-- message routes nothing.\nCREATE TABLE IF NOT EXISTS telegram_decision_message (\n  binding    INTEGER NOT NULL REFERENCES telegram_binding(id) ON DELETE CASCADE,\n  chat_id    TEXT NOT NULL,\n  message_id TEXT NOT NULL,\n  decision   INTEGER NOT NULL REFERENCES decision(id) ON DELETE CASCADE,\n  created_at TEXT NOT NULL,\n  PRIMARY KEY (binding, chat_id, message_id)\n);\n\n-- The free-text draft (v10): an operator's note, held immutable and\n-- expiring until a TAP commits it with the choice. One live draft per\n-- (binding, decision); a newer valid reply SUPERSEDES, never edits.\nCREATE TABLE IF NOT EXISTS telegram_note_draft (\n  id         INTEGER PRIMARY KEY AUTOINCREMENT,\n  binding    INTEGER NOT NULL REFERENCES telegram_binding(id) ON DELETE CASCADE,\n  decision   INTEGER NOT NULL REFERENCES decision(id) ON DELETE CASCADE,\n  update_id  INTEGER NOT NULL,\n  message_id TEXT NOT NULL,\n  reply_to   TEXT NOT NULL,\n  note       TEXT NOT NULL,\n  state      TEXT NOT NULL DEFAULT 'pending' CHECK (state IN ('pending','armed','superseded','consumed','discarded')),\n  created_at TEXT NOT NULL,\n  expires_at TEXT NOT NULL\n);\n\nCREATE UNIQUE INDEX IF NOT EXISTS telegram_note_draft_live\n  ON telegram_note_draft (binding, decision) WHERE state IN ('pending','armed');\n\n-- v62: the durable inbound conversation queue. An ordinary paired message\n-- becomes a row in the SAME transaction that marks its update applied, so\n-- the poll cursor never moves past text nobody holds. The row carries the\n-- exact binding, sender, update, message and the request identity the\n-- shared mate engine receipts it under; the async model turn runs OUTSIDE\n-- any transaction under a short claim, and a replay or restart finds the\n-- receipt instead of dispatching the provider again.\nCREATE TABLE IF NOT EXISTS telegram_conversation (\n  id                  INTEGER PRIMARY KEY AUTOINCREMENT,\n  binding             INTEGER NOT NULL REFERENCES telegram_binding(id) ON DELETE RESTRICT,\n  bot_id              TEXT NOT NULL,\n  chat_id             TEXT NOT NULL,\n  user_id             TEXT NOT NULL,\n  approver            TEXT NOT NULL,\n  approver_generation INTEGER NOT NULL,\n  update_id           INTEGER NOT NULL UNIQUE,\n  message_id          TEXT NOT NULL,\n  reply_to            TEXT,\n  request             TEXT NOT NULL UNIQUE,\n  text                TEXT NOT NULL,\n  context             TEXT,\n  task_id             TEXT,\n  source_run          INTEGER,\n  state               TEXT NOT NULL CHECK (state IN ('queued','running','done','failed')),\n  claim_owner         TEXT,\n  claim_expires_at    TEXT,\n  attempts            INTEGER NOT NULL DEFAULT 0,\n  next_attempt_at     TEXT,\n  session             INTEGER,\n  turn                INTEGER,\n  outcome             TEXT,\n  reply_message_id    TEXT,\n  created_at          TEXT NOT NULL,\n  started_at          TEXT,\n  finished_at         TEXT\n);\nCREATE INDEX IF NOT EXISTS telegram_conversation_queue ON telegram_conversation (bot_id, state, id);\n\n-- v62: opaque one-tap tokens for the lead's proposal cards, the same shape\n-- as telegram_action for decisions: callback_data carries only the token,\n-- and what a tap MEANS (which binding, which proposal, which phase) lives\n-- here. Consumed exactly once; an irreversible answer arms a yes/cancel\n-- pair first, exactly as a decision button does.\nCREATE TABLE IF NOT EXISTS telegram_proposal_action (\n  token       TEXT PRIMARY KEY,\n  binding     INTEGER NOT NULL REFERENCES telegram_binding(id) ON DELETE RESTRICT,\n  proposal    INTEGER NOT NULL REFERENCES lead_proposal(id) ON DELETE CASCADE,\n  phase       TEXT NOT NULL CHECK (phase IN ('confirm','dismiss','yes','cancel')),\n  chat_id     TEXT NOT NULL,\n  message_id  TEXT,\n  created_at  TEXT NOT NULL,\n  expires_at  TEXT,\n  consumed_at TEXT\n);\nCREATE INDEX IF NOT EXISTS telegram_proposal_action_by_proposal ON telegram_proposal_action (proposal);\n\n-- v63: the outbound half of a conversation, durable BEFORE any send. Once\n-- the engine's turn is answered (or recovered from its receipt), the exact\n-- reply text, split into Telegram-sized parts, and one card per pending\n-- proposal are written here in one transaction; the bridge then sends\n-- them in order under the row's claim, marking a part sent only when\n-- Telegram confirmed a message id. A crash, an outage, a rate limit or a\n-- restart resumes from the first unsent part \u2014 never another model call,\n-- proposal, task or revision. A card's buttons are minted with the part,\n-- so a resend carries the same tokens. A part whose network answer was\n-- lost is counted as uncertain: a resend may duplicate it, and the row\n-- says so instead of claiming an exactly-once Telegram cannot provide.\n-- v64: an 'image' part is one verified screenshot of one exact result,\n-- named by typed columns \u2014 task, run, artifact and the hash its record\n-- carried when the part was planned \u2014 never by JSON inside text or a\n-- keyboard, and never by bytes: every send re-reads the artifact from the\n-- evidence root and re-verifies it against these columns first. Its text\n-- is the short caption. A confirmed image message binds replies to that\n-- exact task and run, exactly as an outbox fact's message does.\nCREATE TABLE IF NOT EXISTS telegram_conversation_part (\n  conversation    INTEGER NOT NULL REFERENCES telegram_conversation(id) ON DELETE CASCADE,\n  ordinal         INTEGER NOT NULL,\n  kind            TEXT NOT NULL CHECK (kind IN ('reply','card','image')),\n  text            TEXT NOT NULL,\n  reply_to        TEXT,\n  proposal        INTEGER REFERENCES lead_proposal(id) ON DELETE SET NULL,\n  keyboard_json   TEXT,\n  state           TEXT NOT NULL CHECK (state IN ('pending','sent','dropped')),\n  message_id      TEXT,\n  attempts        INTEGER NOT NULL DEFAULT 0,\n  uncertain       INTEGER NOT NULL DEFAULT 0,\n  next_attempt_at TEXT,\n  last_error      TEXT,\n  created_at      TEXT NOT NULL,\n  sent_at         TEXT,\n  task_id         TEXT,\n  source_run      INTEGER REFERENCES run(id),\n  artifact        INTEGER,\n  sha256          TEXT,\n  PRIMARY KEY (conversation, ordinal),\n  CHECK ((state = 'sent') = (message_id IS NOT NULL)),\n  CHECK ((state = 'sent') = (sent_at IS NOT NULL)),\n  CHECK ((kind = 'image') = (task_id IS NOT NULL AND source_run IS NOT NULL AND artifact IS NOT NULL AND sha256 IS NOT NULL))\n);\n\n\n-- The bridge's poll lease and cursor, per bot. One live poller at a time;\n-- the cursor only ever moves forward, and only under a live generation.\nCREATE TABLE IF NOT EXISTS bridge_lease (\n  bot_id       TEXT PRIMARY KEY,\n  owner        TEXT NOT NULL,\n  generation   INTEGER NOT NULL,\n  cursor       INTEGER NOT NULL DEFAULT 0,\n  expires_at   TEXT NOT NULL,\n  heartbeat_at TEXT NOT NULL,\n  push_url     TEXT,\n  push_at      TEXT,\n  push_problem TEXT\n);\n-- v98: updates Telegram pushed to /hooks/telegram, kept until the bridge\n-- applies them (in update order, through the same door as polled ones).\nCREATE TABLE IF NOT EXISTS telegram_inbox (\n  update_id    INTEGER PRIMARY KEY,\n  bot_id       TEXT NOT NULL,\n  payload      TEXT NOT NULL,\n  received_at  TEXT NOT NULL\n);\n\n\nCREATE TABLE IF NOT EXISTS telegram_flow_confirm (\n  token       TEXT PRIMARY KEY,\n  binding     INTEGER NOT NULL,\n  chat_id     TEXT NOT NULL,\n  message_id  TEXT NOT NULL,\n  card        INTEGER NOT NULL,\n  entry       INTEGER NOT NULL,\n  phase       TEXT NOT NULL CHECK (phase IN ('yes','cancel')),\n  created_at  TEXT NOT NULL,\n  expires_at  TEXT NOT NULL,\n  consumed_at TEXT\n);\nCREATE INDEX IF NOT EXISTS telegram_flow_confirm_visit ON telegram_flow_confirm (card, entry);\n";
-/** Telegram's 21 old tables and the bridge's lease, children first. */
-export declare const LEGACY_TELEGRAM_TABLES: readonly ["telegram_note_draft", "telegram_decision_message", "telegram_task_message", "telegram_outbound_message", "telegram_action", "telegram_proposal_action", "telegram_flow_action", "telegram_flow_confirm", "telegram_flow_choice", "telegram_flow_prompt", "telegram_question_action", "telegram_question_prompt", "telegram_conversation_part", "telegram_conversation", "telegram_team_chat", "telegram_pairing", "telegram_update", "telegram_inbox", "telegram_retry", "telegram_digest", "telegram_binding", "bridge_lease"];
-/** Whether this database already keeps its chats in the shared tables (v116 ran, or it was made at v116 or later). */
-export declare function chatTablesShared(db: Database): boolean;
-/** Whether any of the old per-app tables is still here. */
-export declare function legacyChatTablesPresent(db: Database): boolean;
-/**
- * What is wrong with the old chat tables this database still has, before anything is changed: one that lacks a column
- * its every shape has had is not a table this build knows how to carry. Null when they are fine (or already gone).
- */
-export declare function legacyChatProblem(db: Database): string | null;
-/**
- * v116: every old chat table's rows into the shared ones, in one transaction. Each copy is one INSERT ... SELECT (no
- * row passes through this process), then every count is checked against its source, every Telegram message's words
- * against the person its binding names, and every foreign key; only then are the old tables dropped. Anything that
- * doesn't add up rolls the whole move back and the open fails, with the old tables as they were. Run again (a resumed
- * upgrade) it finds no old tables and does nothing.
- */
-export declare function convertChatTables(db: Database): {
-    copied: number;
-};

package/dist/chat-polish.d.ts

@@ -1,17 +0,0 @@
-import { type Html } from './html.js';
-import type { ChatSnapshot } from './store.js';
-/** Presentation only. These are recorded completions, not a claim that
- * work happened since the user last visited, or that every result passed. */
-export declare function completedWorkHtml(snapshot: ChatSnapshot, projectLabels: readonly string[], assignments?: Readonly<Record<string, {
-    state: string;
-}>>): Html;
-/** Keep activity truthful: the turn's recorded step count is not a
- * percentage or an invented tool phase. Billing detail stays available. */
-export declare function chatWorkingHtml(input: {
-    details: string;
-    stopForm?: Html;
-    keyed?: boolean;
-}): Html;
-/** Recorded activity is inspectable, not a row of performance badges. */
-export declare function chatActivityDetailsHtml(activity: string | null): Html;
-export declare const CHAT_POLISH_CSS = "\n  /* Quiet workspace surfaces: color signals state, not an AI aesthetic. */\n  body { background: var(--background); }\n  .chat-workspace .chat-overview, .chat-workspace .chat-plan, .chat-workspace .result-panel,\n  .chat-workspace .decide-card { background: var(--card); box-shadow: none; }\n  .chat-workspace .result-panel { border-radius: .75rem; }\n  .chat-workspace .chat-empty::before { content: none; }\n  .chat-workspace .thread .msg.mate::before { background: var(--muted); box-shadow: none; border: 0; }\n  .chat-workspace .thread .msg.op { box-shadow: none; border: 0; }\n  .chat-workspace .completion-receipt { background: var(--card); box-shadow: none; }\n  .chat-workspace .completion-receipt::after { content: none; }\n  .chat-workspace .thread { min-height: 0; }\n  .chat-workspace .chat-turn-history { margin: 1rem 0; border: 0; border-top: 1px solid var(--border); border-radius: 0; background: transparent; box-shadow: none; padding: 0; }\n  .chat-turn-history > summary { display: flex; align-items: center; gap: .75rem; min-height: 44px; cursor: pointer; font-size: .875rem; }\n  .chat-turn-history > summary .meta { margin-left: auto; }\n  .chat-turn-history .row { display: flex; flex-wrap: wrap; gap: .4rem; }\n  .chat-turn-history .row .right { float: none; margin-left: auto; }\n  .chat-workspace .task-live-summary { margin-bottom: .75rem; padding-bottom: .25rem; }\n  .chat-workspace .task-journey > details, .chat-workspace .result-feedback-history,\n  .chat-workspace .chat-limits, .chat-workspace .task-chat-agents {\n    border: 0; border-radius: 0; background: transparent; box-shadow: none; padding: 0; margin: .25rem 0;\n  }\n  .chat-workspace .task-chat-agents > summary { min-height: 44px; cursor: pointer; font-size: .8125rem; color: var(--muted-foreground); }\n  .chat-workspace .task-chat-agents p { margin: 0 0 .5rem; }\n  .chat-workspace .decide-options .decide-option { border: 0; border-top: 1px solid var(--border); border-radius: 0; background: transparent; padding: .75rem 0; }\n  .chat-workspace .chat-plan { padding: 1rem; margin-top: .5rem; }\n  .chat-workspace .result-knowledge { margin-bottom: .5rem; }\n  .chat-workspace .result-panel [data-result-view] > details { margin-block: 0; padding-block: 0; }\n  .chat-workspace .result-panel [data-result-view] > details > summary { min-height: 44px; display: flex; align-items: center; }\n  .chat-workspace .result-feedback-history > summary { min-height: 44px; }\n  .chat-activity-details { border: 0; background: transparent; box-shadow: none; border-radius: 0; padding: 0; margin: 0; }\n  .chat-activity-details > summary { min-height: 44px; display: flex; align-items: center; gap: .4rem; cursor: pointer; color: var(--muted-foreground); font-size: .75rem; }\n  .chat-activity-details > summary::after { content: '\u2304'; }\n  .chat-activity-details[open] > summary::after { transform: rotate(180deg); }\n  .chat-activity-details .chat-activity { gap: .25rem .75rem; }\n  .chat-activity-details .chat-activity span { border: 0; padding: 0; border-radius: 0; font: inherit; font-size: .75rem; }\n  .chat-workspace .chat-message-foot { justify-content: flex-start; align-items: baseline; margin-top: .25rem; }\n  .chat-activity-row { border: 0; background: transparent; box-shadow: none; padding: .5rem 0; min-height: 44px; gap: .65rem; }\n  .chat-activity-row details { flex: 1; min-width: 0; border: 0; background: transparent; padding: 0; margin: 0; box-shadow: none; }\n  .chat-activity-row summary { min-height: 44px; display: flex; align-items: center; cursor: pointer; width: fit-content; font-size: .875rem; font-weight: 550; }\n  .chat-activity-row summary::after { content: '\u2304'; margin-left: .65rem; color: var(--muted-foreground); }\n  .chat-activity-row details[open] summary::after { transform: rotate(180deg); }\n  .chat-activity-row .meta { padding-bottom: .5rem; overflow-wrap: anywhere; }\n  .activity-dot { width: 6px; height: 6px; border-radius: 50%; background: currentColor; flex: none; }\n  .task-live-summary { border-bottom: 1px solid var(--border); margin-bottom: 1rem; padding-bottom: .5rem; }\n  .task-live-summary .task-journey, .task-live-summary .task-control { border: 0; border-radius: 0; box-shadow: none; background: transparent; margin: 0; padding: .65rem 0; }\n  .task-live-summary .task-journey h2 { font-size: 1rem; }\n  .task-live-summary .agents-strip { margin: .4rem 0; }\n  .chat-decisions .chat-section-head { margin-bottom: .5rem; }\n  .chat-decisions h2 { font-size: .875rem; font-weight: 550; color: var(--muted-foreground); }\n  .decision-context summary { cursor: pointer; min-height: 44px; display: flex; align-items: center; font-size: .8125rem; color: var(--muted-foreground); }\n  .decision-context { border: 0; padding: 0; margin: 0; background: transparent; box-shadow: none; }\n  .decide-options { display: grid; gap: .5rem; }\n  .decide-options .decide-option { margin: 0; padding: .65rem .75rem; border: 1px solid var(--border); border-radius: .75rem; background: var(--background); }\n  .decide-options .decide-option .meta { display: block; margin-top: .3rem; overflow-wrap: anywhere; }\n  .decide-options .decide-option button { min-height: 44px; max-width: 100%; white-space: normal; text-align: left; }\n  .chat-completed { margin-top: 1rem; }\n  .chat-completed h3 { font-size: .8125rem; font-weight: 550; margin: 0 0 .25rem; color: var(--muted-foreground); }\n  .chat-completed-action { flex: none; font-size: .75rem; white-space: nowrap; color: var(--muted-foreground); }\n  .chat-overview .chat-overview-stat { box-shadow: none; border: 0; background: transparent; border-radius: 0; }\n  .chat-overview .chat-overview-stat + .chat-overview-stat { border-left: 1px solid var(--border); }\n  .result-panel .result-request { border-top: 1px solid var(--border); padding-top: 1rem; }\n  .result-panel .result-head h2 { color: var(--foreground); }\n  .result-panel .result-request h3 { color: var(--foreground); font-size: .875rem; text-transform: none; letter-spacing: 0; }\n  .result-panel .result-feedback-actions { display: flex; justify-content: flex-end; align-items: center; flex-wrap: wrap; gap: .5rem; }\n  .result-panel .result-feedback-actions > [data-request-changes] { order: 2; background: var(--foreground); color: var(--background); border-color: var(--foreground); box-shadow: none; }\n  .result-panel .result-feedback-actions > button { width: auto; min-height: 44px; white-space: nowrap; }\n  .result-panel .result-feedback-actions > .quiet { background: transparent; border-color: transparent; box-shadow: none; }\n  .result-panel .result-feedback-actions > button:disabled { opacity: .45; cursor: default; }\n  .result-panel .result-feedback-link { display: inline-flex; align-items: center; min-height: 44px; font-size: .8125rem; text-underline-offset: 3px; }\n  .result-panel .result-pin > summary, .result-panel .result-notes > summary, .result-panel .result-details > summary { min-height: 44px; }\n  .result-panel .diff-comment-form textarea { min-height: 80px; margin: 0; font-size: 1rem; }\n  .result-panel .result-attention { background: transparent; border: 0; border-radius: 0; box-shadow: none; padding: 0; margin: .75rem 0; color: var(--foreground); }\n  .result-panel .result-attention ul { margin: 0; padding-left: 1.15rem; }\n  .result-panel .result-attention ul:has(> li:only-child) { list-style: none; padding-left: 0; }\n  .result-panel .result-knowledge { border: 0; border-top: 1px solid var(--border); background: transparent; box-shadow: none; border-radius: 0; padding: .25rem 0; }\n  .result-panel .revision-from-comments { border: 0; background: transparent; box-shadow: none; padding: .5rem 0; }\n  .result-panel .result-pin summary { font-size: .8125rem; min-height: 44px; display: flex; align-items: center; cursor: pointer; }\n  .result-panel .diff-comment-limit { font-size: .75rem; }\n  .chat-main .chat-plan { box-shadow: none; }\n  .proposal-review-notes { margin: .5rem 0; padding-left: 1.15rem; overflow-wrap: anywhere; }\n  .proposal-review-notes li + li { margin-top: .5rem; }\n  .proposal-actions .button-link, .proposal-actions button { min-height: 44px; white-space: nowrap; }\n  .chat-stop-confirm > summary { min-height: 44px; display: flex; align-items: center; cursor: pointer; }\n  .task-chat-title-line h1, .task-main-title, .resume-target, .resume-ceremony, .proposal-task_action, .chat-stop-confirm { overflow-wrap: anywhere; }\n  .chat-main .chat-task-back { display: none; }\n  .knowledge-library .knowledge-intro { padding: .5rem 0 1.25rem; margin-bottom: 1.5rem; border-bottom: 1px solid var(--border); }\n  .knowledge-library .knowledge-instructions { line-height: 1.65; margin-bottom: .5rem; }\n  .knowledge-library .knowledge-editor summary { width: fit-content; font-size: .875rem; font-weight: 550; }\n  .knowledge-library .knowledge-editor, .knowledge-library > details { border: 0; border-bottom: 1px solid var(--border); border-radius: 0; box-shadow: none; background: transparent; padding: 0; }\n  .knowledge-library .knowledge-editor { border-bottom: 0; }\n  .knowledge-library .card { border: 0; border-bottom: 1px solid var(--border); border-radius: 0; padding: 0 0 .5rem; margin: 0; box-shadow: none; background: transparent; }\n  .knowledge-library .card[open] { padding-bottom: 1rem; }\n  .knowledge-library .card > summary { padding: .85rem 0; }\n  @media (prefers-reduced-motion: no-preference) {\n    .chat-activity-row .activity-dot { animation: quiet-activity 1.8s ease-in-out infinite; }\n    .chat-completed .chat-overview-item { transition: background-color 140ms ease; }\n    @keyframes quiet-activity { 50% { opacity: .35; } }\n  }\n  @media (max-width: 600px) {\n    .chat-workspace .result-panel { background: transparent; border-radius: 0; }\n    .chat-completed .chat-overview-item { align-items: flex-start; flex-wrap: wrap; gap: .35rem; }\n    .chat-completed .chat-overview-copy { flex-basis: 65%; }\n    .task-live-summary .task-journey { gap: .5rem; }\n  }\n";

package/dist/chat-quiet.d.ts

@@ -1,40 +0,0 @@
-import { type ProgressEntity } from "./telegram-progress.js";
-import { type PhoneTaskLink } from "./telegram-status.js";
-import { type ChatBatch, type Notification, type Store } from "./store.js";
-import { type DecideTarget } from "./chat-decide.js";
-/** `also`: more buttons after `link`, such as [Look first] beside [Merge]. `target`: the one card a chat may act on in
- * place (chat-decide.ts), when the message is about one result, plan, failure or pull request. */
-export type QuietView = {
-    text: string;
-    entities: ProgressEntity[];
-    link: PhoneTaskLink;
-    also?: PhoneTaskLink[];
-    target?: DecideTarget;
-};
-/** What still wants a person who pairs after it landed, in every chat app: an open decision or an unresolved attention
- * notice. Routine history is never replayed to a chat that just arrived (store.ts WANTED_BEFORE_PAIRING, the same rule). */
-export declare function wantedBeforePairing(row: Pick<Notification, "dedupeKey" | "pushClass" | "resolvedAt">): boolean;
-export declare function needsPerson(row: Pick<Notification, "dedupeKey" | "kind" | "pushClass" | "recipient">): boolean;
-/** A fact about one placed task: in quiet mode it lands on that task's card. */
-export declare function isTaskFact(row: Pick<Notification, "taskRef" | "taskId" | "project">): row is typeof row & {
-    taskRef: number;
-    taskId: string;
-    project: string;
-};
-/** The card's words now: one task's progress card, or one line per task when several were filed together. */
-export declare function quietCardView(store: Store, taskRefs: readonly number[], now: Date, root?: string, viewer?: string): QuietView | null;
-/** Whether this update for a person joins their two-minute batch: anything about one task that needs them,
- * except a fact that must stand alone. */
-export declare function joinsBatch(row: Pick<Notification, "dedupeKey" | "kind" | "pushClass" | "recipient" | "taskRef">): boolean;
-/** One person's update message: one task says what happened with its next step; several updates within two
- * minutes become "4 tasks finished: …" (or "3 updates: …") with one Open button. Null when none can be read. */
-export declare function finishedView(store: Store, batch: Pick<ChatBatch, "items">, now: Date, root?: string, viewer?: string): QuietView | null;
-/** This computer's local day and time, which is what a person means by "the evening". */
-export declare function localDay(now: Date): string;
-export declare function localTime(now: Date): string;
-/** One person's evening: what finished and what failed in the last day, and what waits for them now. Null when
- * nothing happened, so a quiet day sends nothing. */
-export declare function eveningDigestText(store: Store, account: string, now: Date, root?: string): string | null;
-/** Record each due evening digest once per person per local day, as one notification addressed to that person:
- * every chat they paired delivers it with the usual receipts, and the console keeps it. */
-export declare function enqueueEveningDigests(store: Store, now: Date, root?: string): number;

package/dist/chat-review.d.ts

@@ -1,51 +0,0 @@
-import type { RevisionOrigin } from "./contracts/route-results.js";
-import type { Store } from "./store.js";
-import type { VerifiedApprover } from "./principal.js";
-import { type FeedbackImage } from "./result-review.js";
-export type ReviewSnapshot = {
-    task: string;
-    root: string;
-    execution: string;
-    run: number;
-    artifact: number;
-    sha: string;
-    source: string;
-    title: string;
-    images?: FeedbackImage[];
-    notes: {
-        id: number;
-        note: string;
-        path: string | null;
-        line: number | null;
-        image?: FeedbackImage | null;
-    }[];
-};
-type Problem = {
-    ok: false;
-    message: string;
-};
-/** Read precisely the result named, never silently substitute a newer version. */
-export declare function readChatResult(store: Store, who: VerifiedApprover, evidenceRoot: string | undefined, task: string, run?: number): {
-    ok: true;
-    snapshot: ReviewSnapshot;
-} | Problem;
-export type ReviewRequest = {
-    snapshot: ReviewSnapshot;
-    operation: "note" | "revise";
-    note: string | null;
-    path: string | null;
-    line: number | null;
-    notes: number[];
-    image?: FeedbackImage | null;
-};
-export declare function reviewInputProblem(note: string | null, path: string | null, line: number | null): string | null;
-/** Chat and the result form write the same comments and call the same revision service.
- * A failed combined note+revision rolls back the note too; no half-completed action.
- */
-export declare function applyChatReview(store: Store, who: VerifiedApprover, evidenceRoot: string, request: ReviewRequest, now: Date, allowMode: boolean, origin: RevisionOrigin): {
-    ok: true;
-    taskId: string;
-    run: number;
-    said: string;
-} | Problem;
-export {};