@rrlab/cli 1.0.1-git-e008b4d.0 → 1.1.0

package/dist/cli.usage.kdl

@@ -1,7 +1,7 @@
 // @generated by @usage-spec/commander from Commander.js metadata
 name rr
 bin rr
-version "1.0.1-git-e008b4d.0"
+version "1.1.0"
 usage "<command...> [options...]"
 flag --usage help="print KDL spec for this CLI (https://kdl.dev)"
 cmd completion help="print shell completion script (usage)" {

package/dist/config.d.mts

@@ -1,4 +1,4 @@
-import { u as Plugin } from "./types-6gZWuLJf.mjs";
+import { u as Plugin } from "./types-snfbujDH.mjs";
 
 //#region src/types/config.d.ts
 type UserConfig = {

package/dist/plugin.d.mts

@@ -1,4 +1,4 @@
-import { C as StaticChecker, D as ReleaseService, E as TypeChecker, O as ReleaseServiceOptions, S as RunReport, T as TypeCheckOptions, _ as Doctor, a as InstallFlags, b as LintOptions, c as PLUGIN_KINDS, d as PluginCapabilities, f as PluginContext, g as UninstallResult, h as UninstallFlags, i as InstallContext, l as Packer, m as UninstallContext, n as ClackPromptsSelectOption, o as InstallResult, p as PluginKind, r as FileOp, s as JsonEdit, t as ClackPrompts, u as Plugin, v as FormatOptions, w as StaticCheckerOptions, x as Linter, y as Formatter } from "./types-6gZWuLJf.mjs";
+import { C as StaticChecker, D as ReleaseService, E as TypeChecker, O as ReleaseServiceOptions, S as RunReport, T as TypeCheckOptions, _ as Doctor, a as InstallFlags, b as LintOptions, c as PLUGIN_KINDS, d as PluginCapabilities, f as PluginContext, g as UninstallResult, h as UninstallFlags, i as InstallContext, l as Packer, m as UninstallContext, n as ClackPromptsSelectOption, o as InstallResult, p as PluginKind, r as FileOp, s as JsonEdit, t as ClackPrompts, u as Plugin, v as FormatOptions, w as StaticCheckerOptions, x as Linter, y as Formatter } from "./types-snfbujDH.mjs";
 import { ShellService } from "@vlandoss/clibuddy";
 
 //#region src/plugin/decide-scaffold.d.ts

package/dist/run.mjs

@@ -164,29 +164,19 @@ function commandTool(command, provider) {
 function pkgName(appPkg) {
 	return appPkg.packageJson.name ?? basename(appPkg.dirPath);
 }
-/**
-* The one canonical row label for a single-target run: `<command> (<tool>) · <package>`.
-* Every command/subcommand that acts on one target (lint, format, jsc, pack,
-* single-app tsc, a `doctor` subcommand) builds its row through here so they
-* all read identically.
-*/
+/** The canonical single-target row label, `<command> (<tool>) · <package>`, so every command reads alike. */
 function targetLabel(command, provider, appPkg) {
 	return `${commandTool(command, provider)} ${palette.dim(`· ${pkgName(appPkg)}`)}`;
 }
 /**
-* The one canonical section title for a fan-out run: `<command> (<tool>) · <n> <unit>`
-* (e.g. `tsc (oxlint) · 8 packages`). The tool is omitted when the fan-out
-* spans several tools (`rr doctor` → `doctor · 3 tools`); the rows then carry
-* the per-unit name.
+* The canonical fan-out section title, `<command> (<tool>) · <n> <unit>`. The
+* tool is omitted when the fan-out spans several tools (`rr doctor` → `doctor ·
+* 3 tools`), since the rows then carry the per-tool name.
 */
 function fanoutTitle(command, provider, count, unit) {
 	return `${provider ? commandTool(command, provider) : command} · ${count} ${unit}`;
 }
-/**
-* Bridges a check-family verb (which returns a `RunReport`) to a board row.
-* The row's spinner reflects the in-flight run; the captured `output` becomes
-* the detail the board flushes grouped under the label.
-*/
+/** Bridges a check-family verb (returns a `RunReport`) to a board row, its `output` becoming the flushed detail. */
 function reportTask(label, run) {
 	return {
 		label,
@@ -283,17 +273,11 @@ ${runRunColor(`
 //#endregion
 //#region src/program/commands/check.ts
 /**
-* `rr check` is the umbrella that runs the JS check (lint+format) and the
-* TS type check together. Both subcommands are already wired into
-* commander as siblings (`rr jsc`, `rr tsc`), so we reuse the program's
-* command tree as the action registry instead of duplicating it: look the
-* sibling up by name and invoke its action via `parseAsync([])`, which
-* applies its declared option defaults exactly as if the user had typed
-* `rr jsc` directly.
-*
-* Commander binds the running command as `this` inside an action (see
-* `command.js` — `fn.apply(this, actionArgs)`). `this.parent` gives us the
-* parent program without any late-binding ceremony.
+* `rr check` runs `jsc` then `tsc`. Rather than keep a parallel action
+* registry, it reuses commander's command tree: it finds each sibling on
+* `this.parent` and runs it via `parseAsync([])`, which applies the sibling's
+* own option defaults. (`this` is the running command inside a non-arrow
+* action — see cli/CLAUDE.md.)
 */
 function createCheckCommand(ctx) {
 	return createCommand("check").summary(`run static checks${checkAnnotation(ctx)}`).description("Runs `rr jsc` then `rr tsc` in-process, each as its own section. Aggregates their exit codes — non-zero when either subcommand fails.").action(async function checkAction() {
@@ -336,12 +320,9 @@ function findCommand(program, name) {
 	return program.commands.find((c) => c.name() === name || c.aliases().includes(name));
 }
 /**
-* Mirrors the provider resolution of `jsc` + `tsc` and flattens the
-* underlying tool labels — e.g. biome (composed lint+format) + oxc (tsc)
-* renders as `(biome, oxlint)` rather than `(biome + biome, oxlint)`. When
-* neither sibling has a provider, falls back to the standard `(not
-* configured)` annotation so the help reads consistently with other
-* commands.
+* Flattens the underlying tool labels of `jsc` + `tsc` for the help summary —
+* e.g. `(biome, oxlint)`, deduped, not `(biome + biome, oxlint)`. Falls back to
+* the standard `(not configured)` when neither sibling has a provider.
 */
 function checkAnnotation(ctx) {
 	const directJsc = ctx.registry.get("jsc");
@@ -475,15 +456,11 @@ function createFormatCommand(ctx) {
 //#endregion
 //#region src/program/composed-jsc.ts
 /**
-* Synthesises a `StaticChecker & Doctor` (the `jsc` capability) by composing
-* a separately-registered linter and formatter. Used when the user's plugin
-* set provides `lint` and `format` independently (e.g. oxc, or eslint +
-* prettier) but no single plugin claims `jsc`.
-*
-* The check runs lint then format sequentially — interleaved stdout from a
-* parallel run is hard to read for the user — and merges their reports into one
-* so the board renders the pair as a single row. `fixStaged` is dropped because
-* the underlying tools don't have a uniform staged-aware mode.
+* Synthesises the `jsc` capability (`StaticChecker & Doctor`) by composing a
+* separately-registered linter and formatter — used when the plugin set
+* provides `lint` and `format` independently (e.g. oxc) but no plugin claims
+* `jsc`. Runs lint then format sequentially (parallel stdout interleaves badly)
+* and merges their reports into one board row.
 */
 function composedJscProvider(linter, formatter) {
 	return {

package/dist/{types-6gZWuLJf.d.mts → types-snfbujDH.d.mts}

@@ -28,13 +28,11 @@ declare class ReleaseService {
 //#endregion
 //#region src/types/tool.d.ts
 /**
- * The outcome of running a check-family tool (lint / format / static check /
- * type check) captured rather than streamed. `ok` is the tool's own verdict —
- * its exit code, never a guess parsed from output — and `output` is the
- * combined captured stdout+stderr (color preserved), flushed verbatim grouped
- * under the package label. We deliberately do NOT parse tool summaries for
- * warning/error counts: the formats are unstable and not uniform across tools
- * (tsc and oxfmt have no machine output at all). See decisions/013.
+ * The outcome of a check-family tool (lint / format / static check / type
+ * check) captured rather than streamed. `ok` is the tool's exit code — never a
+ * guess parsed from output, since tool summaries are unstable and not uniform
+ * (tsc and oxfmt emit none) — and `output` is the combined stdout+stderr (color
+ * preserved), flushed verbatim under the package label. See decisions/013.
  */
 type RunReport = {
   ok: boolean;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rrlab/cli",
-  "version": "1.0.1-git-e008b4d.0",
+  "version": "1.1.0",
   "description": "The CLI toolbox to fullstack common scripts in Variable Land",
   "homepage": "https://github.com/variableland/dx/tree/main/run-run/cli#readme",
   "bugs": {
@@ -56,7 +56,7 @@
     "memoize": "10.2.0",
     "nypm": "0.6.0",
     "rimraf": "6.1.3",
-    "@vlandoss/clibuddy": "0.6.2-git-e008b4d.0",
+    "@vlandoss/clibuddy": "0.7.0",
     "@vlandoss/loggy": "0.2.1"
   },
   "devDependencies": {

package/src/program/board.ts

@@ -17,32 +17,22 @@ function pkgName(appPkg: Pkg): string {
   return appPkg.packageJson.name ?? basename(appPkg.dirPath);
 }
 
-/**
- * The one canonical row label for a single-target run: `<command> (<tool>) · <package>`.
- * Every command/subcommand that acts on one target (lint, format, jsc, pack,
- * single-app tsc, a `doctor` subcommand) builds its row through here so they
- * all read identically.
- */
+/** The canonical single-target row label, `<command> (<tool>) · <package>`, so every command reads alike. */
 export function targetLabel(command: string, provider: Provider, appPkg: Pkg): string {
   return `${commandTool(command, provider)} ${palette.dim(`· ${pkgName(appPkg)}`)}`;
 }
 
 /**
- * The one canonical section title for a fan-out run: `<command> (<tool>) · <n> <unit>`
- * (e.g. `tsc (oxlint) · 8 packages`). The tool is omitted when the fan-out
- * spans several tools (`rr doctor` → `doctor · 3 tools`); the rows then carry
- * the per-unit name.
+ * The canonical fan-out section title, `<command> (<tool>) · <n> <unit>`. The
+ * tool is omitted when the fan-out spans several tools (`rr doctor` → `doctor ·
+ * 3 tools`), since the rows then carry the per-tool name.
  */
 export function fanoutTitle(command: string, provider: Provider | undefined, count: number, unit: string): string {
   const head = provider ? commandTool(command, provider) : command;
   return `${head} · ${count} ${unit}`;
 }
 
-/**
- * Bridges a check-family verb (which returns a `RunReport`) to a board row.
- * The row's spinner reflects the in-flight run; the captured `output` becomes
- * the detail the board flushes grouped under the label.
- */
+/** Bridges a check-family verb (returns a `RunReport`) to a board row, its `output` becoming the flushed detail. */
 export function reportTask(label: string, run: () => Promise<RunReport>): BoardTask {
   return {
     label,
@@ -53,11 +43,8 @@ export function reportTask(label: string, run: () => Promise<RunReport>): BoardT
   };
 }
 
-// `rr check` runs several single-task sections (jsc, tsc) back to back. On its
-// own each would render compactly, but the frame is what visually divides the
-// sections — so while check is dispatching, force every board to stay framed.
-// While active, the collector also gathers each section's result in run order
-// so `check` can print one overall verdict.
+// While `rr check` is dispatching, boards stay framed (to divide the sections)
+// and their results land in this collector so `check` can print one verdict.
 let collector: BoardResult[] | null = null;
 
 export async function runCheckSections(run: () => Promise<void>): Promise<BoardResult[]> {

package/src/program/commands/check.ts

@@ -6,17 +6,11 @@ import type { Context } from "#src/services/ctx.ts";
 import { logger } from "#src/services/logger.ts";
 
 /**
- * `rr check` is the umbrella that runs the JS check (lint+format) and the
- * TS type check together. Both subcommands are already wired into
- * commander as siblings (`rr jsc`, `rr tsc`), so we reuse the program's
- * command tree as the action registry instead of duplicating it: look the
- * sibling up by name and invoke its action via `parseAsync([])`, which
- * applies its declared option defaults exactly as if the user had typed
- * `rr jsc` directly.
- *
- * Commander binds the running command as `this` inside an action (see
- * `command.js` — `fn.apply(this, actionArgs)`). `this.parent` gives us the
- * parent program without any late-binding ceremony.
+ * `rr check` runs `jsc` then `tsc`. Rather than keep a parallel action
+ * registry, it reuses commander's command tree: it finds each sibling on
+ * `this.parent` and runs it via `parseAsync([])`, which applies the sibling's
+ * own option defaults. (`this` is the running command inside a non-arrow
+ * action — see cli/CLAUDE.md.)
  */
 export function createCheckCommand(ctx: Context) {
   return createCommand("check")
@@ -32,13 +26,11 @@ export function createCheckCommand(ctx: Context) {
         throw new Error("`rr check` requires the parent program to dispatch sibling subcommands.");
       }
 
-      // jsc then tsc, sequentially: each renders its own live board and two
-      // boards can't animate the same terminal region at once (decision 012).
-      // Each section runs inside its own `runCheckSections` scope — that both
-      // keeps it framed (so the frames divide the sections) and returns the
-      // boards THAT section rendered, so failure is attributed by section name,
-      // never by a fragile dispatch-vs-render index. A section that runs no
-      // board (tsc with no tsconfig) simply reports no results.
+      // Sequentially, not in parallel: two live boards can't animate the same
+      // terminal region at once (decision 012). Each section runs in its own
+      // `runCheckSections` scope, which frames it and returns the boards it
+      // rendered — so a failure is attributed by section name, not a fragile
+      // dispatch-vs-render index.
       const start = Date.now();
       const failed: string[] = [];
       let rendered = false;
@@ -85,12 +77,9 @@ function findCommand(program: Command, name: string): Command | undefined {
 }
 
 /**
- * Mirrors the provider resolution of `jsc` + `tsc` and flattens the
- * underlying tool labels — e.g. biome (composed lint+format) + oxc (tsc)
- * renders as `(biome, oxlint)` rather than `(biome + biome, oxlint)`. When
- * neither sibling has a provider, falls back to the standard `(not
- * configured)` annotation so the help reads consistently with other
- * commands.
+ * Flattens the underlying tool labels of `jsc` + `tsc` for the help summary —
+ * e.g. `(biome, oxlint)`, deduped, not `(biome + biome, oxlint)`. Falls back to
+ * the standard `(not configured)` when neither sibling has a provider.
  */
 function checkAnnotation(ctx: Context): string {
   const directJsc = ctx.registry.get("jsc");

package/src/program/composed-jsc.ts

@@ -1,15 +1,11 @@
 import type { Doctor, Formatter, Linter, RunReport, StaticChecker, StaticCheckerOptions } from "#src/plugin/types.ts";
 
 /**
- * Synthesises a `StaticChecker & Doctor` (the `jsc` capability) by composing
- * a separately-registered linter and formatter. Used when the user's plugin
- * set provides `lint` and `format` independently (e.g. oxc, or eslint +
- * prettier) but no single plugin claims `jsc`.
- *
- * The check runs lint then format sequentially — interleaved stdout from a
- * parallel run is hard to read for the user — and merges their reports into one
- * so the board renders the pair as a single row. `fixStaged` is dropped because
- * the underlying tools don't have a uniform staged-aware mode.
+ * Synthesises the `jsc` capability (`StaticChecker & Doctor`) by composing a
+ * separately-registered linter and formatter — used when the plugin set
+ * provides `lint` and `format` independently (e.g. oxc) but no plugin claims
+ * `jsc`. Runs lint then format sequentially (parallel stdout interleaves badly)
+ * and merges their reports into one board row.
  */
 export function composedJscProvider(linter: Linter & Doctor, formatter: Formatter & Doctor): StaticChecker & Doctor {
   return {

package/src/types/tool.ts

@@ -1,11 +1,9 @@
 /**
- * The outcome of running a check-family tool (lint / format / static check /
- * type check) captured rather than streamed. `ok` is the tool's own verdict —
- * its exit code, never a guess parsed from output — and `output` is the
- * combined captured stdout+stderr (color preserved), flushed verbatim grouped
- * under the package label. We deliberately do NOT parse tool summaries for
- * warning/error counts: the formats are unstable and not uniform across tools
- * (tsc and oxfmt have no machine output at all). See decisions/013.
+ * The outcome of a check-family tool (lint / format / static check / type
+ * check) captured rather than streamed. `ok` is the tool's exit code — never a
+ * guess parsed from output, since tool summaries are unstable and not uniform
+ * (tsc and oxfmt emit none) — and `output` is the combined stdout+stderr (color
+ * preserved), flushed verbatim under the package label. See decisions/013.
  */
 export type RunReport = {
   ok: boolean;