@phnx-labs/agents-cli 1.22.119 → 1.22.121

package/dist/lib/feed-broadcast.js

@@ -1,49 +1,13 @@
-/**
- * Fan an `agents feed post` out to the systems the operator actually watches.
- *
- * A post is already durable — it lands in the append-only activity log and shows
- * up in `agents feed --filter updates`. But an operator who is away from every
- * terminal never sees it, and the tracker that owns the work (a Linear ticket,
- * a GitHub issue) hears nothing at all. So a post can also be mirrored outward.
- *
- * Sinks are **argv templates from config**, never hardcoded integrations. This
- * CLI ships under FSL-1.1-Apache-2.0 and must not depend on one person's tracker or messaging
- * stack; declaring `[linear, update, "{ticket}", --comment, "{text}"]` in
- * `agents.yaml` keeps the coupling in the operator's config where it belongs,
- * and lets someone else point the same mechanism at `jira`, `gh issue comment`,
- * or a webhook script.
- *
- * Two rules decide whether a sink runs, both derived from the post itself:
- *
- *   - **Level.** `minLevel: important` keeps a sink for the posts worth
- *     interrupting someone over, so a routine "CI green" does not buzz a phone.
- *   - **Placeholders.** A template that references `{ticket}` is skipped when no
- *     ticket is known. The template declares what it needs; nothing has to
- *     restate it as a flag, and a sink can never fire with a hole in its argv.
- *
- * Delivery is best-effort and reported: a sink that fails prints a warning and
- * the post still stands. Losing a mirror must never cost the operator the post.
- *
- * A second sink shape (RUSH-2123) delivers **in-process** through the same
- * channel-provider registry `agents send` uses (`channel:` instead of
- * `command:`) — no spawn, no argv templating. `channel: owner` is the address
- * alias that expands to `notify.owner.{channel,to}`, matching `agents send --to owner`.
- * When the operator has never written a `feed.broadcast` block at all, an
- * important-level post falls back to that owner address implicitly
- * ({@link effectiveBroadcastConfig}) rather than reaching nobody — see that
- * function's doc for why this was a silent failure before.
- */
 import { spawnSync } from 'child_process';
 import { isOwnerAlias, readOwnerDest, resolveSendEnvelope, deliverEnvelope } from './channels/send.js';
 import { lookupTransport } from './channels/resolve.js';
 import { registerBuiltinProviders } from './channels/providers/index.js';
 import { sendToOwner } from './notify.js';
-import { linearIssueUrl, linearIssueKeys } from './session/linear.js';
+import { linearIssueUrl, linearIssueKeys } from '@phnx-labs/sessions-cli/reader';
 import { isValidMailboxId } from './mailbox.js';
 import { forwardOwnerNotifyToPeer } from './channels/owner-forward.js';
 import { sinkMessageFormat } from './sink-format.js';
 const LEVEL_RANK = { milestone: 0, important: 1 };
-/** Parse a `--level` value; anything unrecognized is a usage error, not a default. */
 export function parseFeedPostLevel(raw) {
     const v = (raw ?? '').trim().toLowerCase();
     if (!v || v === 'milestone')
@@ -52,28 +16,12 @@ export function parseFeedPostLevel(raw) {
         return 'important';
     throw new Error(`Unknown --level '${raw}'. Use milestone or important.`);
 }
-/**
- * Map an open block onto the broadcast context, so a block reaches the same sinks
- * a post does instead of dying in the ledger.
- *
- * The `text` is the ask itself, front-loaded — a notification banner shows roughly
- * two lines, and a phone message is scanned, not read. `focus` carries the literal
- * command that unblocks it, so the message the operator receives contains the one
- * action they have to take rather than making them go find the session.
- *
- * Level is always `important`: a block is by definition an agent that has stopped
- * making progress, so there is no per-block level flag to get wrong.
- */
 export function blockBroadcastContext(block, extras = {}) {
     const ask = block.questions?.[0]?.text?.trim() || 'agent is blocked';
     const links = [block.pr].filter((l) => !!l && /^https?:\/\//i.test(l));
-    // The answer choices + the safe default are what make the phone message
-    // actionable: the operator sees the options and what happens if they do not
-    // reply, instead of a `agents focus <id>` CLI command they cannot run from a phone.
     const options = (block.questions?.[0]?.options ?? [])
         .map((o) => o?.label?.trim())
         .filter((l) => !!l);
-    // Prefer explicit title/body from the feed post; fall back to the ask as body.
     const title = extras.title?.trim() || undefined;
     const text = extras.body?.trim() || ask;
     return {
@@ -89,9 +37,6 @@ export function blockBroadcastContext(block, extras = {}) {
         blockId: block.blockId,
         class: block.blockClass,
         cost: block.costOfDelay,
-        // Short id: `agents focus` matches on a prefix, and a full uuid in a phone
-        // message is noise. Kept for a `{focus}` sink; the human message no longer
-        // shows it (a CLI command is unusable from a phone).
         focus: `agents focus ${block.sessionId.slice(0, 8)}`,
         ...(options.length ? { options } : {}),
         ...(block.safeDefault ? { safeDefault: block.safeDefault } : {}),
@@ -99,17 +44,6 @@ export function blockBroadcastContext(block, extras = {}) {
         ...(links.length ? { links } : {}),
     };
 }
-/**
- * Why a declared block reached nobody, or undefined when it got through.
- *
- * Pure so the fail-loud contract is testable without driving the CLI — the
- * original version lived inline in the command action and was consequently
- * never covered, which is how a `--json` early-return quietly bypassed it.
- *
- * Only a TOTAL failure counts. One sink failing among several is a warning, not
- * an error: the channels are redundant by design, and a dead `rush` login must
- * not mask a delivered desktop notification.
- */
 export function blockDeliveryFailure(blocked, outcomes) {
     if (!blocked)
         return undefined;
@@ -123,10 +57,6 @@ export function blockDeliveryFailure(blocked, outcomes) {
     return undefined;
 }
 const PLACEHOLDER = /\{([a-z_]+)\}/g;
-/**
- * Short host label for a phone line — strip user@ and domain so
- * `muqsit@mac-mini.tailnet.ts.net` reads as `mac-mini`.
- */
 function shortHost(host) {
     if (!host?.trim())
         return undefined;
@@ -139,7 +69,6 @@ function shortHost(host) {
         h = h.slice(0, dot);
     return h || undefined;
 }
-/** First 8 hex chars of a session id for the footer (readable, not a full uuid). */
 function shortSessionChunk(session) {
     if (!session?.trim())
         return undefined;
@@ -147,31 +76,12 @@ function shortSessionChunk(session) {
     const chunk = hex.replace(/[^a-f0-9]/g, '').slice(0, 8);
     return chunk || undefined;
 }
-/**
- * Tap-to-view link for the session behind a post: the addressable console page
- * ({@link https://prix.dev/console/sessions/<id>}, prix/web). The footer already
- * carries a short session crumb for disambiguation; this rides the link trail so
- * the owner can open the full transcript straight from an iMessage broadcast
- * instead of hunting for it in the console.
- *
- * Accepts any real, path-safe session id — a Claude/Codex UUID *and* a native
- * `ses_…` id from OpenCode or another harness. The console shard uploader
- * (`traces/sync.ts`) syncs sessions with no harness filter, so all of them are
- * addressable; a UUID-only gate would silently drop the link for every non-Claude
- * harness (the whole point of the link). Reject only an id that could not resolve:
- * one with a path separator (URL-unsafe, via {@link isValidMailboxId}) or the bare
- * 8-char footer crumb (a truncated id that would 404).
- */
 function sessionConsoleUrl(session) {
     const id = session?.trim();
     if (!id || !isValidMailboxId(id) || /^[0-9a-f]{8}$/i.test(id))
         return undefined;
     return `https://prix.dev/console/sessions/${id}`;
 }
-/**
- * Scrub em/en dashes from outbound phone copy (house rule + iMessage readability).
- * Collapses whitespace; does not invent meaning.
- */
 function scrubOutboundDashes(text) {
     return text
         .replace(/\u2014/g, ' - ')
@@ -181,27 +91,12 @@ function scrubOutboundDashes(text) {
         .replace(/[ \t]{2,}/g, ' ')
         .trim();
 }
-/** Slack mrkdwn labeled link: `<url|label>` renders as blue `label` text. */
 function slackLink(url, label) {
     return `<${url}|${label}>`;
 }
-/**
- * The provider a channel name actually delivers through — the same
- * `notify.transports` remap `lookupTransport` applies at delivery — so the format
- * decision and the delivery agree on what Slack is. Identity when no mapping
- * exists (or no `meta`), matching the default name-identity transport rule.
- */
 function resolveSinkProvider(channel, meta) {
     return meta?.notify?.transports?.[channel] ?? channel;
 }
-/**
- * Replace each real Linear key the text NAMES with a Slack labeled link to its
- * issue — `PHNX-3689` → `<https://linear.app/getrush/issue/PHNX-3689|PHNX-3689>`
- * — so the key itself turns blue in place (no trailing URL line). Plain format,
- * or a key the workspace can't resolve, or a denylisted unit string, is left as
- * the bare key. `linearIssueKeys` is the same canonical detector the trail used,
- * so mrkdwn linkifies exactly the keys plain leaves as text.
- */
 function linkifyKeys(text, format) {
     if (format !== 'mrkdwn' || !text)
         return text;
@@ -214,19 +109,6 @@ function linkifyKeys(text, format) {
     }
     return out;
 }
-/**
- * Footer like "Sent from my iPhone" — who posted, a session crumb, which box.
- *
- *   Sent from grok/a02da0e2 on mac-mini
- *
- * Agent name first; session chunk for disambiguation when many groks run;
- * host last. Skip the uninformative default label `agent`.
- *
- * In `mrkdwn` the crumb (`agent/short`) becomes a Slack labeled link to the
- * session's console page, so the human sentence reads identically while the
- * crumb turns blue and taps through (PHNX-3698). `plain` keeps the bare sentence
- * — it can't render a labeled link and must not dump the URL.
- */
 function composeBroadcastFooter(ctx, format = 'plain') {
     const agent = ctx.agent?.trim();
     const agentLabel = agent && agent !== 'agent' ? agent : undefined;
@@ -239,7 +121,6 @@ function composeBroadcastFooter(ctx, format = 'plain') {
         who = agentLabel;
     else if (session)
         who = session;
-    // The crumb is only a link when the session resolves to a real console page.
     const consoleUrl = who ? sessionConsoleUrl(ctx.session) : undefined;
     if (who && format === 'mrkdwn' && consoleUrl)
         who = slackLink(consoleUrl, who);
@@ -251,36 +132,6 @@ function composeBroadcastFooter(ctx, format = 'plain') {
         return `Sent from host ${host}`;
     return undefined;
 }
-/**
- * Human-facing body for a messaging sink (`{message}`).
- *
- * ```
- * Title in a few words
- *
- * Body of what happened or the ask.
- * Options: publish / wait          (blocks with choices)
- * Default in 15 min: wait          (blocks with a safe default)
- *
- * Sent from grok/a02da0e2 on mac-mini
- * https://…                        (optional attach URL)
- * ```
- *
- * Title first (scannable subject). Blank line. Body. Then the phone-actionable
- * choices + default (a block that has stopped for the human), then footer
- * provenance. No `agents focus <id>` line: a CLI command is unusable from a phone,
- * so the safe default is the fallback and the message carries it. Prefer `{message}`
- * over bare `{text}` in messaging sinks.
- */
-/**
- * The phone copy is a text, not a report. A long body reaches the owner's phone
- * as an unreadable wall, and the `feed post` forwarding path is where that has to
- * be shaped: every sink (owner alias, in-process `channel:`, spawned `command:`)
- * funnels through {@link composeBroadcastMessage}, which is the only seam a shell
- * hook cannot reach. Keep the title (the scannable headline) and cap the BODY to a
- * short excerpt, marking the cut with a plain "(full in feed)" — NOT a CLI command
- * (unusable from a phone, see the note on composeBroadcastMessage). Nothing is
- * lost: this shapes only the outbound sink text; the full post stays in the feed.
- */
 const PHONE_BODY_MAX_CHARS = 500;
 const PHONE_BODY_MAX_LINES = 8;
 function truncateBroadcastBody(body) {
@@ -304,18 +155,9 @@ function truncateBroadcastBody(body) {
 export function composeBroadcastMessage(ctx, format = 'plain') {
     const title = scrubOutboundDashes(ctx.title ?? '');
     const body = truncateBroadcastBody(scrubOutboundDashes(ctx.text ?? ''));
-    // Title preferred; if an older post has no title, body alone still sends.
-    // A `TEAM-N` key the human typed is dead text on a phone — in `mrkdwn` the key
-    // itself becomes a Slack labeled link in place, so nothing rides a trailing
-    // naked URL line; `plain` leaves the bare key (iMessage can't render a label,
-    // and dumping the URL is worse than leaving it — PHNX-3698).
     const head = linkifyKeys(title || body, format);
     const mid = title && body && title !== body ? linkifyKeys(body, format) : undefined;
     const footer = composeBroadcastFooter(ctx, format);
-    // The action block: the one thing the operator can act on from a phone. Show the
-    // choices, then what happens if they do not answer. Deliberately NOT a CLI command
-    // (`agents focus <id>` is unusable from a phone) -- the safe default is the real
-    // fallback, so a block meant for a phone should always carry one.
     const choices = ctx.options?.length
         ? `Options: ${ctx.options.map((o) => scrubOutboundDashes(o)).join(' / ')}`
         : undefined;
@@ -329,31 +171,21 @@ export function composeBroadcastMessage(ctx, format = 'plain') {
     if (head)
         parts.push(head);
     if (mid) {
-        // Blank line between subject and body (title, then space, then message).
         parts.push('');
         parts.push(mid);
     }
     if (action) {
-        // The choices/default hug the ask under a blank line so they read as the reply.
         if (parts.length)
             parts.push('');
         parts.push(action);
     }
     if (footer) {
-        // Blank line before the "Sent from" footer (iPhone "Sent from my iPhone" spacing).
-        // The crumb/ticket links are inline (footer + prose) — never a trailing URL line.
         if (parts.length)
             parts.push('');
         parts.push(footer);
     }
     return parts.join('\n').trim();
 }
-/**
- * The values a template may reference, resolved once per post. `format` decides
- * how `{message}` surfaces its links — Slack `mrkdwn` (labeled links) vs `plain`
- * (the human sentence, no URLs). The scalar `{ticket_url}`/`{links}` vars are the
- * raw URLs a custom `message:` template can place itself, so they are unaffected.
- */
 function templateVars(ctx, format = 'plain') {
     return {
         title: ctx.title,
@@ -375,12 +207,6 @@ function templateVars(ctx, format = 'plain') {
         default: ctx.safeDefault,
     };
 }
-/**
- * Substitute `{placeholder}` tokens in an argv template. Returns undefined when
- * the template needs a value this post does not have — the sink is then skipped
- * rather than run with an empty argument, which is how a `linear update --comment`
- * would otherwise comment on nothing.
- */
 export function renderSinkArgv(template, ctx) {
     const vars = templateVars(ctx);
     const argv = [];
@@ -400,12 +226,6 @@ export function renderSinkArgv(template, ctx) {
     }
     return argv.length > 0 ? argv : undefined;
 }
-/**
- * Render one channel-message template with the same fail-closed placeholder
- * contract as argv. `format` (Slack `mrkdwn` vs `plain`) flows into the shared
- * `{message}` var so a Slack sink gets labeled links and an iMessage/owner sink
- * gets the plain sentence.
- */
 export function renderSinkMessage(template, ctx, format = 'plain') {
     const vars = templateVars(ctx, format);
     let missing = false;
@@ -435,18 +255,6 @@ export function renderSinkMessage(template, ctx, format = 'plain') {
         .join('\n');
     return text || undefined;
 }
-/**
- * Which sinks this post reaches, in config order. Pure — the dry-run listing and
- * the real fan-out plan through here, so what `--dry-run` shows is what runs.
- *
- * A `channel:` sink is gated by the same `minLevel` rule as a `command:` sink —
- * one level check for both shapes, so a dry-run plan is truthful regardless of
- * which shape an operator's sink uses.
- *
- * `meta` is used only to resolve a channel name to its real provider for the
- * mrkdwn/plain format decision (`notify.transports`), the same map delivery uses;
- * it is optional so a test can plan without a config snapshot (identity mapping).
- */
 export function planFeedBroadcast(config, ctx, meta) {
     if (!config)
         return [];
@@ -459,22 +267,8 @@ export function planFeedBroadcast(config, ctx, meta) {
             continue;
         const channel = sink.channel?.trim();
         if (channel) {
-            // The owner alias resolves its recipient from notify.owner at delivery
-            // time; any other channel name needs an explicit recipient now, or the
-            // sink can never fire with a hole in it (same contract as a missing argv
-            // placeholder below).
             if (!isOwnerAlias(channel) && !sink.to?.trim())
                 continue;
-            // Slack renders labeled links; every other channel (iMessage, telegram,
-            // discord, mailbox, desktop) stays plain (PHNX-3698). A DIRECT channel sink
-            // has one known provider, so its format is resolved here. The OWNER ALIAS
-            // fans out to every channel in owner.policy.normal — each with its OWN
-            // provider — so it can't pick one format now: it carries the ctx + template
-            // and re-renders per destination inside the owner fan-out (runChannelSink →
-            // sendToOwner), so the Slack destination turns blue while a sibling iMessage
-            // copy stays plain. The plain body computed here is the dry-run/fallback
-            // default. Keying on the resolved provider (not the raw name) matches what
-            // delivery does.
             const owner = isOwnerAlias(channel);
             const template = sink.message ?? '{message}';
             const provider = owner ? channel : resolveSinkProvider(channel, meta);
@@ -499,25 +293,6 @@ export function planFeedBroadcast(config, ctx, meta) {
     }
     return planned;
 }
-/**
- * The effective sink config for a post: the operator's `feed.broadcast`, or —
- * when that is unset or empty — an implicit fallback straight to
- * `notify.owner`, for a post worth interrupting someone over.
- *
- * Before this, `broadcastPostedEvent`/`broadcastBlock` returned early the
- * moment `feed.broadcast` was empty, even when `notify.owner` was fully
- * configured — so the common case (an operator who set up owner notifications
- * but never wrote a `feed.broadcast` block) produced a `--blocked` post that
- * looked recorded and reached nobody. `agents send --to owner` already treats
- * `notify.owner` as the default human destination; this makes an important
- * feed post/block use that same default instead of requiring a second,
- * redundant config block that says the same thing.
- *
- * The fallback only fires for `important` — a routine `milestone` post stays
- * record-only, matching the `minLevel` contract every declared sink already
- * follows. An operator-declared `feed.broadcast` (any non-empty config)
- * always wins outright; the fallback never layers on top of it.
- */
 export function effectiveBroadcastConfig(config, level, meta) {
     if (config && Object.keys(config).length > 0)
         return config;
@@ -527,30 +302,7 @@ export function effectiveBroadcastConfig(config, level, meta) {
         return undefined;
     return { owner: { channel: 'owner' } };
 }
-/** Sink name for the ephemeral local banner added by `feed post --notify`. */
 export const DESKTOP_NOTIFY_SINK = 'notify';
-/**
- * Add a local desktop-banner sink when `feed post --notify` is set — the same
- * `notifyDesktop` banner `run --notify` raises, but for an authored post.
- *
- * `--notify` is a per-post opt-in that ADDS the local banner on top of whatever
- * `feed.broadcast`/owner delivery already runs; it never replaces a configured
- * sink. It carries no `minLevel`, so it fires for any level — a quiet milestone
- * banner on this box does not touch the phone the way an `important` post does.
- * And it routes through the `desktop` channel provider exactly like every other
- * `channel:` sink, so it appears in the outcomes and the `--json` payload rather
- * than a parallel code path the reporting cannot see.
- *
- * The desktop banner is inherently local — `notifyDesktop` reaches whoever is at
- * THIS machine — so a post authored on a headless box notifies that box (a no-op
- * with a stated reason where no notifier exists, per the desktop provider),
- * never the operator's Mac. That is the same locality `run --notify` has; the
- * phone hop stays the job of an `important`-level owner/broadcast sink.
- *
- * The banner is added under `DESKTOP_NOTIFY_SINK`, or the first free
- * `notify-2`/`notify-3`/… when the operator already declared a sink by that
- * name — so `--notify` can never silently overwrite a configured sink; both fire.
- */
 export function withDesktopNotify(config, notify) {
     if (!notify)
         return config;
@@ -575,33 +327,11 @@ function runCommandSink(name, argv, timeoutMs) {
     }
     return { name, ok: true };
 }
-/**
- * Deliver one `channel:` sink through the real provider registry —
- * `resolveSendEnvelope` reuses `agents send --to owner`'s owner-alias expansion, and
- * `deliverEnvelope` is the same seam `agents send` calls. A bad channel name
- * is checked with `lookupTransport` (the non-throwing lookup) BEFORE handing
- * off to `deliverEnvelope`: that function's own resolution `die()`s on an
- * unregistered provider, which is the right answer for an interactive `agents
- * send` typo but would take the whole broadcast fan-out down with it here —
- * one misconfigured sink must report a failure, not kill the process running
- * every other sink.
- */
 async function runChannelSink(sink, meta) {
     const name = sink.name;
-    // Registration is idempotent and normally happens inside deliverEnvelope();
-    // it has to happen before the lookupTransport pre-check below too, or the
-    // very first channel sink in a process would report "no channel provider"
-    // for a name that is, in fact, registered.
     registerBuiltinProviders();
     const owner = isOwnerAlias(sink.channel);
     if (owner) {
-        // Re-render the body PER owner destination so a Slack channel in the policy
-        // gets mrkdwn labeled links while iMessage stays plain (PHNX-3698). The
-        // fan-out (sendToOwner) resolves each destination's provider and asks this
-        // composer for the matching format. renderSinkMessage is fail-closed on a
-        // missing placeholder — the plan already dropped the sink if the template
-        // couldn't fill, so here it always resolves; `?? sink.text` is a belt-and-
-        // braces guard, never the normal path.
         const composeForFormat = sink.ctx
             ? (format) => renderSinkMessage(sink.messageTemplate ?? '{message}', sink.ctx, format) ?? sink.text ?? ''
             : undefined;
@@ -622,23 +352,11 @@ async function runChannelSink(sink, meta) {
     const result = await deliverEnvelope(resolved.envelope, meta);
     if (result.ok)
         return { name, ok: true };
-    // Explicit rush-backed channel sinks need the same cross-device handoff as
-    // the owner alias. Linux workers do not carry the macOS Keychain-bound Rush
-    // transport, but feed posts originate on those workers routinely. Keep the
-    // destination explicit so the peer delivers exactly this sink once instead
-    // of expanding the owner's multi-channel policy.
     const forwarded = await forwardOwnerNotifyToPeer(resolved.envelope.text, resolved.envelope.channel, resolved.envelope.to, meta);
     if (forwarded?.ok)
         return { name, ok: true };
     return { name, ok: false, error: result.error };
 }
-/**
- * Run the planned sinks. A `command:` sink is a direct spawn with a bounded
- * lifetime; a `channel:` sink delivers in-process. Either way a sink that
- * fails or is not installed/registered is reported, never thrown — the post
- * is already written and must not be undone by a mirror that could not be
- * reached.
- */
 export async function runFeedBroadcast(planned, meta, timeoutMs = 20_000) {
     const outcomes = [];
     for (const sink of planned) {

package/dist/lib/feed-outcome.d.ts

@@ -1,80 +1,38 @@
 import { type OpenBlock } from './feed/feed.js';
 type OutcomeKind = 'ticket' | 'pr' | 'worktree' | 'unassigned';
-/** Stable attribution of a block (or agent) to one deliverable. */
 export interface OutcomeRef {
-    /** Map/JSON key, e.g. `ticket:RUSH-1125`, `pr:#534`, `worktree:headless-secrets`, `unassigned`. */
     key: string;
     kind: OutcomeKind;
-    /** Human header label, e.g. `RUSH-1125`, `PR#534`, `headless-secrets`, `Unassigned`. */
     label: string;
 }
-/**
- * Signals used to derive an outcome. All optional — callers pass whatever they
- * already know (block fields, session meta, free-text questions).
- */
 interface OutcomeSignals {
     ticket?: string | null;
     pr?: string | null;
     worktreeSlug?: string | null;
-    /** Branch name — scanned for `rush-1125`-style ticket slugs. */
     branch?: string | null;
-    /** Epic / team label when no ticket/PR/worktree is known. */
     epic?: string | null;
-    /** Free text (question headers + bodies) scanned for ticket/PR refs. */
     text?: string | null;
 }
-/**
- * Normalize a PR ref.
- * - Full GitHub URL → `owner/repo#N` (repo identity included)
- * - Bare `#123` / `PR#123` → `#123` (no repo known)
- */
 export declare function normalizePrRef(raw: string | null | undefined): string | undefined;
-/** Canonical ticket id (uppercase team key). */
 export declare function normalizeTicketRef(raw: string | null | undefined): string | undefined;
-/**
- * Derive the single outcome a block/agent belongs to.
- * Exactly one outcome per call — never ambiguous, never empty.
- */
 export declare function deriveOutcome(signals: OutcomeSignals): OutcomeRef;
-/** Outcome for a stored open block (uses stamped fields + question text). */
 export declare function outcomeForBlock(block: OpenBlock): OutcomeRef;
-/** Per-outcome rollup used by the default `agents feed` view. */
 export interface OutcomeGroup {
     outcome: OutcomeRef;
     blocks: OpenBlock[];
     counts: {
-        /** Distinct mailbox ids under this outcome. */
         agents: number;
-        /** Still open: unanswered and not hard-parked. */
         open: number;
         answered: number;
         parked: number;
     };
 }
-/**
- * Collapse blocks under their outcome. Order: needs-you outcomes first
- * (open count desc), then by label. Unassigned always last among ties of 0 open.
- */
 export declare function groupBlocksByOutcome(blocks: OpenBlock[]): OutcomeGroup[];
-/**
- * Stamp each block with its derived outcome for JSON consumers.
- * Does not mutate the input records.
- */
 export declare function stampBlockOutcomes(blocks: OpenBlock[]): Array<OpenBlock & {
     outcome: OutcomeRef;
 }>;
-/**
- * True when every still-open block under the outcome asks the same question
- * (same cluster of header+text). Fan-out answers are only safe when this holds
- * — otherwise the operator must pick a specific agent.
- */
 export declare function isUnambiguousOutcomeAnswer(group: OutcomeGroup): boolean;
-/** Still-open blocks under an outcome (candidates for a fan-out reply). */
 export declare function openBlocksForOutcome(group: OutcomeGroup): OpenBlock[];
-/**
- * Lightweight session signals used to fill missing ticket/PR/worktree on a
- * block at list time (the publish hook may not have had them yet).
- */
 export interface SessionOutcomeHint {
     sessionId?: string | null;
     agentId?: string | null;
@@ -89,14 +47,6 @@ export interface SessionOutcomeHint {
     origin?: 'cli' | 'routine' | null;
     routineName?: string | null;
 }
-/**
- * Overlay session meta onto a block when the block itself is missing ticket/PR/
- * worktree. Never overwrites a field the block already carries.
- */
 export declare function enrichBlockFromSession(block: OpenBlock, hint: SessionOutcomeHint): OpenBlock;
-/**
- * Build a mailboxId → session-hint index and enrich every block. Pure.
- * Matching order: mailboxId, then sessionId, then agentId.
- */
 export declare function enrichBlocksFromSessions(blocks: OpenBlock[], sessions: SessionOutcomeHint[]): OpenBlock[];
 export {};