/**
 * Starter Trail bundle — the 5 reference trails ship with the SDK.
 *
 * `STARTER_TRAILS` is an array of pre-parsed Trail objects suitable for handing straight to
 * `TrailLibrary.fromArray(...)`. Browser callers get them in the bundle automatically (no
 * filesystem access needed); Node callers can either use the bundle or load fresh from disk via
 * `TrailLibrary.fromDirectory()`.
 *
 * Adding a new starter trail: drop a `.trail.json` into this directory, add it to STARTER_TRAILS
 * below. The static import gives you compile-time JSON validation against the Trail type.
 */
import { type Trail } from "../trail.js";
/**
 * Pre-validated starter trails. Parsed once at module load.
 *
 * Design note: we DO NOT throw on individual trail failures here. A broken trail json should
 * not take down the entire SDK module — that cascades to every consumer (UI, CLI, MCP) and
 * makes the LLM provider classes (which have nothing to do with trails) unreachable. Instead
 * we filter out bad trails + log a warning so the issue is visible without being fatal.
 * Schema violations should be caught by the trail test suite at SDK build time.
 */
export declare const STARTER_TRAILS: Trail[];
/** Get a single starter trail by id; convenience wrapper for one-off references. */
export declare function getStarterTrail(id: string): Trail | undefined;