@theholocron/cli 5.0.0-alpha.162 → 5.0.0-alpha.164

package/dist/index.d.mts

@@ -237,7 +237,8 @@ interface EnvConfig {
   namespaces?: string[];
 }
 /**
- * A single Chromatic project entry in a monorepo `run-chromatic` config.
+ * A single Chromatic project entry in a `verification.visualRegression`
+ * task's `chromatic-projects` config.
  * Each entry produces one matrix job in CI, publishing to a separate Chromatic project.
  *
  * The `tokenName` maps to a repository secret named `CHROMATIC_PROJECT_TOKEN_<TOKENNAME>`.
@@ -299,8 +300,9 @@ interface StorybookDeployProject {
 /**
  * Typed `with:` inputs for reusable workflows.
  *
- * `run-chromatic` accepts either a plain boolean (single-project) or a
- * `ChromaticProjectConfig[]` object (multi-project monorepo).
+ * `chromatic-projects` (on the `verification.visualRegression` task) takes a
+ * `ChromaticProjectConfig[]` directly; each entry's `untraced` glob list may
+ * be authored as an array and is newline-joined for you.
  *
  * `docs` / `storybook` are high-level deploy shorthand that `holocron repo setup`
  * translates to `type` / `storybook-projects` before writing the thin caller.
@@ -308,9 +310,7 @@ interface StorybookDeployProject {
  * `paths:` manually for deploy entries.
  */
 type WorkflowWithConfig = Record<string, unknown> & {
-  "run-chromatic"?: boolean | {
-    projects: ChromaticProjectConfig[];
-  };
+  "chromatic-projects"?: ChromaticProjectConfig[];
   /**
    * Docs deployment shorthand. `true` uses the org-standard `docs/` directory;
    * `{ path: "custom" }` uses a custom directory. Both derive a `paths:` entry automatically.
@@ -336,6 +336,25 @@ interface TaskEntryConfig {
   local?: boolean;
   /** The task's CI check context is a required status check + part of `holocron run ci`'s default run. */
   required?: boolean;
+  /**
+   * Per-repo additions to this task's generated `turbo.json` entry —
+   * a separate channel from `with:` (that's the reusable *workflow's*
+   * inputs; this is local turbo cache config, unrelated). No-op for a
+   * task with no turbo fan-out config in the registry. Mirrors
+   * astromech's own `TaskEntry["turbo"]` — kept in sync by hand, since
+   * this package doesn't depend on astromech directly.
+   */
+  turbo?: {
+    /** Extra env vars turbo hashes into this task's cache key, appended to the registry default. */
+    passThroughEnv?: string[];
+    /**
+     * Extra input globs appended to the registry default's `inputs`
+     * (holocron#845) — for a package whose layout the registry
+     * default doesn't cover (e.g. a flat-layout package with no
+     * `src/` directory at all).
+     */
+    inputs?: string[];
+  };
 }
 interface HolocronConfig {
   /** Project name. Derived from package.json when absent. */
@@ -371,7 +390,7 @@ interface HolocronConfig {
    * workflows / `package.json` scripts.
    *
    * Supported values (intent-facing vocabulary — epic #672, D3):
-   *   "verification.unitTests" | "verification.typeSafety" | "verification.performance" |
+   *   "verification.unitTests" | "verification.visualRegression" | "verification.typeSafety" | "verification.performance" |
    *   "sourceQuality.staticAnalysis" | "sourceQuality.formatting" |
    *   "sourceQuality.structuredDataValidation" | "sourceQuality.deadCodeAnalysis" |
    *   "security.secretDetection" | "security.codeScanning" |
@@ -415,23 +434,37 @@ interface HolocronConfig {
    * { name: "delivery.deploy", with: { docs: { path: "packages/site" } } }
    * ```
    *
-   * ### run-chromatic
-   * For a single-project repo, use `"run-chromatic": true` with a
-   * `CHROMATIC_PROJECT_TOKEN` repository secret.
+   * ### verification.visualRegression
+   * Its own task, not a `verification.unitTests` sub-job (holocron#394/#1062)
+   * — GitHub evaluates a job's `if:` before expanding its `strategy.matrix`,
+   * so no `chromatic-projects` default can make a *disabled* Chromatic job
+   * disappear from PR checks; only not generating the job at all does. Omit
+   * this task entirely for a repo that doesn't use Chromatic — no workflow,
+   * no job, no check, not even a skipped one.
+   *
+   * For a single-project repo, use a `CHROMATIC_PROJECT_TOKEN` repository
+   * secret with `tokenName: "default"`:
+   * ```ts
+   * {
+   *   name: "verification.visualRegression",
+   *   with: { "chromatic-projects": [{ tokenName: "default", workingDir: "." }] },
+   * }
+   * ```
    *
-   * For monorepos with multiple Storybooks, use the object form:
+   * For monorepos with multiple Storybooks, list one entry per project:
    * ```ts
-   * "run-chromatic": {
-   *   projects: [
-   *     { tokenName: "WEB", workingDir: "apps/web" },
-   *     { tokenName: "UI",  workingDir: "packages/ui" },
-   *   ]
+   * {
+   *   name: "verification.visualRegression",
+   *   with: {
+   *     "chromatic-projects": [
+   *       { tokenName: "WEB", workingDir: "apps/web" },
+   *       { tokenName: "UI",  workingDir: "packages/ui" },
+   *     ],
+   *   },
    * }
    * ```
    * Each `tokenName` maps to a repository secret named
-   * `CHROMATIC_PROJECT_TOKEN_<TOKENNAME>`. `holocron repo setup` expands this
-   * to the flat `run-chromatic: true` + `chromatic-projects: <json>` inputs
-   * that the reusable workflow accepts.
+   * `CHROMATIC_PROJECT_TOKEN_<TOKENNAME>`.
    *
    * @example
    * ["sourceQuality.staticAnalysis", { "name": "delivery.publish", "with": { "run-build": false } }]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@theholocron/cli",
-  "version": "5.0.0-alpha.162",
+  "version": "5.0.0-alpha.164",
   "description": "The Holocron CLI - a pluggable, capability-based orchestrator for spinning up and operating software projects.",
   "keywords": [
     "cli",
@@ -63,8 +63,8 @@
     "pino-pretty": "^13.1.3",
     "posthog-node": "^5.51.6",
     "yargs": "^18.1.0",
-    "@theholocron/astromech": "5.0.0-alpha.162",
-    "@theholocron/datapad": "5.0.0-alpha.162"
+    "@theholocron/astromech": "5.0.0-alpha.164",
+    "@theholocron/datapad": "5.0.0-alpha.164"
   },
   "devDependencies": {
     "@theholocron/eslint-config": "^8.8.0",