/**
 * Named exit codes for the olam CLI.
 *
 * Pipelines and CI workflows depend on these to distinguish "skipped because
 * an optional feature wasn't configured" from "failed because of an actual
 * error" (both differ from exit 0 = success).
 */
/** Generic failure (default for any unhandled error path). */
export const EXIT_GENERIC_ERROR = 1;
/**
 * Skipped: PLERI integration not configured. Emitted by `olam crystallize`
 * when `PLERI_BASE_URL` (or the equivalent `pleri` config block) is absent.
 * Pipelines that script `olam crystallize` should treat exit 2 as "skipped,
 * not failed" — equivalent to exit 0 for "did the pipeline succeed?" but
 * distinguishable from "the operation actually ran."
 */
export const EXIT_PLERI_NOT_CONFIGURED = 2;
/**
 * Bootstrap pull failure (transient network / GHCR outage / arch mismatch).
 * Reserved for Phase C's `olam bootstrap` command.
 */
export const EXIT_BOOTSTRAP_PULL_FAILED = 3;
/**
 * Devbox image's `olam.protocol.versions` LABEL doesn't overlap CLI's
 * compiled-in supported list. Reserved for Phase C's protocol-version
 * handshake (Decision #14).
 */
export const EXIT_PROTOCOL_MISMATCH = 4;
/**
 * Auth-service has no eligible credential to pick (all cooled-down,
 * disabled, or expired). Used by `olam auth status` to signal "needs
 * attention" — distinct from EXIT_PLERI_NOT_CONFIGURED (= 2).
 */
export const EXIT_AUTH_NEEDS_ATTENTION = 5;
/**
 * `olam worldspec validate` failed because the worldspec violates the
 * v1 schema (one or more Zod issues surfaced). Plan AC #4 reserves a
 * worldspec-scoped range (20–29) so future worldspec commands can sub-
 * distinguish without colliding with codes 1–5 which already carry
 * CLI-wide meaning.
 *
 * `olam worldspec validate <path>`:
 *   exit 0  → worldspec valid
 *   exit 20 → schema violation (one or more issues)
 *   exit 21 → worldspec file not found / not readable
 *   exit 1  → internal error (parse crash, etc)
 */
export const EXIT_WORLDSPEC_INVALID = 20;
export const EXIT_WORLDSPEC_FILE_NOT_FOUND = 21;
/**
 * `olam worldspec compile` failed to resolve image content-digests
 * (Docker unreachable / image not present locally). Distinct from
 * EXIT_GENERIC_ERROR=1 so CI pipelines can fail-fast on lockfile-
 * digest gaps. Decision #13 invariant: lockfile MUST record digests
 * for fail-fast at world-spawn. MEDIUM-fix (A6 CP3 audit 2026-05-09):
 * digest resolution failure now exits 23 by default; `--allow-pending-
 * digests` opts INTO the soft-warning path for dry-run / no-Docker CI.
 */
export const EXIT_DIGEST_UNRESOLVED = 23;
/**
 * `olam worldspec init` refused to overwrite an existing default.yaml
 * without `--force`. Distinct from EXIT_GENERIC_ERROR=1 (internal/parse
 * crash) so pipelines can distinguish "user forgot --force" from
 * "something is broken." A3 CP3 audit MEDIUM-fix 2026-05-09.
 */
export const EXIT_WORLDSPEC_EXISTS = 22;
//# sourceMappingURL=exit-codes.js.map