/**
 * @file envelope-snapshots.test.ts
 *
 * Drift detection for Issue #33's CLI UX standardization. Snapshots:
 *   1. The JSON Schema returned by `vibe <cmd> --describe` for every
 *      leaf command (catches schema/option/argument drift).
 *   2. The `--dry-run --json` envelope shape for representative
 *      commands across the major groups (catches success-envelope
 *      drift — keys moved, renamed, removed).
 *
 * Why:
 * - The new `outputSuccess()` envelope (#194-#199, v0.72.0) is now load-bearing.
 *   Every agent / MCP host parses `data.X` not `X`. A regression that
 *   re-flattens or renames keys would silently break agent integrations.
 *   Snapshots make the regression visible in PR review.
 * - `--describe` is the agent's discovery channel for parameters. Drift
 *   in option descriptions / enum hints / argument shapes invalidates
 *   prompts that were written against the old schema.
 *
 * Normalization:
 * - `elapsedMs` is replaced with `<elapsedMs>` before snapshotting (it
 *   varies per run). Other fields are kept verbatim.
 * - Cost-estimate-driven `costUsd` is stable per command and not normalized.
 *
 * Maintenance:
 * - When a snapshot diff is INTENTIONAL (e.g. you renamed a key on
 *   purpose), run with `-u` (`pnpm -F @vibeframe/cli exec vitest run -u`)
 *   to update the snapshot file, then review the diff.
 * - When a snapshot diff is UNINTENTIONAL, the test names will tell
 *   you which command and which channel (--describe vs --dry-run).
 */
export {};
