/** * Session-side mention close (2026-09). * * The hub's AgentMention row is the deterministic answer to "has this agent * already been asked, and did it answer?". The DAEMON claims a mention before * spawning a session (that is what stops a replayed wake from opening a second * session on an answered question); the SESSION closes it here once it has * finished with it. * * The id arrives as `TS_MENTION_ID` in the session's identity env, so every * mention surface (chat, document, board, task comment) closes the same way * without each command growing its own argument. * * Closing is best-effort and idempotent on the hub: if this call fails, the * mention stays `triggered` and therefore visible in the pending list for a * human, rather than being silently re-answered later. */ import type { TeamshareApi } from '../api'; export declare function sessionMentionId(): string | null; /** * EVERY mention this session owes an answer for, oldest first (2026-10). * * `TS_MENTION_IDS` is a comma-separated list; `TS_MENTION_ID` stays supported as * the single-id shorthand, so an older spawn (or an operator exporting the env by * hand) keeps working untouched. * * Why a list: a lane coalesces, so one run can legitimately owe answers to * several people - "5 mentions while it runs" is one wake carrying five * obligations. Closing only the newest left the other four rows `triggered` and * invisible, which is the same silence the list exists to remove. The single id * is included when present but not in the list, and the result is de-duplicated, * so a spawn that sets both is still closed exactly once each. */ export declare function sessionMentionIds(): string[]; /** * Close the mention this session was working, if any. * * @param outcome `answered` when a reply was actually delivered; `handled` for a * session that finished the work but posted nothing the user needed to see * (the row is still closed - the agent did engage with the mention). */ export declare function closeSessionMention(api: TeamshareApi, agentId: string, opts?: { outcome?: 'answered' | 'handled'; answerMessageId?: string | null; log?: (m: string) => void; }): Promise;