/**
 * `agent-hook` CLI entry point for canonical event emission.
 *
 * Flow:
 *   1. Parse argv → event-name + adapter.
 *   2. Read stdin → adapter payload (JSON or empty).
 *   3. Find coord root (walk up for .harnery/).
 *   4. Resolve instance_id (env → payload → pid-map walk).
 *   5. Map event-name → canonical event_type.
 *   6. Build event data from payload + resolvers (intent, transcript scan).
 *   7. Record the normalized observation in the canonical V3 ledger.
 *   8. (Still also writes a debug breadcrumb to .harnery/debug/ for visibility.)
 *
 * Phase 2 ship criterion: confirms parser correctness across thousands of
 * real events without affecting behavior. Always exits 0. Failures land in
 * `.harnery/debug/agent-hook.errors.ndjson` for audit but never break the
 * adapter flow.
 */
export {};
//# sourceMappingURL=cli.d.ts.map