@williamthorsen/release-kit 10.7.0 → 10.9.0

package/dist/esm/workTypesData.d.ts

@@ -1,15 +1,13 @@
 /**
- * Canonical work-types data — runtime mirror of `work-types.json`.
+ * Canonical work-types data: the runtime mirror of `work-types.json`.
  *
- * `work-types.json` is the canonical SSOT for the taxonomy and is the file
- * `release-kit work-types check` / `:sync` operate on. This `.ts` mirror exists for
- * runtime consumption: ESM JSON imports require an `import attributes` clause that
- * esbuild's `bundle: false` mode strips, so a plain TS module is the most reliable way
- * to ship the data to consumers.
+ * `work-types.json` is release-kit's copy of the codeassembly canonical. This `.ts` mirror exists for
+ * runtime consumption: The compiler baseline does not enable JSON module imports, and a TS constant keeps
+ * `breakingPolicy` typed as its three-value union.
  *
- * A drift test (`workTypesData.unit.test.ts`) asserts that this constant deep-equals the
- * parsed contents of `work-types.json`. To change the taxonomy, edit BOTH files (or run
- * `nmr work-types:sync` to pull from upstream).
+ * `nmr work-types:sync` updates only the JSON, so copy its change here by hand. A drift test
+ * (`workTypesData.unit.test.ts`) asserts that this constant deep-equals the parsed contents of
+ * `work-types.json`.
  */
 /** Schema for a single entry. */
 export interface WorkTypeEntry {
@@ -18,6 +16,7 @@ export interface WorkTypeEntry {
     aliases: string[];
     emoji: string;
     label: string;
+    description: string;
     breakingPolicy: 'forbidden' | 'optional' | 'required';
     excludedFromChangelog?: boolean;
 }
@@ -34,6 +33,8 @@ export interface MarkerEntry {
 }
 /** Schema for the full data. */
 export interface WorkTypesData {
+    /** Semantic version of the data shape, as declared by the upstream canonical. */
+    version: string;
     tiers: string[];
     types: WorkTypeEntry[];
     /**

package/dist/esm/workTypesData.js

@@ -1,18 +1,60 @@
 export const WORK_TYPES_DATA = {
+    version: '1.1.0',
     tiers: ['public', 'internal', 'process'],
     types: [
-        { tier: 'public', key: 'feat', aliases: ['feature'], emoji: '🎉', label: 'Features', breakingPolicy: 'optional' },
-        { tier: 'public', key: 'drop', aliases: [], emoji: '🪦', label: 'Removed', breakingPolicy: 'required' },
-        { tier: 'public', key: 'deprecate', aliases: [], emoji: '🗑️', label: 'Deprecated', breakingPolicy: 'forbidden' },
-        { tier: 'public', key: 'fix', aliases: ['bugfix'], emoji: '🐛', label: 'Bug fixes', breakingPolicy: 'forbidden' },
-        { tier: 'public', key: 'sec', aliases: ['security'], emoji: '🔒', label: 'Security', breakingPolicy: 'optional' },
+        {
+            tier: 'public',
+            key: 'feat',
+            aliases: ['feature'],
+            emoji: '🎉',
+            label: 'Features',
+            description: 'A change that gives consumers a new capability or extends an existing one.',
+            breakingPolicy: 'optional',
+        },
+        {
+            tier: 'public',
+            key: 'drop',
+            aliases: [],
+            emoji: '🪦',
+            label: 'Removed',
+            description: 'A change that removes a capability or surface on which consumers depend.',
+            breakingPolicy: 'required',
+        },
+        {
+            tier: 'public',
+            key: 'deprecate',
+            aliases: [],
+            emoji: '🗑️',
+            label: 'Deprecated',
+            description: 'A change that marks a capability or surface for removal while the capability or surface keeps working.',
+            breakingPolicy: 'forbidden',
+        },
+        {
+            tier: 'public',
+            key: 'fix',
+            aliases: ['bugfix'],
+            emoji: '🐛',
+            label: 'Bug fixes',
+            description: 'A change that corrects behavior that consumers meet and that differs from what was intended.',
+            breakingPolicy: 'optional',
+        },
+        {
+            tier: 'public',
+            key: 'sec',
+            aliases: ['security'],
+            emoji: '🔒',
+            label: 'Security',
+            description: 'A change that closes a vulnerability or hardens a consumer-facing surface against attack.',
+            breakingPolicy: 'optional',
+        },
         {
             tier: 'public',
             key: 'perf',
             aliases: ['performance'],
             emoji: '⚡',
             label: 'Performance',
-            breakingPolicy: 'forbidden',
+            description: 'A change that reduces the time, memory, or other resources that consumer-facing work uses, without changing its result.',
+            breakingPolicy: 'optional',
         },
         {
             tier: 'internal',
@@ -20,6 +62,7 @@ export const WORK_TYPES_DATA = {
             aliases: ['utility'],
             emoji: '🏗️',
             label: 'Internal features',
+            description: 'A change that adds or extends a capability that consumers do not use directly, such as a helper or an internal module.',
             breakingPolicy: 'forbidden',
         },
         {
@@ -28,19 +71,61 @@ export const WORK_TYPES_DATA = {
             aliases: [],
             emoji: '♻️',
             label: 'Refactoring',
+            description: 'A change that restructures existing code without changing its behavior.',
+            breakingPolicy: 'forbidden',
+        },
+        {
+            tier: 'internal',
+            key: 'tests',
+            aliases: ['test'],
+            emoji: '🧪',
+            label: 'Tests',
+            description: 'A change confined to tests, test fixtures, or test helpers, including one that unblocks a build or a type check.',
+            breakingPolicy: 'forbidden',
+        },
+        {
+            tier: 'process',
+            key: 'tooling',
+            aliases: [],
+            emoji: '⚙️',
+            label: 'Tooling',
+            description: 'A change to the tools used to develop the project: build, lint, formatting, and release configuration, and development scripts.',
+            breakingPolicy: 'forbidden',
+        },
+        {
+            tier: 'process',
+            key: 'ci',
+            aliases: [],
+            emoji: '👷',
+            label: 'CI',
+            description: 'A change to continuous-integration workflows and their configuration.',
+            breakingPolicy: 'forbidden',
+        },
+        {
+            tier: 'process',
+            key: 'deps',
+            aliases: ['dep'],
+            emoji: '📦',
+            label: 'Dependencies',
+            description: 'A change that adds, removes, or upgrades a dependency, including its lockfile and version-catalog entries.',
+            breakingPolicy: 'forbidden',
+        },
+        {
+            tier: 'process',
+            key: 'ai',
+            aliases: [],
+            emoji: '🤖',
+            label: 'Agentic support',
+            description: "A change to guidance on working in the repository itself, such as its `AGENTS.md` or a repo-local skill, or to the repository's agent configuration.",
             breakingPolicy: 'forbidden',
         },
-        { tier: 'internal', key: 'tests', aliases: ['test'], emoji: '🧪', label: 'Tests', breakingPolicy: 'forbidden' },
-        { tier: 'process', key: 'tooling', aliases: [], emoji: '⚙️', label: 'Tooling', breakingPolicy: 'forbidden' },
-        { tier: 'process', key: 'ci', aliases: [], emoji: '👷', label: 'CI', breakingPolicy: 'forbidden' },
-        { tier: 'process', key: 'deps', aliases: ['dep'], emoji: '📦', label: 'Dependencies', breakingPolicy: 'forbidden' },
-        { tier: 'process', key: 'ai', aliases: [], emoji: '🤖', label: 'Agentic support', breakingPolicy: 'forbidden' },
         {
             tier: 'process',
             key: 'docs',
             aliases: ['doc'],
             emoji: '📚',
             label: 'Documentation',
+            description: 'A change to documentation for human readers, such as a README, a guide, or a code comment.',
             breakingPolicy: 'forbidden',
         },
         {
@@ -49,6 +134,7 @@ export const WORK_TYPES_DATA = {
             aliases: [],
             emoji: '🎨',
             label: 'Formatting',
+            description: 'A change to formatting alone, such as whitespace or line wrapping, that leaves the content unchanged.',
             breakingPolicy: 'forbidden',
             excludedFromChangelog: true,
         },

package/docs/changelogs.md

@@ -8,13 +8,13 @@ Neither `CHANGELOG.md` nor `.meta/changelog.json` reaches a published tarball on
 
 Each item under a section in `.meta/changelog.json` carries one required field and four optional ones:
 
-| Field         | Type      | Meaning                                                                                                                                        |
-| ------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
-| `description` | `string`  | The bullet headline, taken from the commit subject with the ticket ID and type prefix stripped.                                                |
-| `body`        | `string`  | The commit body, with trailing trailer metadata stripped.                                                                                      |
-| `breaking`    | `boolean` | Present and `true` where the commit subject carried the `!` prefix. See [`!` (breaking change) policy](work-types.md#-breaking-change-policy). |
-| `migration`   | `string`  | The migration step for a consumer. See below.                                                                                                  |
-| `hash`        | `string`  | The full commit SHA, and the key on which an override entry matches. Absent on synthetic propagation entries.                                  |
+| Field         | Type      | Meaning                                                                                                                                                                         |
+| ------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `description` | `string`  | The bullet headline, taken from the commit subject with the ticket ID and type prefix stripped.                                                                                 |
+| `body`        | `string`  | The commit body, with trailing trailer metadata stripped.                                                                                                                       |
+| `breaking`    | `boolean` | Present and `true` where the commit subject carried the `!` prefix and the commit's type permits it. See [`!` (breaking change) policy](work-types.md#-breaking-change-policy). |
+| `migration`   | `string`  | The migration step for a consumer. See below.                                                                                                                                   |
+| `hash`        | `string`  | The full commit SHA, and the key on which an override entry matches. Absent on synthetic propagation entries.                                                                   |
 
 Every optional field is omitted rather than emitted as `null`, so a consumer tests for presence.
 
@@ -32,7 +32,7 @@ A commit body states a migration step as a paragraph opening with the literal la
 
 Three properties are worth knowing:
 
-- **It is independent of `breaking`.** A `fix` cannot carry `!` under the default breaking policy, and a `fix` that tightens validation still imposes a migration. Filter on `migration` to find every step; filter on `breaking` to find every breaking change.
+- **It is independent of `breaking`.** A `deprecate` cannot carry `!` under the default breaking policy, and a `deprecate` still calls for a migration. Filter on `migration` to find every step; filter on `breaking` to find every breaking change.
 - **`body` keeps the paragraph.** The field is an extraction, not a move, so `CHANGELOG.md` and `.meta/changelog.json` go on agreeing.
 - **It is derived, not authored.** `migration` is not a field an override file can set (see [File shape](editorial-overrides.md#file-shape)); it is re-derived from whatever `body` an override installs, and cleared where that body carries no labeled paragraph. To change the migration text, override `body`.
 

package/docs/configuration.md

@@ -1,6 +1,6 @@
 # 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).
 
@@ -103,3 +103,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/work-types.md

@@ -1,17 +1,17 @@
 # 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.
 
-The canonical taxonomy lives in `packages/release-kit/src/work-types.json` and 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   |
 | -------- | ----------- | ------------------------- | ------------- | ------------ |
 | public   | `feat`      | 🎉 Features               | `feature`     | optional     |
 | public   | `drop`      | 🪦 Removed                |               | **required** |
 | public   | `deprecate` | 🗑️ Deprecated             |               | forbidden    |
-| public   | `fix`       | 🐛 Bug fixes              | `bugfix`      | forbidden    |
+| public   | `fix`       | 🐛 Bug fixes              | `bugfix`      | optional     |
 | public   | `sec`       | 🔒 Security               | `security`    | optional     |
-| public   | `perf`      | ⚡ Performance            | `performance` | forbidden    |
+| public   | `perf`      | ⚡ Performance            | `performance` | optional     |
 | internal | `internal`  | 🏗️ Internal features      | `utility`     | forbidden    |
 | internal | `refactor`  | ♻️ Refactoring            |               | forbidden    |
 | internal | `tests`     | 🧪 Tests                  | `test`        | forbidden    |
@@ -38,41 +38,44 @@ Section render order is **tier order (`public` → `internal` → `process`), th
 
 Each work-type carries a `breakingPolicy` value:
 
-- `optional` (`feat`, `sec`) — `!` is allowed; both `type:` and `type!:` parse cleanly.
-- `forbidden` (most types) — `!` is a policy violation. The premise: types like `internal!`, `perf!`, `fix!` are contradictory; an internal change cannot break a consumer contract, a pure perf change preserves the contract, and a bug-fix is by definition not a contract change.
-- `required` (`drop`) — bare `drop:` is a policy violation; only `drop!:` is accepted. The premise: removing a feature always breaks consumers; the `!` form makes that explicit.
+- `optional` (`feat`, `fix`, `sec`, `perf`): `!` is allowed; both `type:` and `type!:` parse cleanly. Any of these can break consumers, and the marker records when one does: A fix can break consumers who relied on the defective behavior, and a performance change can break a contract to achieve its gain.
+- `forbidden` (`deprecate` and every `internal`- and `process`-tier type): `!` is a policy violation. Deprecating a surface keeps it working, and removing it is a `drop`. Internal- and process-tier work does not face consumers; a change that breaks consumers faces them and therefore takes a public-tier type.
+- `required` (`drop`): Bare `drop:` is a policy violation; only `drop!:` is accepted. Removing a public surface always breaks consumers, and the `!` form makes that explicit.
 
-### Two-tier policy enforcement
+### Policy enforcement
 
-The `!` policy operates at two distinct levels with different semantics:
+`parseCommitMessage` enforces the `!` policy at release time and treats a violation as a warning. Commits already in the log cannot be rewritten, so a policy-violating commit is parsed using its canonical type with `breaking: false` (the `!` is dropped from the parse) and an `onPolicyViolation` callback fires. Callers (`decideRelease` etc.) can collect these warnings and surface them in the release report. A single legacy `internal!` in a year-old log does not block releases.
 
-- **Write-time** (commit-msg hook) — strict rejection. Policy violations are blocked at the gate where the author can act on them immediately. _Hook-based enforcement is tracked separately and is not yet shipped._
-- **Release-time** (`parseCommitMessage`) — tolerant warn-and-continue. Commits already in the log cannot be rewritten, so a policy-violating commit is parsed using its canonical type with `breaking: false` (the `!` is dropped from the parse) and a `onPolicyViolation` callback fires. Callers (`decideRelease` etc.) can collect these warnings and surface them in the release report. A single legacy `internal!` in a year-old log does not block releases.
-
-A `BREAKING CHANGE:` body footer on a `forbidden`-policy type triggers the same warning path as the prefix `!` does — the spirit of the policy is "internal/perf/etc. cannot be breaking", which must apply to both surfaces.
+A `BREAKING CHANGE:` body footer on a `forbidden`-policy type triggers the same warning path as the prefix `!` does: A type that cannot be breaking is parsed as non-breaking whichever surface carries the signal.
 
 The release-prepare orchestrators (`releasePrepare`, `releasePrepareMono`, `releasePrepareProject`) apply `DEFAULT_BREAKING_POLICIES` automatically. Violations encountered while parsing each workspace's or project's commit window are collected onto the corresponding result's `policyViolations` field and rendered under the section in the prepare report:
 
 ```
 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)
 ```
 
-To customize, set `breakingPolicies` in `release-kit.config.ts` — provide a partial map to override individual types, or `{}` to disable enforcement entirely (the parser falls back to `'optional'` for any missing type). Violations remain warnings, never failures.
+To customize, set `breakingPolicies` in `release-kit.config.ts`. The map replaces the default policies rather than merging with them, and the parser treats any type that the map omits as `'optional'`: A config that changes one type lists every policy that it keeps, and `{}` disables enforcement entirely. Violations remain warnings, never failures.
 
 ## `🚨 **Breaking:**` bullet marker
 
-Items whose commit subject carries the `!` prefix (e.g. `feat!`, `drop!`, `feat(api)!`) are rendered with a `🚨 **Breaking:** ` prefix on the bullet:
+Items whose commit subject carries the `!` prefix (e.g. `feat!`, `drop!`, `feat(api)!`) on a type whose policy permits it are rendered with a `🚨 **Breaking:** ` prefix on the bullet:
 
 ```markdown
 - 🚨 **Breaking:** Drop legacy /v1 endpoint
 ```
 
-Only the prefix `!` triggers this marker. A `BREAKING CHANGE:` body footer on its own does **not** retroactively mark a changelog item as breaking — the changelog signal is tied to the commit-prefix policy. This avoids surprise breaking-marker appearances for older commits written under earlier conventions.
+The marker agrees with the version bump:
+
+- A `forbidden`-policy type carrying `!`, such as `refactor!`, gets no marker, just as its `!` raises no bump; the prepare report lists it as a policy violation. An [editorial override](editorial-overrides.md) that sets `breaking: true` restores the marker for one entry.
+- The configured `breakingPolicies` map, `{}` included, decides which types permit the marker.
+- A commit whose type the parser cannot resolve has no policy, so its `!` prefix alone decides.
+
+A `BREAKING CHANGE:` body footer on its own does **not** retroactively mark a changelog item as breaking, even on a type whose policy permits `!`; the changelog signal is tied to the commit prefix. This avoids surprise breaking-marker appearances for older commits written under earlier conventions.
 
 The emoji and label of this marker are sourced from the `markers.breaking` entry in `work-types.json` (see [Section markers](#section-markers)) so consumers that render their own breaking-changes section draw from the same SSOT.
 
@@ -100,22 +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.
 
-The check is non-blocking initially: until codeassembly publishes its `work-types.json`, the upstream URL returns 404 and `check` exits 0 with a warning. CI flip to a blocking check is tracked as a follow-up once the upstream ships.
+- `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.
 
-These commands are also exposed as `nmr work-types:check` / `nmr work-types:sync` from any package directory.
+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.
 
-### Authenticated fetches
+`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.
 
-When the upstream codeassembly repo is private, both `check` and `sync` need a GitHub token to fetch the canonical `work-types.json`. Set `GITHUB_TOKEN` in the environment and the commands send `Authorization: Bearer <token>` automatically; without it, requests are unauthenticated and a private upstream will return 404.
-
-```sh
-# Source from `gh auth` for local runs:
-export GITHUB_TOKEN=$(gh auth token)
-pnpm exec release-kit work-types check
-```
+### Authenticated fetches
 
-The token needs `contents: read` on the codeassembly repo (fine-grained PAT scope) or the equivalent classic-PAT scope. A token without sufficient scope still produces a 404 — same response as a missing upstream — so a misconfigured token degrades to the transitional-warning path rather than failing loudly. CI wiring against private upstream is deferred until either codeassembly is publicly readable or a cross-repo PAT is provisioned as a workflow secret.
+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.7.0",
+  "version": "10.9.0",
   "description": "Version-bumping and changelog-generation toolkit for release workflows",
   "keywords": [
     "changelog",
@@ -51,20 +51,20 @@
     "schemas/**"
   ],
   "dependencies": {
-    "@williamthorsen/nmr-core": "0.11.1",
-    "@williamthorsen/toolbelt.errors": "0.7.0",
+    "@williamthorsen/nmr-core": "0.12.0",
+    "@williamthorsen/toolbelt.errors": "0.8.1",
     "glob": "13.0.6",
     "json-stringify-pretty-compact": "4.0.0",
     "semver": "7.8.5",
     "yaml": "2.9.0",
-    "zod": "4.5.4"
+    "zod": "4.6.2"
   },
   "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"
   },
@@ -76,9 +76,9 @@
     "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,36 +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 missing/transitional, 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 transitional warning (codeassembly hasn't published the
- *   JSON yet; the check is informational while migration is in flight).
- * - 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>;

package/dist/esm/checkWorkTypesDrift.js

@@ -1,117 +0,0 @@
-import { readFileSync } from 'node:fs';
-import { dirname, resolve } from 'node:path';
-import { fileURLToPath } from 'node:url';
-import { formatErrorLine } from '@williamthorsen/nmr-core';
-import { describeError } from '@williamthorsen/toolbelt.errors';
-import { buildFetchInit, hasExpectedTopLevelShape } from "./workTypesUtils.js";
-export const UPSTREAM_WORK_TYPES_URL = 'https://raw.githubusercontent.com/williamthorsen/codeassembly/main/packages/agents/content/skills/_data/work-types.json';
-function resolveDefaultLocalPath() {
-    const moduleDir = dirname(fileURLToPath(import.meta.url));
-    return resolve(moduleDir, 'work-types.json');
-}
-export async function checkWorkTypesDrift(dependencies = {}) {
-    const localPath = dependencies.localPath ?? resolveDefaultLocalPath();
-    const fetcher = dependencies.fetch ?? globalThis.fetch;
-    const url = dependencies.upstreamUrl ?? UPSTREAM_WORK_TYPES_URL;
-    const localContent = readFileSync(localPath, 'utf8');
-    let localJson;
-    try {
-        localJson = JSON.parse(localContent);
-    }
-    catch (error) {
-        return {
-            exitCode: 3,
-            message: `Local work-types.json is not valid JSON: ${describeError(error)}`,
-        };
-    }
-    const fetchInit = buildFetchInit();
-    let response;
-    try {
-        response = fetchInit === undefined ? await fetcher(url) : await fetcher(url, fetchInit);
-    }
-    catch (error) {
-        return {
-            exitCode: 2,
-            message: formatErrorLine(`Failed to fetch upstream work-types.json: ${describeError(error)}`),
-        };
-    }
-    if (response.status === 404) {
-        return {
-            exitCode: 0,
-            message: `Upstream work-types.json not yet published at ${url}; skipping drift check.`,
-        };
-    }
-    if (!response.ok) {
-        return {
-            exitCode: 2,
-            message: formatErrorLine(`Failed to fetch upstream work-types.json: HTTP ${response.status} ${response.statusText}`),
-        };
-    }
-    const upstreamText = await response.text();
-    let upstreamJson;
-    try {
-        upstreamJson = JSON.parse(upstreamText);
-    }
-    catch (error) {
-        return {
-            exitCode: 3,
-            message: `Upstream work-types.json is not valid JSON: ${describeError(error)}`,
-        };
-    }
-    if (!hasExpectedTopLevelShape(upstreamJson)) {
-        return {
-            exitCode: 3,
-            message: 'Upstream work-types.json does not match the expected schema shape (missing `tiers` or `types`).',
-        };
-    }
-    const normalisedLocal = stripLocalOnlyFields(localJson);
-    if (deepEqual(normalisedLocal, upstreamJson)) {
-        return {
-            exitCode: 0,
-            message: 'Local work-types.json matches upstream.',
-        };
-    }
-    return {
-        exitCode: 1,
-        message: `Drift detected. Local and upstream work-types.json differ. Run \`nmr work-types:sync\` to update from upstream.\nLocal:    ${localPath}\nUpstream: ${url}`,
-    };
-}
-function stripLocalOnlyFields(value) {
-    if (typeof value !== 'object' || value === null || Array.isArray(value)) {
-        return value;
-    }
-    const record = { ...value };
-    delete record['$schema'];
-    return record;
-}
-function deepEqual(a, b) {
-    if (a === b)
-        return true;
-    if (typeof a !== typeof b)
-        return false;
-    if (a === null || b === null)
-        return a === b;
-    if (Array.isArray(a) && Array.isArray(b)) {
-        if (a.length !== b.length)
-            return false;
-        for (let i = 0; i < a.length; i++) {
-            if (!deepEqual(a[i], b[i]))
-                return false;
-        }
-        return true;
-    }
-    if (typeof a === 'object' && typeof b === 'object' && !Array.isArray(a) && !Array.isArray(b)) {
-        const aRecord = { ...a };
-        const bRecord = { ...b };
-        const aKeys = Object.keys(aRecord);
-        const bKeys = Object.keys(bRecord);
-        if (aKeys.length !== bKeys.length)
-            return false;
-        for (const key of aKeys) {
-            if (!deepEqual(aRecord[key], bRecord[key]))
-                return false;
-        }
-        return true;
-    }
-    return false;
-}

package/dist/esm/syncWorkTypes.d.ts

@@ -1,28 +0,0 @@
-/** Outcome of a sync operation. */
-export interface SyncResult {
-    /**
-     * Process exit code semantics:
-     * - `0` — sync succeeded (file may be unchanged).
-     * - `2` — network error or local write failure.
-     * - `3` — schema mismatch (upstream JSON does not parse or fails the shape check).
-     */
-    exitCode: 0 | 2 | 3;
-    message: string;
-}
-/** Minimal injection seam so unit tests can substitute a deterministic fetcher. */
-export interface SyncWorkTypesDependencies {
-    /** Absolute path of the local `work-types.json`. Defaults to the bundled file. */
-    localPath?: string;
-    /** HTTP fetcher. Defaults to global `fetch`. */
-    fetch?: typeof globalThis.fetch;
-    /** Override the upstream URL (used by tests). */
-    upstreamUrl?: string;
-}
-/**
- * Fetch the upstream `work-types.json`, validate its top-level shape, and overwrite the
- * locally-bundled copy with the formatted upstream contents.
- *
- * Output is reformatted to match the local file's conventions (2-space indent, trailing
- * newline) so subsequent diffs are content-driven, not whitespace-driven.
- */
-export declare function syncWorkTypes(dependencies?: SyncWorkTypesDependencies): Promise<SyncResult>;