import type { ExtensionAPI } from "@earendil-works/pi-coding-agent"; /** * Pi lifecycle-end sentinel extension. * * Listens to the pi `ExtensionAPI` `agent_end` event ("Fired when an * agent loop ends") and appends an end marker to the sentinel file * specified by `PI_TMUX_END_FILE`. The `agent_start` event truncates * the sentinel, re-arming completion detection for re-steered agents. * * This is the authoritative completion signal consumed by * `PiHarness.isComplete()` and `LifecycleController`. It is distinct from * `session_shutdown` (TUI exit) so completion does NOT depend on the * TUI closing or the tmux window dying — it fires the instant the * agent puts the ball back in the user's court. * * See the `completion-sentinel` capability. * * Usage in launch command (the path is the per-agent `/end` * supplied by the harness; legacy records used `$TMPDIR/pi-tmux-end-`): * PI_TMUX_END_FILE=/end pi -e /pi-end-signal.js */ export default function (pi: ExtensionAPI): Promise; export declare function clearEndSentinel(endFile: string): void; //# sourceMappingURL=pi-end-signal.d.ts.map