@williamthorsen/release-kit 10.8.0 → 11.0.0

package/dist/esm/sync-labels/initCommand.d.ts

@@ -1,15 +1,22 @@
+import { type StreamStyles } from '@williamthorsen/nmr-core';
 /** Options for the `sync-labels init` subcommand. */
 interface InitOptions {
+    /** Config file to read, relative to the working directory. Defaults to `CONFIG_FILE_PATH`. */
+    configPath?: string;
     dryRun: boolean;
     force: boolean;
+    styles: StreamStyles;
 }
 /**
  * Run the `sync-labels init` subcommand.
  *
  * Discovers workspaces and retired packages, scaffolds the caller workflow, then seeds the
- * `repoLabels` block: into a new `.config/release-kit.config.ts` when none exists, or
- * printed to stdout for manual paste when the file is already there — an existing,
- * hand-authored config is never rewritten. Returns 0 on success, 1 on failure.
+ * `repoLabels` block: into a new config file when none exists, or printed to stdout for manual
+ * paste when the file is already there — an existing, hand-authored config is never rewritten.
+ * Returns 0 on success, 1 on failure.
+ *
+ * `configPath` names the config to read. Naming one that does not exist fails the command, so the
+ * scaffolding branch is reached only under the default path and always writes to `CONFIG_FILE_PATH`.
  */
-export declare function syncLabelsInitCommand({ dryRun, force }: InitOptions): Promise<number>;
+export declare function syncLabelsInitCommand({ configPath, dryRun, force, styles }: InitOptions): Promise<number>;
 export {};

package/dist/esm/sync-labels/initCommand.js

@@ -1,47 +1,52 @@
 import { existsSync } from 'node:fs';
 import { reportWriteResult, writeFileWithCheck } from '@williamthorsen/nmr-core';
 import { describeError } from '@williamthorsen/toolbelt.errors';
-import { discoverWorkspaces } from "../discoverWorkspaces.js";
+import { describeEmptyWorkspace, discoverWorkspaces } from "../discoverWorkspaces.js";
 import { CONFIG_FILE_PATH } from "../loadConfig.js";
-import { loadValidatedConfig } from "../loadValidatedConfig.js";
+import { loadValidatedConfig, reportConfigProblem } from "../loadValidatedConfig.js";
 import { generateCommand, LABELS_OUTPUT_PATH } from "./generateCommand.js";
 import { checkRetiredSyncLabelsConfig } from "./retiredConfig.js";
 import { buildScopeLabels, renderRepoLabelsBlock, repoLabelsConfigScript, syncLabelsWorkflow } from "./templates.js";
 const WORKFLOW_PATH = '.github/workflows/sync-labels.yaml';
-export async function syncLabelsInitCommand({ dryRun, force }) {
-    if (checkRetiredSyncLabelsConfig()) {
+export async function syncLabelsInitCommand({ configPath, dryRun, force, styles }) {
+    const configFilePath = configPath ?? CONFIG_FILE_PATH;
+    if (checkRetiredSyncLabelsConfig(configPath)) {
         return 1;
     }
     if (dryRun) {
         console.info('[dry-run mode]');
     }
     console.info('\n> Discovering workspaces');
-    let workspacePaths;
+    let workspace;
     try {
-        workspacePaths = await discoverWorkspaces();
+        workspace = discoverWorkspaces();
     }
     catch (error) {
         const message = describeError(error);
         process.stderr.write(`  Failed to discover workspaces: ${message}\n`);
         return 1;
     }
-    if (workspacePaths === undefined) {
+    if (workspace.kind === 'empty') {
+        process.stderr.write(`  No workspace package to label. ${describeEmptyWorkspace(workspace)}\n`);
+        return 1;
+    }
+    if (workspace.kind === 'single-package') {
         console.info('  No pnpm workspaces found (single-package repo)');
     }
     else {
-        console.info(`  Found ${String(workspacePaths.length)} workspaces`);
+        console.info(`  Found ${String(workspace.packageDirs.length)} workspaces`);
     }
-    const configExists = existsSync(CONFIG_FILE_PATH);
-    const retiredNames = configExists ? await loadRetiredPackageNames() : [];
+    const configExists = configPath !== undefined || existsSync(CONFIG_FILE_PATH);
+    const retiredNames = configExists ? await loadRetiredPackageNames(styles, configPath) : [];
     if (retiredNames === undefined) {
         return 1;
     }
-    const scopeLabels = workspacePaths === undefined ? [] : buildScopeLabels(workspacePaths, retiredNames);
+    const scopeLabels = workspace.kind === 'single-package' ? [] : buildScopeLabels(workspace.packageDirs, retiredNames);
     console.info('\n> Scaffolding files');
     const workflowResult = writeFileWithCheck(WORKFLOW_PATH, syncLabelsWorkflow(), { dryRun, overwrite: force });
-    reportWriteResult(workflowResult, dryRun);
+    reportWriteResult(workflowResult, dryRun, styles);
     if (configExists) {
-        console.info(`\n> ${CONFIG_FILE_PATH} already exists; add this block to the object passed to defineConfig:\n`);
+        console.info(`\n> ${configFilePath} already exists; add this block to the object passed to defineConfig:\n`);
         console.info(renderRepoLabelsBlock(scopeLabels));
         if (workflowResult.outcome === 'failed') {
             process.stderr.write('Failed to scaffold one or more files.\n');
@@ -49,7 +54,7 @@ export async function syncLabelsInitCommand({ dryRun, force }) {
         }
         console.info(`
 > Next steps
-  1. Paste the block above into ${CONFIG_FILE_PATH}.
+  1. Paste the block above into ${configFilePath}.
   2. Run \`release-kit sync-labels generate\` to produce ${LABELS_OUTPUT_PATH}.
   3. Commit the changes.
   4. Run \`release-kit sync-labels sync\` to apply labels to your GitHub repo.
@@ -60,7 +65,7 @@ export async function syncLabelsInitCommand({ dryRun, force }) {
         dryRun,
         overwrite: force,
     });
-    reportWriteResult(configResult, dryRun);
+    reportWriteResult(configResult, dryRun, styles);
     if (workflowResult.outcome === 'failed' || configResult.outcome === 'failed') {
         process.stderr.write('Failed to scaffold one or more files.\n');
         return 1;
@@ -70,7 +75,7 @@ export async function syncLabelsInitCommand({ dryRun, force }) {
     }
     else {
         console.info('\n> Generating labels');
-        const generateExitCode = await generateCommand();
+        const generateExitCode = await generateCommand({ styles });
         if (generateExitCode !== 0) {
             return generateExitCode;
         }
@@ -87,9 +92,10 @@ export async function syncLabelsInitCommand({ dryRun, force }) {
 `);
     return 0;
 }
-async function loadRetiredPackageNames() {
-    const result = await loadValidatedConfig();
+async function loadRetiredPackageNames(styles, configPath) {
+    const result = await loadValidatedConfig(configPath);
     if (result.status === 'invalid') {
+        reportConfigProblem(result.problem, styles.stderr);
         return undefined;
     }
     if (result.status === 'missing') {

package/dist/esm/sync-labels/retiredConfig.d.ts

@@ -5,6 +5,8 @@ export declare const RETIRED_SYNC_LABELS_CONFIG_PATH = ".config/sync-labels.conf
  *
  * Returns `true` when the file exists, in which case the caller must abort. The check is
  * unconditional on config content: file presence alone triggers it, so a half-migrated
- * repo cannot silently lose its custom labels.
+ * repo cannot silently lose its custom labels. `configPath` names the config to move the labels
+ * into; it defaults to `CONFIG_FILE_PATH`, which `sync-labels sync` relies on because it takes
+ * no `--config`.
  */
-export declare function checkRetiredSyncLabelsConfig(): boolean;
+export declare function checkRetiredSyncLabelsConfig(configPath?: string): boolean;

package/dist/esm/sync-labels/retiredConfig.js

@@ -2,10 +2,10 @@ import { existsSync } from 'node:fs';
 import { reportError } from '@williamthorsen/nmr-core';
 import { CONFIG_FILE_PATH } from "../loadConfig.js";
 export const RETIRED_SYNC_LABELS_CONFIG_PATH = '.config/sync-labels.config.ts';
-export function checkRetiredSyncLabelsConfig() {
+export function checkRetiredSyncLabelsConfig(configPath = CONFIG_FILE_PATH) {
     if (!existsSync(RETIRED_SYNC_LABELS_CONFIG_PATH)) {
         return false;
     }
-    reportError(`${RETIRED_SYNC_LABELS_CONFIG_PATH} is no longer read. Move its labels into the \`repoLabels\` block of ${CONFIG_FILE_PATH} (presets move to \`repoLabels.extends\`; each label becomes a \`'name': { color, description }\` entry under \`repoLabels.labels\`), then delete the file.`);
+    reportError(`${RETIRED_SYNC_LABELS_CONFIG_PATH} is no longer read. Move its labels into the \`repoLabels\` block of ${configPath} (presets move to \`repoLabels.extends\`; each label becomes a \`'name': { color, description }\` entry under \`repoLabels.labels\`), then delete the file.`);
     return true;
 }

package/dist/esm/tagCommand.d.ts

@@ -1,2 +1,3 @@
+import { type StreamStyles } from '@williamthorsen/nmr-core';
 /** Orchestrate the CLI `tag` command: parse flags and delegate to `createTags`. */
-export declare function tagCommand(argv: string[]): void;
+export declare function tagCommand(argv: string[], styles: StreamStyles): void;

package/dist/esm/tagCommand.js

@@ -5,10 +5,10 @@ const tagFlagSchema = {
     dryRun: { long: '--dry-run', type: 'boolean' },
     noGitChecks: { long: '--no-git-checks', type: 'boolean' },
 };
-export function tagCommand(argv) {
+export function tagCommand(argv, styles) {
     const { dryRun, noGitChecks } = parseArgsOrExit(argv, tagFlagSchema).flags;
     try {
-        createTags({ dryRun, noGitChecks });
+        createTags({ dryRun, noGitChecks, style: styles.stdout });
     }
     catch (error) {
         reportError(describeError(error));

package/dist/esm/validateOverridesCommand.d.ts

@@ -1,9 +1,11 @@
+import { type OutputStyle, type StreamStyles } from '@williamthorsen/nmr-core';
 import { type ValidateAllChangelogOverridesInputs, type ValidateAllChangelogOverridesResult } from './changelogOverrides.js';
+import { type WorkspaceDiscovery } from './discoverWorkspaces.js';
+import { type LoadValidatedConfigResult } from './loadValidatedConfig.js';
 import type { ChangelogEntry, ReleaseConfig } from './types.js';
 /**
  * Result of {@link validateOverridesCommand}: tiered exit code paired with a human-readable
- * message. Mirrors the shape of `checkWorkTypesDrift` so the CLI dispatch layer can stay
- * uniformly thin.
+ * message, which keeps the CLI dispatch layer thin.
  *
  * Exit codes:
  * - `0` — clean: no errors, no warnings.
@@ -16,8 +18,8 @@ export interface ValidateOverridesCommandResult {
 }
 /** Injection seams for unit testing. Production callers leave defaults; tests substitute deterministic fakes. */
 export interface ValidateOverridesCommandDependencies {
-    discoverWorkspaces?: () => Promise<string[] | undefined>;
-    loadConfig?: () => Promise<unknown>;
+    discoverWorkspaces?: () => WorkspaceDiscovery;
+    loadValidatedConfig?: () => Promise<LoadValidatedConfigResult>;
     /**
      * Build changelog entries for a scope. Defaults to `buildChangelogEntries`, the same path
      * `release-kit prepare` uses — anchoring `validate`'s hash universe to `prepare`'s by
@@ -34,11 +36,15 @@ export interface ValidateOverridesCommandDependencies {
  * {@link validateAllChangelogOverrides}.
  *
  * Single-package and monorepo modes are handled uniformly: single-package collapses to one
- * project scope; monorepo expands to a project scope plus one scope per workspace.
+ * project scope; monorepo expands to a project scope plus one scope per workspace. A workspace declaring
+ * patterns that resolve to no package is neither, and exits `2`.
+ *
+ * `configPath` names the config file to read, relative to the working directory; it defaults to
+ * `CONFIG_FILE_PATH`.
  */
-export declare function validateOverridesCommand(dependencies?: ValidateOverridesCommandDependencies): Promise<ValidateOverridesCommandResult>;
+export declare function validateOverridesCommand(styles: StreamStyles, configPath?: string, dependencies?: ValidateOverridesCommandDependencies): Promise<ValidateOverridesCommandResult>;
 /**
  * Pure formatter — take an aggregated validation result, return the tiered exit code and a
  * rendered message. Exported for unit testing without going through the full discovery path.
  */
-export declare function formatValidateOverridesResult(result: ValidateAllChangelogOverridesResult): ValidateOverridesCommandResult;
+export declare function formatValidateOverridesResult(result: ValidateAllChangelogOverridesResult, style: OutputStyle): ValidateOverridesCommandResult;

package/dist/esm/validateOverridesCommand.js

@@ -1,60 +1,57 @@
-import { formatErrorLine } from '@williamthorsen/nmr-core';
+import { formatErrorLine, formatStatusLine } from '@williamthorsen/nmr-core';
 import { describeError } from '@williamthorsen/toolbelt.errors';
 import { buildChangelogEntries } from "./buildChangelogEntries.js";
 import { resolveOverridePath, validateAllChangelogOverrides, } from "./changelogOverrides.js";
-import { discoverWorkspaces } from "./discoverWorkspaces.js";
+import { describeEmptyWorkspace, discoverWorkspaces } from "./discoverWorkspaces.js";
 import { buildTagPattern, getAllTagPrefixes } from "./generateChangelogs.js";
-import { loadConfig, mergeMonorepoConfig, mergeSinglePackageConfig, readRootPackageVersion } from "./loadConfig.js";
-import { validateConfig } from "./validateConfig.js";
+import { mergeMonorepoConfig, mergeSinglePackageConfig, readRootPackageVersion } from "./loadConfig.js";
+import { loadValidatedConfig } from "./loadValidatedConfig.js";
 const SYNTHETIC_VALIDATE_TAG = 'validate-only';
-export async function validateOverridesCommand(dependencies = {}) {
+export async function validateOverridesCommand(styles, configPath, dependencies = {}) {
     const discover = dependencies.discoverWorkspaces ?? discoverWorkspaces;
-    const load = dependencies.loadConfig ?? loadConfig;
+    const load = dependencies.loadValidatedConfig ?? (() => loadValidatedConfig(configPath));
     const buildEntries = dependencies.buildEntries ?? defaultBuildEntries;
     const validate = dependencies.validate ?? validateAllChangelogOverrides;
-    let rawConfig;
-    try {
-        rawConfig = await load();
-    }
-    catch (error) {
-        return { exitCode: 2, message: formatErrorLine(`Failed to load config: ${describeError(error)}`) };
-    }
-    let userConfig;
-    try {
-        userConfig = validateLoadedConfig(rawConfig);
-    }
-    catch (error) {
-        return { exitCode: 2, message: describeError(error) };
+    const configResult = await load();
+    if (configResult.status === 'invalid') {
+        return { exitCode: 2, message: formatConfigProblem(configResult.problem) };
     }
-    let discoveredPaths;
+    const userConfig = configResult.status === 'ok' ? configResult.config : undefined;
+    let workspace;
     try {
-        discoveredPaths = await discover();
+        workspace = discover();
     }
     catch (error) {
         return { exitCode: 2, message: formatErrorLine(`Failed to discover workspaces: ${describeError(error)}`) };
     }
+    if (workspace.kind === 'empty') {
+        return {
+            exitCode: 2,
+            message: formatErrorLine(`No workspace package to validate. ${describeEmptyWorkspace(workspace)}`),
+        };
+    }
     let inputs;
     try {
         inputs =
-            discoveredPaths === undefined
+            workspace.kind === 'single-package'
                 ? buildSinglePackageInputs(userConfig, buildEntries)
-                : buildMonorepoInputs(discoveredPaths, userConfig, buildEntries);
+                : buildMonorepoInputs(workspace.packageDirs, userConfig, buildEntries);
     }
     catch (error) {
         return { exitCode: 2, message: formatErrorLine(`Failed to resolve overrides scope: ${describeError(error)}`) };
     }
     const result = validate(inputs);
-    return formatValidateOverridesResult(result);
+    return formatValidateOverridesResult(result, styles.stderr);
 }
-export function formatValidateOverridesResult(result) {
+export function formatValidateOverridesResult(result, style) {
     const { errors, warnings } = result;
     if (errors.length === 0 && warnings.length === 0) {
         return { exitCode: 0, message: 'All override files are valid (no errors, no stale keys).' };
     }
     const exitCode = errors.length > 0 ? 2 : 1;
     const summary = formatSummaryLine(errors.length, warnings.length);
-    const errorLines = errors.map((message) => `  ❌ ${message}`);
-    const warningLines = warnings.map((message) => `  ⚠️  ${message}`);
+    const errorLines = errors.map((message) => `  ${formatStatusLine(style, 'failed', message)}`);
+    const warningLines = warnings.map((message) => `  ${formatStatusLine(style, 'warning', message)}`);
     const message = [summary, '', ...errorLines, ...warningLines].join('\n');
     return { exitCode, message };
 }
@@ -94,15 +91,10 @@ function flattenEntriesToHashes(entries) {
     }
     return hashes;
 }
-function validateLoadedConfig(rawConfig) {
-    if (rawConfig === undefined) {
-        return undefined;
-    }
-    const { config, errors } = validateConfig(rawConfig);
-    if (errors.length > 0) {
-        throw new Error(`Invalid config:\n  - ${errors.join('\n  - ')}`);
-    }
-    return config;
+function formatConfigProblem(problem) {
+    return problem.kind === 'load'
+        ? formatErrorLine(`Failed to load config: ${problem.message}`)
+        : `Invalid config:\n  - ${problem.errors.join('\n  - ')}`;
 }
 function buildSinglePackageInputs(userConfig, buildEntries) {
     const config = mergeSinglePackageConfig(userConfig);

package/docs/configuration.md

@@ -1,9 +1,19 @@
 # Configuration
 
-The fields of `.config/release-kit.config.ts`, how a workspace declares its prior identities or a retired package, the rule against colliding tag prefixes, and the patterns that decide a bump.
+The fields of `.config/release-kit.config.ts`, how a workspace declares its prior identities or a retired package, the rule against colliding tag prefixes, the patterns that decide a bump, and the environment variable that sets the output style.
 
 A minimal config file is in the [README](../README.md#configuration).
 
+## Config file location
+
+release-kit reads `.config/release-kit.config.ts`, resolved against the working directory. A run reads a different file when the subcommand is given `--config <path>`, which is also resolved against the working directory.
+
+The flag is accepted by every subcommand that reads a config: `prepare`, `publish`, `create-github-release`, `show-tag-prefixes`, `overrides validate`, `sync-labels init`, and `sync-labels generate`. `commit`, `tag`, `push`, and `sync-labels sync` read no config and reject it.
+
+The two paths differ in what an absent file means. An absent default path means the repo declares no config, and the run proceeds on discovered defaults. An absent `--config` path fails the command with an error naming the resolved path, because a caller who names a file expects that file to be read. A file that exists and fails validation is an error on both paths alike, and so is one that exists and fails to load.
+
+`--config` names a file to read, never a write target. `release-kit init --with-config` scaffolds to `.config/release-kit.config.ts` and takes no `--config`, and `sync-labels init` writes its seeded `repoLabels` block to that same path.
+
 ## `ReleaseKitConfig` reference
 
 | Field              | Type                                                      | Description                                                                                                                                                                                   |
@@ -89,6 +99,8 @@ Print a per-workspace table of derived tag prefixes, tag counts, and declared le
 
 Exits `0` when every workspace derives a prefix and there are no cross-workspace collisions; exits `1` on any derivation failure or collision. Undeclared candidates do not affect the exit code — they surface as a warning via the `legacy tag prefixes are declared` readyup check.
 
+A config file that exists and either fails to load or fails schema validation reports the failure on stderr and exits `1`, printing no preview, because a config that cannot be read leaves the declared-versus-undeclared verdict wrong in the one dimension the command exists to report on. That holds on the default path and under `--config`, and in single-package mode as well as monorepo mode. An absent default config is a supported state and still previews against derived defaults.
+
 In single-package mode, prints a single row with `workspacePath = .` and `derivedPrefix = v`; legacy entries and undeclared-candidate scanning are not applicable.
 
 ## `VersionPatterns`
@@ -103,3 +115,25 @@ interface VersionPatterns {
 ```
 
 Default: `{ major: ['!'], minor: ['feat'] }`
+
+## Output style
+
+release-kit prints in one of two styles. `rich` marks each status with an emoji, such as ✅ or 🟠. `plain` replaces each emoji with a word, such as `PASS` or `WARN`, which a reader of a log can search for. The style is decided separately for stdout and stderr, so redirecting one stream to a file leaves the other rich at a terminal.
+
+The `RELEASE_KIT_OUTPUT_STYLE` environment variable sets the style for every command, `init` and `sync-labels init` included:
+
+| Value   | Effect                                                                   |
+| ------- | ------------------------------------------------------------------------ |
+| `auto`  | Detect the style of each stream. The same as leaving the variable unset. |
+| `plain` | Print plain on both streams.                                             |
+| `rich`  | Print rich on both streams, even in a pipe or under CI.                  |
+
+Any other value is a usage error: release-kit reports it and exits with code 1.
+
+The variable outranks detection. Under `auto`, release-kit defers to detection, which reads `CI`, then the stream, then `TERM`. A stream is plain when any of these holds, and rich otherwise:
+
+1. `CI` is set to anything other than an empty string or `false`.
+2. The stream is not a terminal, as when its output is piped or redirected.
+3. `TERM` is `linux`, the Linux virtual console, which draws no emoji.
+
+The style governs emoji alone. Changelog section emoji are file content rather than terminal output, and they are unaffected.

package/docs/labels.md

@@ -8,6 +8,8 @@ Manage GitHub label definitions via the `repoLabels` block of `.config/release-k
 
 `init` scaffolds the `.github/workflows/sync-labels.yaml` caller workflow and seeds a `repoLabels` block with scope labels discovered from workspaces and declared `retiredPackages`. When `.config/release-kit.config.ts` does not exist, `init` writes it; when it does, `init` prints the block for manual paste — a hand-authored config is never rewritten. `generate` resolves the block and writes `.github/labels.yaml`; with `--check` it regenerates in memory and exits non-zero if the committed file is stale or missing, writing nothing. `sync` triggers the workflow remotely — it requires the `gh` CLI and an existing workflow file.
 
+`init` and `generate` accept `--config <path>` to read a config elsewhere; `sync` reads none and rejects the flag. Under `--config`, `init` reads the named file and prints the block for manual paste, and fails when that file does not exist rather than scaffolding one, so its write target stays `.config/release-kit.config.ts`. See [Config file location](configuration.md#config-file-location).
+
 Every `sync-labels` subcommand refuses to run while the retired `.config/sync-labels.config.ts` is present, so custom labels cannot be silently dropped mid-migration, and the refusal names what to move and where.
 
 ### Label configuration

package/docs/work-types.md

@@ -1,8 +1,8 @@
 # Work types and tiers
 
-The taxonomy against which release-kit parses commits: its tiers, the breaking-change policy, section markers, customization, and the commands that compare it with its upstream.
+The taxonomy against which release-kit parses commits: its tiers, the breaking-change policy, section markers, customization, and the maintainer scripts that keep release-kit's copy level with its upstream.
 
-release-kit bundles a copy of the codeassembly canonical taxonomy in `packages/release-kit/src/work-types.json`, kept level by `release-kit work-types sync`. The taxonomy is split into three tiers that drive section rendering and audience classification.
+release-kit bundles a copy of the codeassembly canonical taxonomy in `packages/release-kit/src/work-types.json`, kept level by the [maintainer scripts](#maintaining-the-bundled-taxonomy). The taxonomy is split into three tiers that drive section rendering and audience classification.
 
 | Tier     | Key         | Header                    | Aliases       | `!` policy   |
 | -------- | ----------- | ------------------------- | ------------- | ------------ |
@@ -53,7 +53,7 @@ The release-prepare orchestrators (`releasePrepare`, `releasePrepareMono`, `rele
 ```
 arrays
   Found 1 commits since arrays-v1.0.0
-  ⚠️  1 policy violation:
+  🟠 1 policy violation:
       · def5678 'internal!: refactor cache' — type 'internal' at prefix surface
   Bumping versions (patch)...
   📦 1.0.0 → 1.0.1 (patch)
@@ -103,14 +103,17 @@ Work types from your config are merged with these defaults by key — your entri
 
 The default `devOnlySections` (excluded from public release notes but still written to `CHANGELOG.md`) are derived from the `internal` and `process` tiers (excluding `fmt`). Override via `changelogJson.devOnlySections` in your config; matching is decorator-tolerant, so a bare-name override like `['Internal features']` keeps working against the emoji-prefixed and prefix-decorated default titles.
 
-## `release-kit work-types`
+## Maintaining the bundled taxonomy
 
-Manage the canonical work-types taxonomy used by changelog and release-notes generation.
+`src/workTypesData.ts` mirrors `src/work-types.json` for runtime use. Two maintainer scripts of the release-kit package compare that JSON with its codeassembly upstream and update it. They exist only in a checkout of this repository and are not part of the published `release-kit` CLI.
 
-`check` exits 0 on a match, 1 on drift, 2 when the upstream fetch fails, and 3 when either file is not valid JSON or the upstream fails the shape check. When the upstream URL returns 404, `check` exits 0 with a warning.
+- `nmr work-types:check` compares the content of `src/work-types.json` with the upstream, ignoring the local `$schema` hint.
+- `nmr work-types:sync` overwrites `src/work-types.json` with the upstream when their content differs.
+
+Both run from `packages/release-kit`, or from anywhere in the repository as `nmr -F @williamthorsen/release-kit work-types:check` and `nmr -F @williamthorsen/release-kit work-types:sync`. After `sync` writes the file, update `src/workTypesData.ts` to match; `workTypesData.unit.test.ts` fails until the two agree.
 
-These commands are also exposed as `nmr work-types:check` / `nmr work-types:sync` from any package directory.
+`check` exits 0 on a match, 1 on drift, 2 when the upstream fetch fails, and 3 when either file is not valid JSON or the upstream fails the shape check. When the upstream URL returns 404, `check` exits 0 with a warning.
 
 ### Authenticated fetches
 
-The upstream codeassembly repo is public, so `check` and `sync` need no token. When `GITHUB_TOKEN` is set in the environment, both commands send it as `Authorization: Bearer <token>`.
+The upstream codeassembly repo is public, so `check` and `sync` need no token. When `GITHUB_TOKEN` is set in the environment, both scripts send it as `Authorization: Bearer <token>`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@williamthorsen/release-kit",
-  "version": "10.8.0",
+  "version": "11.0.0",
   "description": "Version-bumping and changelog-generation toolkit for release workflows",
   "keywords": [
     "changelog",
@@ -51,34 +51,33 @@
     "schemas/**"
   ],
   "dependencies": {
-    "@williamthorsen/nmr-core": "0.11.1",
-    "@williamthorsen/toolbelt.errors": "0.7.0",
-    "glob": "13.0.6",
+    "@williamthorsen/nmr-core": "0.13.0",
+    "@williamthorsen/toolbelt.errors": "0.8.1",
     "json-stringify-pretty-compact": "4.0.0",
     "semver": "7.8.5",
-    "yaml": "2.9.0",
-    "zod": "4.5.4"
+    "yaml": "2.9.1",
+    "zod": "4.6.5"
   },
   "devDependencies": {
     "@types/semver": "7.8.0",
-    "@williamthorsen/toolbelt.filesystem": "0.8.3",
-    "@williamthorsen/toolbelt.testing": "0.5.1",
-    "@williamthorsen/toolbelt.vitest": "0.9.0",
-    "readyup": "0.36.0",
+    "@williamthorsen/toolbelt.filesystem": "0.9.1",
+    "@williamthorsen/toolbelt.testing": "0.6.1",
+    "@williamthorsen/toolbelt.vitest": "0.10.1",
+    "readyup": "0.38.0",
     "smol-toml": "1.8.0",
     "vitest": "4.1.11"
   },
   "engines": {
-    "node": ">=24"
+    "node": ">=24.16.0"
   },
   "publishConfig": {
     "access": "public",
     "registry": "https://registry.npmjs.org"
   },
   "scripts": {
-    "build:post": "node scripts/copy-work-types.js && rdy compile",
+    "build:post": "rdy compile",
     "build:pre": "rdy verify",
-    "work-types:check": "pnpm exec release-kit work-types check",
-    "work-types:sync": "pnpm exec release-kit work-types sync"
+    "work-types:check": "node scripts/check-work-types.ts",
+    "work-types:sync": "node scripts/sync-work-types.ts"
   }
 }

package/presets/labels/common.yaml

@@ -4,7 +4,7 @@
 # Main categories
 - name: ai
   color: a2eeef
-  description: Documentation and configs used by agents
+  description: Guidance on working in this repo, such as its AGENTS.md or a repo-local skill, or its agent config
 - name: breaking
   color: b60205
   description: Breaking API change or removal of functionality
@@ -16,7 +16,7 @@
   description: Marks functionality for future removal
 - name: documentation
   color: a2eeef
-  description: Improvements or additions to documentation
+  description: Documentation for human readers, such as a README, a guide, or a code comment
 - name: feature
   color: '0075ca'
   description: Added or improved external functionality

package/dist/esm/checkWorkTypesDrift.d.ts

@@ -1,35 +0,0 @@
-/** URL of the upstream canonical `work-types.json` published by codeassembly. */
-export declare const UPSTREAM_WORK_TYPES_URL = "https://raw.githubusercontent.com/williamthorsen/codeassembly/main/packages/agents/content/skills/_data/work-types.json";
-/** Outcome of a drift check, paired with a human-readable message. */
-export interface DriftCheckResult {
-    /**
-     * Process exit code semantics:
-     * - `0` — match (or upstream not found, with a warning).
-     * - `1` — drift detected.
-     * - `2` — network error.
-     * - `3` — schema mismatch (upstream JSON does not parse or fails the schema invariants).
-     */
-    exitCode: 0 | 1 | 2 | 3;
-    message: string;
-}
-/** Minimal injection seam so unit tests can substitute a deterministic fetcher. */
-export interface CheckWorkTypesDriftDependencies {
-    /** Absolute path of the local `work-types.json`. Defaults to the bundled file. */
-    localPath?: string;
-    /** HTTP fetcher. Defaults to global `fetch` (Node 18+). */
-    fetch?: typeof globalThis.fetch;
-    /** Override the upstream URL (used by tests; production callers should leave default). */
-    upstreamUrl?: string;
-}
-/**
- * Compare the bundled `work-types.json` against the upstream codeassembly canonical and
- * report drift.
- *
- * Failure modes:
- * - Network error → exit 2 with a diagnostic.
- * - Upstream 404 → exit 0 with a warning.
- * - Schema mismatch → exit 3 with a diagnostic.
- * - Drift → exit 1 with a unified-diff-style message.
- * - Match → exit 0.
- */
-export declare function checkWorkTypesDrift(dependencies?: CheckWorkTypesDriftDependencies): Promise<DriftCheckResult>;