#!/usr/bin/env node /** * `run-evals` (DES-DEFAULT-EVALS-001 ยง7): the Tool step of the `run-evals` workflow, and a plain command. * * node dist/evals/run-cli.js [--daemon ] [--project |all] [--baseline] [--out ] * node dist/evals/run-cli.js --runs-dir (the workflow's Tool step) * * From a shell, the daemon is `--daemon`, else `$WICKED_CREW_URL`; with neither it refuses (it never guesses a port). * As the `run-evals` workflow's Tool step it calls nothing: the daemon ran the evals when it launched the run and * wrote `/$WICKED_RUN_ID/report.json`; the step reads that back and prints its summary. * * It asks the daemon to run the default evals (`POST /api/v1/testing/default-evals/run`), so the daemon's own store * is what gets scored and the report is stored where studio reads it. It prints a short plain summary, writes the * full report to `--out` when given, and exits 0 on a completed run (a regression is a finding, not a failure), * 1 when the daemon refused or could not be reached. */ import type { DefaultEvalReport } from './types.js'; export interface CliArgs { /** `null` until named: the CLI never guesses a port, since a default could reach another daemon. */ daemon: string | null; project: string | null; baseline: boolean; out: string | null; /** The workflow's mode: read `/$WICKED_RUN_ID/report.json` back instead of calling a daemon. */ runsDir: string | null; } export declare function parseArgs(argv: readonly string[], env?: NodeJS.ProcessEnv): CliArgs; /** The plain summary: one line per suite, too-few marked, then the drift keys. */ export declare function summaryLines(r: DefaultEvalReport): string[]; export declare function main(argv: readonly string[], fetchImpl?: typeof fetch, env?: NodeJS.ProcessEnv): Promise; //# sourceMappingURL=run-cli.d.ts.map