#!/usr/bin/env node
/**
 * @omnify/ts CLI
 *
 * Reads omnify.yaml to resolve schemas.json input and TypeScript output paths.
 * Falls back to explicit --input / --output flags.
 *
 * Two omnify.yaml shapes are accepted:
 *
 *   1. Backend shape (legacy / source-of-truth): the schemas.json path is
 *      resolved indirectly via `connections.<default>.migrations[type=laravel].schemasPath`.
 *      The same file the omnify-go CLI reads.
 *
 *   2. Consumer shape (frontend): a top-level `input` field that accepts
 *      a local path, an http(s) URL, or an npm package specifier (e.g.
 *      `@org/pkg/schemas.json`). No connections / migrations needed —
 *      consumers don't have a database.
 *
 * Usage:
 *   omnify-ts                              # reads omnify.yaml in cwd
 *   omnify-ts --config path/to/omnify.yaml
 *   omnify-ts --input schemas.json --output ./types  # explicit override
 *   omnify-ts --frozen-lockfile             # CI mode: fail if upstream drift
 *   omnify-ts --update                      # force re-fetch remote input
 */
export {};