toolroll 0.9.103 → 0.9.105

package/dist/task-status.d.ts

@@ -1,324 +0,0 @@
-import { type Html } from "./html.js";
-import type { AssignmentSnapshot } from "./assignment.js";
-import { type NeedAction, type NeedContext, type NeedKey, type WaitKey } from "./needs-you.js";
-export type { NeedKey, WaitKey } from "./needs-you.js";
-/** A cancelled task with a successor reads "Replaced by <id>" everywhere, never "Cancelled". */
-export declare const replacedWords: (successor: string) => string;
-/** Waiting: a reason no person can act on, worded as what it waits for (needs-you.ts). */
-export declare const HEADLINES: readonly ["Queued", "Planning", "Needs you", "Waiting", "Building", "Ready for review", "Complete", "Failed", "Stopped"];
-export type Headline = (typeof HEADLINES)[number];
-export type HeadlineTone = "neutral" | "live" | "attention" | "ready" | "success" | "danger";
-export declare const HEADLINE_TONE: Readonly<Record<Headline, HeadlineTone>>;
-/** The project's own checks and the pull request's CI are two different things, never one word (Checks beside CI). */
-export declare const CHECKS_LABEL = "Project checks";
-export declare const PR_CI_LABEL = "PR CI";
-/** The one verb for opening a saved result, on every surface. */
-export declare const OPEN_RESULT = "Open result";
-/** A machine-run check under way (a prepared candidate: no agent runs), on every surface that has no richer words. */
-export declare const MACHINE_CHECK_RUNNING = "Running the check on the prepared version.";
-export type DetailKey = "checks" | "pull-request" | "requirements" | "evidence";
-/** The row's small icon: the only coloured part of a detail. `failed` is red
- * and only ever appears under the Failed headline; `note` is ink, with a caution mark. */
-export type DetailMark = "ok" | "running" | "none" | "note" | "failed";
-export type StatusAction = {
-    label: string;
-    href: string | null;
-};
-export type StatusDetail = {
-    key: DetailKey;
-    label: string;
-    text: string;
-    mark: DetailMark;
-    href: string | null;
-    action: StatusAction | null;
-    why: string | null;
-};
-/** `need`: what a Needs you asks for and the one action that resolves it; null under every other headline. */
-export type TaskStatus = {
-    headline: Headline;
-    tone: HeadlineTone;
-    sentence: string;
-    details: StatusDetail[];
-    primaryAction: StatusAction | null;
-    why: string[];
-    need?: {
-        key: NeedKey;
-        action: NeedAction;
-    } | null;
-    /** The approved check as the Checks row shows it (`approvedCheckStateOf`): the road reads this, never the row's words. */
-    check?: ApprovedCheckState | null;
-};
-/** `reviewing`: the one automatic review (build-review.ts) is reading a finished build; it reads Building, not a headline of its own. */
-export type TaskStage = "queued" | "planning" | "needs-you" | "waiting" | "building" | "checking" | "reviewing" | "finished" | "complete" | "failed" | "stopped";
-export type ChecksFact = {
-    status: "passed" | "failed" | "running" | "not-run" | "unavailable";
-    exitCode: number | null;
-    head: string | null;
-    /** The check level that ran (check-levels.ts). Off never reads Ready; a quick pass says so. */
-    level?: "quick" | "full" | "off" | null;
-    /** A follow-up check (Run checks) waiting or running on this commit. */
-    running?: "quick" | "full" | null;
-    /** A batch check (batch-checks.ts): waiting for its batch, or how it was checked. */
-    batch?: ChecksBatch | null;
-    /** Off: the passing full release check whose commit contains this one (release-coverage.ts), read at read time. */
-    release?: {
-        run: number;
-        head: string;
-    } | null;
-    /** Why it can't be read, when that is the project's check command approved again since it ran. */
-    cause?: "command-changed" | null;
-};
-/** What checks Off leaves for a release: `pending` until a passing full release check contains the commit, then
- * `covered`. `running`: a check is waiting for its batch or running on this commit. */
-export type ReleaseState = "pending" | "covered" | "running";
-export declare const CHECKED_AT_RELEASE = "Checked at release";
-export declare function releaseStateOf(checks: Pick<ChecksFact, "status" | "level" | "release"> | null | undefined): ReleaseState | undefined;
-/** How the project check stands for requirements that rest on it, read now: `covered` once a check passed on this
- * commit (its own, a follow-up, or a release check containing it), `pending` while checks Off wait for a release. */
-export declare function checkBackingOf(checks: Pick<ChecksFact, "status" | "level" | "release" | "running" | "batch"> | null | undefined): ReleaseState | undefined;
-/**
- * Did the approved check pass for this result? The ONE answer the status headline and sentence, the Project checks
- * row, the road's Checks step and the result page all read, so none of them can say "passed" while another says the
- * check couldn't be read. Two records speak to it: the machine verdict sealed when the build finished, and the saved
- * check receipt read now (with any follow-up check on the same commit). Fail closed: the check passed only when the
- * receipt read now says so. A verdict that recorded a pass whose receipt is missing, says nothing ran, or can't be
- * read is unreadable; a verdict that recorded a failure stays failed unless a later check on the same commit passed.
- * `checks` undefined or null: nothing was read. Returns the check as every surface shows it (null: nothing to show).
- */
-export declare function approvedCheckOf(verdict: string | null | undefined, reasons: readonly string[], checks: ChecksFact | null | undefined): ChecksFact | null;
-/** How the approved check reads, in one word every surface shares (from `approvedCheckOf`'s answer): `running` while a
- * check is underway on the commit, else what it recorded. `unreadable`: it couldn't be read or the records disagree. */
-export type ApprovedCheckState = "passed" | "failed" | "running" | "not-run" | "off" | "unreadable";
-export declare function approvedCheckStateOf(checks: Pick<ChecksFact, "status" | "level" | "release" | "running" | "batch"> | null | undefined): ApprovedCheckState | null;
-/** A saved check that can't be read, in the words every surface uses. */
-export declare const CHECK_UNREADABLE = "The check result couldn't be read.";
-export declare const CHECK_UNREADABLE_ASK = "The check result couldn't be read. Run checks on it, or open the result to see why.";
-/** A saved check whose files are intact but whose command was approved again since it ran. */
-export declare const CHECK_COMMAND_CHANGED = "The check command changed since this check; run checks again.";
-/** What stands between a finished result and Complete (`completionBlockersOf`): each with the exact next step. */
-export type CompletionBlocker = {
-    key: "check-failed" | "check-missing" | "criteria" | "high";
-    message: string;
-};
-/** `waiting`: the result waits to be checked with others. Otherwise how its check ran: `together` on the
- * temporary batch commit `tested` with `peers`; `split` (its batch failed), `conflict` or `alone` on its own commit. */
-export type ChecksBatch = {
-    state: "waiting" | "together" | "split" | "conflict" | "alone";
-    tested: string | null;
-    peers: string[];
-};
-/** "T2", "T2 and T3", "T2, T3 and 2 more": short enough for one line. The full list is on the result. */
-export declare function peerWords(peers: readonly string[], shown?: number): string;
-/** "Checked together with T2 on 1a2b3c4": every surface says a shared check the same way, naming the commit it tested. */
-export declare function checkedTogetherWords(batch: ChecksBatch): string | null;
-export type PullRequestFact = {
-    state: "none" | "opening" | "open" | "merged" | "closed" | "failed";
-    number: number | null;
-    url: string | null;
-    ci: "running" | "passing" | "failing" | null;
-    error: string | null;
-    /** GitHub's compare page for the pushed branch: where a person opens it by hand. */
-    compareUrl?: string | null;
-    /** Who merged it and its merge commit, shown on request. */
-    note?: string | null;
-};
-export type TaskStatusFacts = {
-    stage: TaskStage;
-    /** Needs you: what a person is asked for (needs-you.ts). The sentence names it. */
-    need?: NeedKey;
-    /** Waiting: what the work waits for when no person can act. */
-    wait?: WaitKey;
-    /** The build or agent a need's sentence names. */
-    needContext?: NeedContext;
-    /** The recorded reason in plain words, when the stage has one. */
-    reason?: string | null;
-    /** A research report rather than a code change. */
-    report?: boolean;
-    /** The machine runs this task's check on a prepared candidate; no agent runs (machine-check.ts). Building then says
-     * the check is running, never "an agent". */
-    machine?: boolean;
-    checks?: ChecksFact | null;
-    pullRequest?: PullRequestFact | null;
-    /** `unverified`: the report is refuted, so no requirement counts as met however it was marked. `missed`: the ones it
-     * failed or left unanswered. `atRelease`: checks Off, waiting for a release check. `unshown`: a required screenshot
-     * is missing. `ask`: what a person is asked to look at first (a requirement they check, or a missing screenshot). */
-    requirements?: {
-        met: number;
-        total: number;
-        yours: number;
-        missed?: number;
-        unverified?: boolean;
-        atRelease?: number;
-        unshown?: number;
-        ask?: string | null;
-    } | null;
-    /** A person accepted this result's proof: their own check and a recorded exception need nothing more. */
-    accepted?: boolean;
-    /** What refuses Complete (`completionBlockersOf`); the first one is the sentence when it holds the result back. */
-    blockers?: readonly CompletionBlocker[];
-    evidence?: {
-        shortened: number;
-        missing: number;
-        damaged: number;
-    } | null;
-    completedBy?: string | null;
-    /** Marked complete by Toolroll because its work landed: why, in a few words ("its pull request merged"). */
-    landed?: string | null;
-    action?: StatusAction | null;
-    /** Where a row's one action leads: the result (and its Checks tab), the task's pull request, Run checks. */
-    links?: {
-        result?: string | null;
-        checks?: string | null;
-        pullRequest?: string | null;
-        runChecks?: string | null;
-    };
-    /** Exact technical reasons, shown only on request. */
-    why?: readonly string[];
-    /** The person's lead took this on (lead-voice.ts): "on-it" reads "<name> is on it" and needs nobody; "lapsed"
-     * (two hours without a lead act) is back with the person, and says so. */
-    lead?: "on-it" | "lapsed" | null;
-    /** What the person calls their lead (Settings → Lead); "Lead" when unnamed. */
-    leadName?: string;
-};
-export declare function headlineOf(facts: Pick<TaskStatusFacts, "stage" | "checks" | "report" | "requirements" | "accepted" | "blockers">): Headline;
-/** What the lead's claim says, in place of "waits for you" (lead-voice.ts). */
-export declare const leadOnIt: (name?: string) => string;
-export declare const leadLapsed: (name?: string) => string;
-/** The one status every surface shows (console list, task and result pages, CLI, chat, phone, `status`). */
-export declare function statusOf(facts: TaskStatusFacts): TaskStatus;
-/** The name most surfaces already import. */
-export declare const taskStatusOf: typeof statusOf;
-export declare function plainReasonOf(stage: TaskStage, code: string, detail: string | null | undefined): string | null;
-/** Every dispatch or work-index code, as the stage it means (needs-you.ts CODE_READING, the one table). Unknown
- * codes that wait on a person stay Needs you; everything else waits in the queue. */
-export declare function stageOfCode(code: string, options?: {
-    needsPerson?: boolean;
-    planning?: boolean;
-    operatorHold?: boolean;
-}): {
-    stage: TaskStage;
-    need?: TaskStatusFacts["need"];
-    wait?: WaitKey;
-};
-/** The pull request as the task page's follower reports it, or the bare publication row. */
-export declare function pullRequestFactOf(publication: {
-    state: string;
-    prNumber?: number | null;
-    prUrl: string | null;
-    remoteState: string | null;
-    lastCheckState?: string | null;
-    lastError?: string | null;
-    merged?: boolean;
-    githubRepo?: string;
-    base?: string;
-    head?: string;
-} | null): PullRequestFact | null;
-/** The assignment's stage. The work status, when the caller read one, names
- * the exact reason (a running planner, a pause, a failed attempt, a sign-in). */
-export declare function assignmentStageOf(assignment: Pick<AssignmentSnapshot, "state" | "primaryAction"> & {
-    review?: AssignmentSnapshot["review"];
-    need?: AssignmentSnapshot["need"];
-}, work?: {
-    token: string;
-    views?: readonly string[];
-} | null, planning?: boolean): {
-    stage: TaskStage;
-    need?: TaskStatusFacts["need"];
-    wait?: WaitKey;
-};
-type RequirementRow = {
-    id?: string;
-    statement?: string;
-    state: string;
-    requiredEvidence?: readonly string[];
-    answered?: readonly {
-        kind: string;
-    }[];
-    detail?: readonly string[];
-    assessment?: {
-        evidenceState?: string;
-        detail?: readonly string[];
-    } | undefined;
-    review?: unknown;
-};
-/** One requirement's state in words: the card's Requirements row and the Checks tab read this one source, so they
- * can't disagree. A refuted report verifies none of its requirements, so each reads Unverified, as the card does.
- * With checks Off, a requirement that waits only on the check reads Checked at release, then Met once a passing full
- * release check contains the commit. */
-export type RequirementWord = "Met" | "You check" | "Not shown yet" | "Checked at release" | "Waiting for checks" | "Not met" | "Unverified";
-export declare function requirementWordOf(row: RequirementRow, verdict?: string | null, release?: ReleaseState): RequirementWord;
-/** Requirements from the stored matrix: met, the ones only a person confirms, and the total. */
-export declare function requirementsOf(matrix: readonly RequirementRow[] | null | undefined, release?: ReleaseState): NonNullable<TaskStatusFacts["requirements"]> | null;
-/** What refuses Complete, for `task complete`, the console and chat completion and deploy-candidate alike: a failed
- * check; a required check that is missing (checks deliberately Off are not missing: they are checked at release);
- * an unresolved requirement (a person's own check is theirs to give by completing; a recorded acceptance resolves
- * the rest); an unresolved HIGH review finding. A release check that covers the commit counts as passed. */
-export declare function completionBlockersOf(f: {
-    report: boolean;
-    checks: Pick<ChecksFact, "status" | "exitCode" | "level" | "release" | "running" | "batch" | "cause"> | null;
-    checkRequired: boolean;
-    matrix: readonly RequirementRow[] | null | undefined;
-    verdict: string | null | undefined;
-    accepted: boolean;
-    high: number;
-}): CompletionBlocker[];
-/** A refuted report verifies none of its requirements, whatever it marked met (a person's acceptance doesn't change that). */
-export declare function unverifiedWhenRefuted(requirements: NonNullable<TaskStatusFacts["requirements"]> | null, verdict: string | null | undefined): NonNullable<TaskStatusFacts["requirements"]> | null;
-/** Saved evidence health from the receipt's artifact list and its caveats. */
-export declare function evidenceOf(receipt: AssignmentSnapshot["receipt"], problems?: readonly string[]): NonNullable<TaskStatusFacts["evidence"]> | null;
-/** A saved check reading as the shared fact (head, level, a follow-up running, a batch, release coverage). */
-export declare function checksFactOf(checks: NonNullable<AssignmentSnapshot["receipt"]>["checks"], head: string | null): ChecksFact;
-/** A receipt's approved check, as every surface reads it (`approvedCheckOf` over its verdict and its saved check). */
-export declare function receiptChecksOf(receipt: NonNullable<AssignmentSnapshot["receipt"]>): ChecksFact | null;
-/** The status facts of one assignment, as every surface reads them. */
-export declare function assignmentStatusFacts(assignment: AssignmentSnapshot, options?: {
-    work?: {
-        token: string;
-        views?: readonly string[];
-        detail?: string;
-    } | null;
-    planning?: boolean;
-    pullRequest?: PullRequestFact | null;
-    action?: StatusAction | null;
-    links?: TaskStatusFacts["links"];
-    evidence?: TaskStatusFacts["evidence"];
-    why?: readonly string[];
-}): TaskStatusFacts;
-/** The legacy work tone each headline wears where a surface still keys off StatusTone. */
-export declare function workToneOf(headline: Headline): "attention" | "problem" | "live" | "ready" | "done" | "muted";
-/** One plain-text line per detail for chat cards: an icon, the label, the words. */
-export declare function statusDetailLines(status: TaskStatus): string[];
-/** The headline's emoji for chat cards (colour is never the only signal: the words follow). */
-export declare function headlineEmoji(headline: Headline): string;
-export declare const statusIconSvg: (mark: DetailMark) => Html;
-/** The detail rows as server HTML: quiet rows, colour only on the icon. */
-export declare function statusDetailsHtml(status: TaskStatus): Html;
-/** The status card's fold of exact reasons: "More", never a third thing called Details. */
-export declare const STATUS_MORE = "More";
-/** The technical reasons, one tap away. */
-export declare function statusWhyHtml(status: TaskStatus, extra?: readonly string[], diagnostics?: readonly {
-    token: string;
-    label: string;
-    detail: string;
-}[]): Html;
-/** Shared CSS for the server-rendered status: neutral rows, coloured icons. */
-export declare const TASK_STATUS_CSS = ".status-headline{display:flex;align-items:center;gap:.6rem;margin:0;font-size:1.125rem;font-weight:600;color:var(--foreground)}.status-headline i{width:.625rem;height:.625rem;border-radius:999px;flex-shrink:0;background:var(--muted-foreground)}[data-headline-tone=live] .status-headline i{background:var(--so-info,#0d74ce)}[data-headline-tone=attention] .status-headline i{background:var(--so-attention,var(--attention))}[data-headline-tone=ready] .status-headline i{background:transparent;box-shadow:inset 0 0 0 2px var(--so-success,#218358)}[data-headline-tone=success] .status-headline i{background:var(--so-success,#218358)}[data-headline-tone=danger] .status-headline i{background:var(--so-danger,#c4320a)}.status-sentence{margin:.35rem 0 0;color:var(--muted-foreground)}.status-details{list-style:none;margin:.75rem 0 0;padding:.25rem 0 0;border-top:1px solid var(--so-line,var(--border))}.status-detail{display:grid;grid-template-columns:14px 7.5rem minmax(0,1fr);align-items:center;gap:.6rem;padding:.4rem 0;font-size:.8125rem;color:var(--foreground)}.status-detail .status-icon{align-self:center;color:var(--muted-foreground)}.status-detail--ok .status-icon{color:var(--so-success,#218358)}.status-detail--running .status-icon{color:var(--so-info,#0d74ce)}.status-detail--note .status-icon{color:var(--so-ink)}.status-detail--failed .status-icon{color:var(--so-danger,#c4320a)}.status-detail-label{color:var(--muted-foreground)}.status-detail-text{display:flex;flex-wrap:wrap;align-items:baseline;gap:0 .6rem;min-width:0;overflow-wrap:anywhere}.status-detail-text a{color:inherit}.status-detail-act{font-weight:600;white-space:nowrap}.status-detail--note .status-detail-act{color:var(--so-ink)}@media(max-width:480px){.status-detail{grid-template-columns:14px 6.5rem minmax(0,1fr);min-height:2.75rem;padding:.25rem 0}.status-detail-text a{display:inline-block;padding:.75rem 0;margin:-.75rem 0}}.status-why{border:0;padding:0;margin:.25rem 0 0;background:transparent;box-shadow:none}.status-why>summary{cursor:pointer;min-height:2.75rem;display:list-item;align-content:center;font-size:.8125rem;color:var(--muted-foreground)}.status-why p{margin:.25rem 0 .5rem}.receipt-note{display:flex;align-items:center;gap:.45rem;font-size:.8125rem;color:var(--foreground)}.receipt-note .status-icon{color:var(--so-ink)}";
-/** A dispatch diagnosis as its stage, for the phone and CLI reads that hold
- * no assignment. A done task is Complete once a person marked its result;
- * a refuted result whose project check failed is Failed. */
-export declare function stageOfDispatch(d: {
-    code: string;
-    condition: string;
-    action: string | null;
-    role?: string | null;
-    detail?: string;
-}, options?: {
-    completed?: boolean;
-}): {
-    stage: TaskStage;
-    need?: TaskStatusFacts["need"];
-    wait?: WaitKey;
-};
-/** The demo runs no checks: a Checks row that would offer to run one (or open one that never ran) says so instead. */
-export declare const DEMO_CHECKS = "Can't run in the demo";
-export declare function demoChecksOf(status: TaskStatus): TaskStatus;

package/dist/task-text.d.ts

@@ -1,31 +0,0 @@
-export declare const TASK_TEXT_LIMITS: {
-    readonly title: 200;
-    readonly text: 8000;
-    readonly textBytes: 32000;
-};
-export type TaskTextRefusal = {
-    ok: false;
-    reason: "bad-title" | "bad-goal";
-    message: string;
-};
-export declare function validateScopeText(fields: {
-    goal?: string;
-    outOfScope?: string | null;
-    touches?: readonly string[];
-}): {
-    ok: false;
-    reason: "bad-goal" | "bad-out-of-scope" | "bad-touches";
-    message: string;
-} | null;
-export declare function validateTaskText(fields: {
-    title: string;
-    goal?: string;
-    outOfScope?: string | null;
-    touches?: readonly string[];
-}): TaskTextRefusal | null;
-/**
- * A title that fits: words longer than the title limit are cut at the last whole word that fits, with an ellipsis,
- * never mid-word (one unbroken word longer than half the limit is the only thing cut inside a word). Whitespace runs
- * read as one space. Text within the limit is returned as it is.
- */
-export declare function titleWithin(text: string, max?: number): string;

package/dist/team-chat-authorization.d.ts

@@ -1,11 +0,0 @@
-import type { Store, ChatConfig } from './store.js';
-import type { TeamActor, TeamChatAuthorization, TeamSnapshot } from './team-contract.js';
-export type TeamChatProvider = {
-    config: ChatConfig;
-    key: string | null;
-};
-export type TeamChatProviderResolver = () => TeamChatProvider | null;
-/** Subscription-only surfaces can resolve current terms from saved settings.
- * Direct API callers must supply their live key; a stored grant is never proof of it. */
-export declare function subscriptionTeamChatProvider(store: Store): TeamChatProvider | null;
-export declare function teamChatAuthorization(store: Store, actor: TeamActor, conversation: Pick<NonNullable<TeamSnapshot['selected']>, 'id' | 'threadId' | 'projects'> | null, live: TeamChatProvider | null): TeamChatAuthorization;

package/dist/team-contract.d.ts

@@ -1,103 +0,0 @@
-import type { WorkIndexPage } from './work-index.js';
-import type { BrowserActionCard } from './browser-workspace.js';
-import type { Principal } from './operate-remote.js';
-/** Shared central-team transport contract. Requests never establish actor identity. */
-export type TeamActor = {
-    name: string;
-    generation: number;
-    /** Set when an `so_` API token signed in: its scope and project limit narrow every check, never widen one. */
-    principal?: Principal;
-};
-export type TeamRole = 'viewer' | 'contributor' | 'manager';
-export type TeamLead = {
-    id: string;
-    name: string;
-    instructions: string;
-    projects: string[];
-    revision: number;
-    status: 'active' | 'paused';
-    createdBy: string;
-};
-export type TeamConversation = {
-    id: string;
-    leadId: string;
-    title: string;
-    visibility: 'private' | 'team';
-    projects: string[];
-    revision: number;
-    threadId: number;
-    createdBy: string;
-    follow: boolean;
-};
-export type TeamParticipant = {
-    account: string;
-    role: TeamRole;
-    active: boolean;
-};
-export type TeamMessage = {
-    id: number;
-    author: string;
-    role: 'operator' | 'assistant';
-    text: string;
-    status: 'queued' | 'running' | 'answered' | 'failed' | 'cancelled' | 'uncertain';
-    revision: number;
-    createdAt: string;
-    requestId: string | null;
-    turnId: number | null;
-    error: string | null;
-};
-export type TeamChatAuthorization = {
-    enabled: boolean;
-    provider: string | null;
-    model: string | null;
-    dailyTurns: number;
-    weeklyCeilingUsd: number | null;
-    conversationCeilingUsd: number | null;
-    termsDigest: string;
-    waitingReason?: string;
-};
-/** Browser cards extend the existing CLI summary; both refer to the same saved proposal. */
-export type TeamProposal = {
-    id: number;
-    turnId: number;
-    title: string;
-    state: string;
-    href: string;
-    card?: BrowserActionCard;
-};
-export type TeamSnapshot = {
-    leads: TeamLead[];
-    conversations: TeamConversation[];
-    selected: TeamConversation | null;
-    participants: TeamParticipant[];
-    messages: TeamMessage[];
-    canManage: boolean;
-    canSend: boolean;
-    canCreateLead?: boolean;
-    cursor: number;
-    truncated: boolean;
-    projects: string[];
-    accounts: string[];
-    chatAuthorization?: TeamChatAuthorization;
-    tasks?: WorkIndexPage;
-    proposals?: TeamProposal[];
-};
-export declare const TEAM_OPERATIONS: readonly ['list', 'show', 'create-lead', 'update-lead', 'create-conversation', 'member', 'send', 'edit', 'withdraw', 'read', 'authorize', 'follow', 'stop', 'transfer'];
-export type TeamOperation = typeof TEAM_OPERATIONS[number];
-/** Whether each operation writes anything (a read receipt included). Exhaustive, so a new operation can't default to read. */
-export declare const TEAM_MUTATIONS: Readonly<Record<TeamOperation, boolean>>;
-/** Whether this actor may run `operation`: a read-scope token never writes. */
-export declare const teamScopeAllows: (actor: TeamActor, operation: TeamOperation) => boolean;
-export type TeamRequest = {
-    operation: TeamOperation;
-    args: Record<string, unknown>;
-};
-export type TeamResponse = {
-    version: 1;
-    ok: boolean;
-    code: string;
-    message: string;
-    result?: unknown;
-    snapshot?: TeamSnapshot;
-};
-export type TeamExecute = (actor: TeamActor, request: TeamRequest) => Promise<TeamResponse>;

package/dist/team-http.d.ts

@@ -1,25 +0,0 @@
-import type { IncomingMessage, ServerResponse } from 'node:http';
-import { type TeamActor, type TeamExecute } from './team-contract.js';
-import { type Admission } from './request-budget.js';
-export declare const TEAM_REQUEST_BYTES: number;
-/** How long a password bearer's proof stands on a long live team stream (GET /live?room=team) before its password is
- * checked again. The account, its revocation and its credential generation are still rechecked on every signal. */
-export declare const TEAM_PASSWORD_REVERIFY_MS: number;
-/** Account role belongs to HTTP authentication; API tokens carry their own scope. */
-export type TeamHttpActor = TeamActor & {
-    role?: 'approver' | 'viewer';
-};
-export type TeamHttpOptions = {
-    authenticate: (request: IncomingMessage) => TeamHttpActor | null | Promise<TeamHttpActor | null>;
-    /** Recheck the original credential/session and current account, without extending idle expiry. */
-    revalidate: (request: IncomingMessage, actor: TeamActor) => boolean;
-    authorizeMutation: (request: IncomingMessage, actor: TeamActor) => boolean;
-    execute: TeamExecute;
-    /** Source admission before credential verification. */
-    admit?: (request: IncomingMessage) => Admission;
-    /** Proved account/token admission, before reading the body or executing any operation. */
-    admitAuthenticated?: (request: IncomingMessage, actor: TeamActor) => Admission;
-};
-/** Authenticated browser and remote CLI share one operation boundary. Live
- * updates come from GET /live?room=team (server/live.ts). */
-export declare function handleTeamHttp(request: IncomingMessage, response: ServerResponse, options: TeamHttpOptions): Promise<boolean>;

package/dist/team-leads.d.ts

@@ -1,85 +0,0 @@
-import type { Store } from './store.js';
-import { type TeamActor, type TeamConversation, type TeamLead, type TeamRequest, type TeamResponse, type TeamRole, type TeamSnapshot } from './team-contract.js';
-export type TeamAccess = {
-    conversation: TeamConversation;
-    lead: TeamLead;
-    role: TeamRole;
-};
-export type TeamClaim = {
-    conversationId: string;
-    leadId: string;
-    threadId: number;
-    messageId: number;
-    messageRevision: number;
-    generation: number;
-    runner: string;
-    actor: TeamActor;
-    text: string;
-    projects: string[];
-    instructions: string;
-    requestId: string;
-};
-/** One central database owns audiences and queued turns. No model or provider calls here. */
-export declare class TeamLeads {
-    readonly store: Store;
-    readonly enrolled: () => readonly string[];
-    constructor(store: Store, enrolled: () => readonly string[]);
-    private get db();
-    /** The account as this actor may use it now. An API token's principal narrows it: a read token acts as a viewer, and a
-     * project-limited token sees only its projects. Every role and project check below reads this, never the raw row. */
-    private account;
-    /** Whether the actor may use `repo` now: their account's access, narrowed by any token limit. */
-    private reaches;
-    private leadRow;
-    private leadProjects;
-    private leadOf;
-    private leadAccess;
-    private projects;
-    private conversationOf;
-    access(actor: TeamActor, conversationId: string, required?: TeamRole): TeamAccess;
-    private event;
-    /** Permission recheck and a small indexed cursor query; it never rebuilds chat history. */
-    cursor(actor: TeamActor, conversationId?: string): number | null;
-    snapshot(actor: TeamActor, conversationId?: string, leadId?: string): TeamSnapshot;
-    execute(actor: TeamActor, request: TeamRequest, now?: Date): TeamResponse;
-    private perform;
-    private revokeMemberSessions;
-    private memberRevisions;
-    private authorStillAllowed;
-    claimNext(runner: string, now?: Date, eligible?: (candidate: {
-        actor: TeamActor;
-        conversationId: string;
-        threadId: number;
-        messageId: number;
-    }) => boolean): TeamClaim | null;
-    private claimed;
-    current(claim: TeamClaim): boolean;
-    bindTurn(claim: TeamClaim, turnId: number): boolean;
-    finish(claim: TeamClaim, result: {
-        status: 'answered' | 'failed' | 'uncertain' | 'cancelled';
-        text?: string;
-        error?: string;
-        turnId?: number;
-    }, now?: Date): boolean;
-    /** A pre-admission refusal saves a waiting reason. Admitted work is never requeued. */
-    defer(claim: TeamClaim, error: string, now?: Date): boolean;
-    /** Reconcile only recorded terminal receipts; never infer success from time or rerun a turn. */
-    reconcileFinished(now?: Date): number;
-    deliveryUncertain(turnId: number): boolean;
-    activeRunners(): string[];
-    /** Called only after the runtime proves this runner has stopped. Never repeats work. */
-    recover(runner: string, now?: Date): number;
-    followGrants(): {
-        actor: TeamActor;
-        conversation: TeamConversation;
-        lead: TeamLead;
-    }[];
-    taskOwner(taskId: string): {
-        leadId: string;
-        revision: number;
-        conversationId: string | null;
-    } | null;
-    /** Attach newly filed work in its original admission transaction. Never steals an existing owner. */
-    recordTaskOwner(taskId: string, leadId: string, conversationId: string | null, actor: TeamActor, now?: Date): boolean;
-    private transfer;
-}

package/dist/team-runtime.d.ts

@@ -1,25 +0,0 @@
-import type { Store } from './store.js';
-import type { WorkspaceRevision } from './workspace-revision.js';
-import { TeamLeads } from './team-leads.js';
-import { type TeamActor, type TeamExecute } from './team-contract.js';
-import { type LeadTurnInput } from './lead.js';
-import { type TeamChatProviderResolver } from './team-chat-authorization.js';
-export type TeamRuntimeOptions = {
-    store: Store;
-    repos: () => readonly string[];
-    evidenceRoot: string;
-    provider: TeamChatProviderResolver;
-    subscriptionRunner?: LeadTurnInput['subscriptionRunner'];
-    fetcher?: typeof fetch;
-    clock?: () => Date;
-    capacity?: number;
-    workspaceRevision?: WorkspaceRevision;
-};
-export declare function createTeamRuntime(options: TeamRuntimeOptions): {
-    execute: TeamExecute;
-    start: () => void;
-    close: () => Promise<void>;
-    pass: () => Promise<void>;
-    cursor: (actor: TeamActor, conversationId?: string) => number | null;
-    domain: TeamLeads;
-};

package/dist/team-ui.d.ts

@@ -1,4 +0,0 @@
-import { type Html } from './html.js';
-import type { TeamSnapshot } from './team-contract.js';
-/** Readable fallback uses the same admitted projection as the interactive UI. */
-export declare function teamWorkspaceHtml(snapshot: TeamSnapshot): Html;

package/dist/team-updates.d.ts

@@ -1,8 +0,0 @@
-/** Shared conversations consume the existing saved status stream. No task
- * scans, model calls, or execution retries happen in this delivery layer. */
-import type { Store } from './store.js';
-import { TeamLeads } from './team-leads.js';
-import type { TeamActor } from './team-contract.js';
-export declare const teamUpdateCursor: (conversation: string) => string;
-export declare function startTeamUpdates(store: Store, conversation: string, now: Date): void;
-export declare function deliverTeamUpdates(store: Store, domain: TeamLeads, authorized: (actor: TeamActor, conversation: string) => boolean, now: Date): number;