import type { CliAdapter } from './types.js';
/** Adapter for Pi coding-agent's native TUI (`pi`).
 *
 *  ## Type-ahead (re-enabled 2026-08; first tried b2c2ba67, reverted next day
 *  b7dfa0c0 because Pi then had NO turn boundary at all — only the screen marker
 *  `Working...` — so merging multiple busy-period inputs mis-attributed the
 *  final reply / crossed Lark cards).
 *
 *  What changed since the revert: PR #327 (2026-06-30) added Pi's per-session
 *  JSONL transcript bridge (`services/pi-transcript.ts`). Pi's `AssistantMessage`
 *  carries a `stopReason` (`@earendil-works/pi-ai`:
 *  `"stop" | "length" | "toolUse" | "error" | "aborted"`), and `drainPiTranscript`
 *  emits an `assistant_final` on every terminal stopReason (incl. empty
 *  error/aborted turns). That gives CodexBridgeQueue a per-turn user/final pair
 *  to attribute the reply for ordinary turns — enough for type-ahead.
 *
 *  Pi's Message Queue is an active-turn STEER (verified on 0.80.6 — the TUI
 *  shows "Steering: …" + "Alt+Up to edit all queued messages"): a message
 *  submitted while a turn runs is pulled into that same turn, which emits one
 *  merged final (transcript: user1 → tools → user2 → assistant_final, user2
 *  written at dequeue time). This is the identical shape Codex/Grok produce, and
 *  CodexBridgeQueue's HOL-block-drop + dequeue-time markTimeMs override attribute
 *  the single final to the newest matching Lark turn. We deliberately do NOT set
 *  `mergeQueuedInput`: each Lark message keeps its own botmux turn / card, and
 *  the steer merge is reconciled by the bridge queue rather than by pre-squashing
 *  the queue (which the revert-era code did, collapsing distinct cards).
 *
 *  ## Why NOT `reliableTurnTerminal` (type-ahead does not need it)
 *  Type-ahead is gated on `supportsTypeAhead` alone (input-gate.ts); reply
 *  attribution rides the structured-bridge allowlist (pi is in it), not this
 *  flag. `reliableTurnTerminal` is a STRONGER promise — an authoritative,
 *  always-on-disk end-of-turn boundary — that Pi cannot honestly make (verified
 *  on 0.80.6, PR #710 review):
 *    1. Pi's SessionManager writes the JSONL with short-lived `appendFileSync`
 *       (open→append→close); the process holds NO fd on the session file, even
 *       mid-turn (empirically: /proc/<pid>/fd + lsof show nothing across a whole
 *       turn). So a pid→session follow can't track `/new`/`/resume`/fork
 *       rotation, and durable meeting delivery has no reliable boundary.
 *    2. A custom tool returning `terminate:true` ends the agent right after the
 *       toolResult with the last assistant record being `toolUse` (not a
 *       terminal stopReason), and `terminate` is not persisted — so that turn
 *       has no on-disk end marker.
 *  Setting `reliableTurnTerminal` would (a) claim VC-meeting delivery eligibility
 *  Pi can't honor and (b) suppress the busy-marker idle probe Pi actually relies
 *  on, so it stays unset — keeping Pi on its proven quiescence + `Working...`
 *  busy-marker idle path. (Pi's screen `rate` verdict is NOT at risk here:
 *  `structuredRateLimitAuthoritative` gates on `claudeDataDir` /
 *  `emitsStructuredRateLimit`, neither of which Pi sets — Pi has no structured
 *  rate-limit emit, so it correctly keeps screen-scanning real 429s.)
 *
 *  ## Idle detection
 *  Pi is a pure-quiescence adapter (no `readyPattern`, no `injectsReadyHook`).
 *  Without `reliableTurnTerminal` the worker keeps the post-submit busy-marker
 *  idle probe and the reattach probe (`scheduleReattachIdleProbe`, gated on
 *  `busyPattern`), so a turn — and a reattached persistent pane with no new PTY
 *  output — is marked ready via the `Working...` marker exactly as before this
 *  change. `assistant_final` events additionally fire idle when they land.
 *  Three guards keep quiescence honest (the raw heuristic alone mis-fires):
 *    1. Startup window: the TUI renders its input box seconds before the CLI
 *       begins consuming an argv-baked first prompt (extension/model loading).
 *       The worker holds the first ready until the turn has visibly started —
 *       `Working...` seen on PTY, or the transcript's first user record
 *       (worker `spawnArgvTurnStartEvidenceSeen` gate).
 *    2. Mid-turn: pi is in STRUCTURED_BRIDGE_LIFECYCLE_BLOCKING_CLI_IDS, so a
 *       transcript-started turn without a terminal suppresses screen idle
 *       (drainPiTranscript emits terminals for stop/length-no-toolcall and the
 *       hard error/aborted edges — see pi-transcript.ts for the accepted
 *       custom-tool `terminate:true` gap).
 *    3. Post-idle: `idleToBusyPattern` flips a falsely published ready back to
 *       working when `Working...` reappears. */
export declare function createPiAdapter(pathOverride?: string): CliAdapter;
export declare const create: typeof createPiAdapter;
//# sourceMappingURL=pi.d.ts.map