/**
 * Port: Where pipeline configuration comes from.
 *
 * The ConfigSource abstracts configuration resolution so the pipeline
 * can be driven from different sources without changing orchestration:
 *
 * Adapters:
 * - CliConfigAdapter — Commander flags + env vars (current behavior)
 * - FileConfigAdapter — reads a JSON/YAML config file (--config flag)
 * - ContentLakeConfigAdapter (future: studio-eval-config) — GROQ query
 *
 * @see packages/eval/src/commands/pipeline-action.ts — current implementation
 * @see docs/ideas/studio-eval-config.md — future Content Lake adapter
 */
export {};
