@ultimat3/cli 22.2.2 → 22.3.0

package/src/verify-run.ts

@@ -17,16 +17,18 @@ import type { StepOutcome, VerifyContext, VerifyStep } from './verify-step';
  * Run every step, never bailing early: an agent fixing three things at once needs all
  * three findings from one run, not one per round-trip.
  *
- * `ctx.only` narrows the list to one step. The narrowing lives HERE rather than in `cmd-verify.ts`
- * so that every caller of the runner — the command, `x build`, the MCP host — gets the banner and
- * the `--json` flag with it, instead of one of them filtering a list quietly.
+ * `ctx.only` narrows the list to the steps it names, kept in declared order. The narrowing lives
+ * HERE rather than in `cmd-verify.ts` so that every caller of the runner — the command, `x build`,
+ * the MCP host — gets the banner and the `--json` flag with it, instead of one of them filtering a
+ * list quietly.
  */
 export async function runVerify(
   steps: readonly VerifyStep[],
   ctx: VerifyContext,
 ): Promise<CommandResult> {
   const floor = await readVerifyFloor(ctx.root);
-  const selected = ctx.only === undefined ? steps : steps.filter((step) => step.name === ctx.only);
+  const only = onlyList(ctx.only);
+  const selected = only === undefined ? steps : steps.filter((step) => only.includes(step.name));
   const byName = new Map<string, StepResult>();
   const began = performance.now();
   // The static steps wait for the serial suites and then run BESIDE them — only when `live` is in
@@ -75,7 +77,7 @@ export async function runVerify(
     // Rendered through the catalog like every other summary this file emits; the machine marker
     // is `data.notAGateRun` below. It was a bare `NOT A GATE RUN` constant, which put one
     // user-facing string outside `messages.ts` for a fact `--json` was already carrying twice.
-    summary: ctx.only === undefined ? summary : msg('cli.verify.notAGateRun', { summary }),
+    summary: only === undefined ? summary : msg('cli.verify.notAGateRun', { summary }),
     steps: results,
     // `skipped` is a list beside `failed` and not a count, because the two answer the same kind of
     // question — *which* steps, not how many — and a caller ratcheting on coverage needs the names.
@@ -85,13 +87,18 @@ export async function runVerify(
       durationMs: totalMs,
       // A BOOLEAN beside the banner, so a reader of `--json` never has to substring-match a
       // summary line to learn that this run checked one thing.
-      ...(ctx.only === undefined ? {} : { notAGateRun: true, only: ctx.only }),
+      // `only` is always the LIST, in declared order — one name is a list of one.
+      ...(only === undefined ? {} : { notAGateRun: true, only: [...only] }),
     },
     // The step's own status: one step, so `failedSteps` is that step and nothing else.
     exitCode: failedSteps.length === 0 ? 0 : 1,
   };
 }
 
+/** One name or several, as one list — the context accepts both, every reader here wants a list. */
+const onlyList = (only: VerifyContext['only']): readonly string[] | undefined =>
+  only === undefined ? undefined : typeof only === 'string' ? [only] : only;
+
 /**
  * What the counts are allowed to claim. A step that does not apply is recorded green so the run
  * continues, and the summary counted it among the "all 17 steps passed" — so a repo whose `job`

package/src/verify-step.ts

@@ -79,15 +79,18 @@ export interface VerifyContext {
    */
   readonly workers?: number;
   /**
-   * ONE step, by name — an iteration loop, and the one thing here that IS a narrowing. The
+   * Some steps, by name — an iteration loop, and the one thing here that IS a narrowing. The
    * whole gate costs minutes (3m19s at the framework root on 12 cores, `As of 2026-09-23`), which
-   * is the cost of asking a question about one step. It does not weaken axiom 5, and the two rules that keep it honest are
-   * mechanical rather than remembered: a run with this set prints `NOT A GATE RUN` in the summary
-   * AND carries `notAGateRun` in `--json` (`verify-run.ts`), so no reader of either can mistake it
-   * for the gate; and nothing writes `x.verify.json`, so the suite floor cannot be lowered by a
-   * run that never executed the suites. Green still means the no-flag run, unchanged.
+   * is the cost of asking a question about one step. A list (`x verify --only typecheck,lint`) runs
+   * in ONE process, so an app's scoped runner stops paying a CLI boot and an app load per step.
+   * It does not weaken axiom 5, and the two rules that keep it honest are mechanical rather than
+   * remembered: a run with this set prints `NOT A GATE RUN` in the summary AND carries `notAGateRun`
+   * in `--json` (`verify-run.ts`), so no reader of either can mistake it for the gate; and nothing
+   * writes `x.verify.json`, so the suite floor cannot be lowered by a run that never executed the
+   * suites — even a list naming every step. Green still means the no-flag run, unchanged. A single
+   * name is accepted for the callers that narrow to one (`scripts/verify.ts`).
    */
-  readonly only?: VerifyStepName;
+  readonly only?: VerifyStepName | readonly VerifyStepName[];
 }
 
 export interface StepOutcome {