/**
 * Format an agent's terminal status into the body of an
 * `orca:agent-completion` message for the parent LLM's context.
 *
 * Spec §5.8 — Enhanced completion. The body is what the parent LLM
 * actually reads on its next turn (via the in-process completion queue
 * drained by the agents extension's `context` hook / idle-poll
 * sendUserMessage path).
 *
 * Why the function lives in its own module instead of inline at the
 * call site: it's reused by the SDK spawner (in-process enqueue), and
 * RPC/tmux notify-socket handlers will reuse it when they're wired up,
 * so the format stays consistent across isolation modes.
 */
import type { AgentStatusFile } from "@pi-orca/core";
/** Custom-entry type per spec §5.8. Reserved for future on-disk writes. */
export declare const AGENT_COMPLETION_CUSTOM_TYPE = "orca:agent-completion";
/**
 * Build the LLM-context body per spec §5.8. One-line prefix (so a
 * downstream reader can identify the completion without parsing labels)
 * followed by the agent's result text.
 */
export declare function formatAgentCompletionBody(status: AgentStatusFile): string;
//# sourceMappingURL=completion-notify.d.ts.map