@kitschpatrol/shared-config 8.12.0 → 8.13.0

package/skills/ksc-update/SKILL.md

@@ -1,280 +1,239 @@
 ---
 name: ksc-update
 description: >-
-  Update dependencies in kitschpatrol shared config pnpm repositories and
-  monorepos with compatible changes, explicitly approved breaking changes, or
-  breaking changes for zero-versioned projects. Use when asked to update,
-  upgrade, refresh, or audit repository dependencies or GitHub Actions. Applies
-  a 24-hour release maturity policy with exceptions for kitschpatrol's packages,
-  reviews fresh-install consumer compatibility, validates known consumers,
-  minimizes configuration overrides, and recommends a release level.
-  Does not commit or release.
-compatibility: Requires Node.js, pnpm/pnpx, curl, jq, git, Bash, and access to npm, GitHub, and upstream release documentation.
+  Run full dependency and repository maintenance in kitschpatrol shared config
+  pnpm repositories and monorepos. Use when asked to update, upgrade, refresh,
+  or audit dependencies or GitHub Actions. Includes compatibility review,
+  migrations, configuration and documentation cleanup, packed-install
+  validation, and a release recommendation. Does not commit or release.
+license: MIT
 ---
 
 # Update dependencies
 
-Accept dependency and GitHub Actions updates under the version policy below.
-For projects at 1.0.0 or later, preserve existing contracts: public APIs, CLI
-behavior, outputs, defaults, supported consumer environments, and peer
-compatibility, unless the user explicitly approves a reviewed breaking change.
-Make the migrations accepted updates require. Do not commit, push, tag, publish,
-or release.
-
-## Execution mode
-
-Determine the mode before Setup and record it with the reason. Use unattended
-mode when explicitly requested, when `GITHUB_ACTIONS=true` or `CI=true`, or when
-the host cannot receive user replies. Otherwise use interactive mode; a missing
-TTY alone does not establish that an agent session is unattended.
-
-In unattended mode, never ask questions, wait for answers, or invoke a command
-that requires an interactive response. Existing explicit approvals still apply;
-silence and CI execution do not grant new approval. This mode overrides every
-instruction below to ask, confirm, or await a decision:
-
-- **Projects at 1.0.0 or later:** apply compatible changes and any reviewed
-  breaks already explicitly authorized. Defer other breaking candidates and
-  report them for a later decision. Judge consumer impact, not dependency
-  version labels; a compatible dependency major remains eligible.
-- **Zero-versioned projects:** retain the existing `0.x` allowance in unattended
-  runs. Apply reviewed breaking changes, complete their migrations, validate
-  the new contracts, and normally recommend a minor release. Do not defer them
-  merely because no person is present to approve the break. Other requirements,
-  including explicit approval for runtime-range restrictions and Node-types
-  changes, still apply.
-- **Other decisions and missing prerequisites:** without prior authorization,
-  leave approval-dependent changes unapplied, including range restrictions and
-  peer-warning suppressions. Report missing consumer information, credentials,
-  permissions, or validation resources instead of requesting them. Continue
-  independent work; if a required prerequisite prevents progress, report the
-  affected work as blocked or incomplete without waiting or bypassing it.
-
-Review and validation remain required in both modes. Defer candidates whose
-impact cannot be established or whose migration cannot be validated. If safe
-updates cannot be isolated without an unapproved change, leave those updates
-unapplied and explain the blocker. Report incompatible releases already allowed
-by published runtime ranges as existing consumer exposure; an older lockfile
-does not resolve that exposure.
-
-Produce changes and a report suitable for later PR automation. This skill does
-not create workflows or pull requests, or split work into multiple PRs. If
-nothing can be applied, produce the report without manufacturing a change.
-
-## Policy
-
-- **Compatible by default at 1.0.0 or later:** assess the effect on this repository
-  and its consumers, not just the dependency's version label. Minor and patch
-  updates can break compatibility; a dependency major can still be compatible.
-  Present useful breaking candidates with their impact, migration, validation,
-  and release implications before asking for approval; apply only within the
-  approved scope. Existing explicit approval remains valid. Defer unapproved
-  breaks and updates whose impact cannot be established. This includes authored
-  packages, production transitives, and workflow actions.
-- **Zero-versioned projects:** if the project's current release version has
-  major version zero (`0.x.y`), any breaking change within this update workflow
-  is permitted in both interactive and unattended modes, including changes to
-  public contracts and consumer Node.js requirements. This exception overrides
-  compatibility-preservation requirements below. Use the project's version, not
-  the dependency's version; in monorepos,
-  assess each affected published package or shared release version, not just a
-  private workspace root. Review and report breaking changes, make required
-  migrations, and validate the resulting behavior. All other policies still
-  apply.
-- **Release maturity:** third-party releases must be at least 24 hours old
-  (`--maturity-period 1` for Taze, `--min-age 1` for Actions Up, pnpm
-  `minimumReleaseAge` of 1440 minutes). Never disable installation safeguards to
-  make an update succeed.
-- **Authored packages:** packages owned by `kitschpatrol` (discovered at runtime
-  in Setup) are exempt from maturity and target their latest stable release,
-  including majors. The exemption does not bypass security or compatibility
-  review.
-- **Consumer ranges:** review the newest published version allowed by each
-  runtime dependency's declared range, as well as the lockfile. A fresh consumer
-  install can resolve that version even when CI locks an older one. Holding
-  back an in-range release requires a genuinely restrictive published range
-  (for example, `~1.8.0` instead of `^1.8.0` to exclude `1.9.0`), not just an
-  older lockfile entry. Obtain explicit approval before narrowing a runtime
-  range to hold a release back, even for a zero-versioned project; explain the
-  consumer effect. Do not use local overrides as a substitute for that decision.
-- **TypeScript:** select a compiler within the peer range of the accepted
-  `@kitschpatrol/typescript-config` version, intersected with other required
-  peers. Do not hard-code a compiler version. Offer the migration when an
-  authored major requires a newer compiler; see step 3. If that config is not
-  used, follow the project's compiler policy and peer requirements.
-- **Node types:** preserve `@types/node` declarations, including catalogs and
-  overrides, unless a reviewed migration has explicit authorization to change
-  them. New compiler libraries do not establish runtime API availability.
-- **Package manager:** only Setup manages `packageManager`. Exclude `pnpm`
-  from Taze discovery and writes.
-- **No weakening:** do not relax tests, lint rules, type checking, or security
-  settings to get a pass; do not blindly accept changed snapshots or generated
-  output. Compatibility-preserving lint disables described in step 5 are an
-  exception.
-- **No new noise:** every check is compared against the Setup baseline. A new
-  warning, deprecation, or peer issue is a finding to trace and report, not
-  background noise. Report compatibility-preserving lint disables from step 5;
-  ask before silencing other findings.
+Every invocation is a full maintenance run, including audits and requests that
+mention only GitHub Actions; there is no report-only or Actions-only mode. The
+caller's only decision is whether consumer-breaking changes are pre-approved for
+packages at 1.0.0 or later. Make the migrations that accepted updates require.
+
+Supporting files sit beside this file. [configuration.md](references/configuration.md)
+owns every per-file rule; read it during Setup and apply it through the final
+cleanup. [verification.md](references/verification.md) owns baselines,
+validation procedures, and the bundled scripts.
+
+## Execution and authorization
+
+Record the execution mode and its reason before Setup. Use unattended mode when
+explicitly requested, when `GITHUB_ACTIONS=true` or `CI=true`, or when the host
+cannot receive replies; a missing TTY alone does not establish it. Unattended
+runs never ask, wait, or run a command that needs an interactive response, and
+report needed decisions as follow-up items.
+
+Judge compatibility by effect on public APIs, CLI behavior, outputs, defaults,
+supported consumer environments, and peers, never by a dependency's version
+label: minors and patches can break those contracts and majors can preserve
+them. This applies to authored packages, production transitives, and actions
+alike. A package is `0.x` by its own published version, or the shared release
+version in a monorepo, never a private root's version.
+
+| Change                                                                                                                                                                                                               | Rule                                           |
+| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
+| Compatible update                                                                                                                                                                                                    | Apply after review and validation.             |
+| Consumer break in a package at 1.0.0 or later                                                                                                                                                                        | Apply only within existing explicit approval.  |
+| Consumer break in a `0.x` package, including Node.js support changes                                                                                                                                                 | Apply after review, migration, and validation. |
+| Pre-authorized by the configuration policy: Homebrew pnpm alignment, LTS-only Node.js ranges, Node-types alignment, compatibility-preserving lint disables, scoped suppression of a verified-compatible peer warning | Apply and report.                              |
+| Other restrictions and suppressions: a published runtime-range restriction to hold a release back, including in `0.x`; a build approval outside the trust list; any other warning suppression                        | Apply only within existing explicit approval.  |
+
+Where approval is missing, present the reviewed proposal and ask in interactive
+mode; defer in unattended mode. General permission to update dependencies never
+approves an unspecified break. For each approval-dependent candidate record
+concrete effects, migration work, validation results or gaps, and release
+implications, trialing an isolated migration when useful. Continue independent
+work while a decision is pending; track accepted, declined, pending, and
+deferred decisions separately. Defer candidates with unknown impact or
+unvalidated migrations, and leave acceptable updates unapplied when they cannot
+be separated from an unauthorized change. Report missing credentials,
+permissions, and validation resources instead of bypassing them.
+
+Produce working-tree changes and a report suitable for later PR automation even
+when nothing can be applied. Do not manufacture changes, create workflows or
+pull requests, split work into PRs, bump repository versions, commit, push, tag,
+publish, or release.
+
+### Pacing
+
+Unattended runs have a turn limit, and a run that stops early publishes nothing.
+Finish Setup and steps 1 to 5 before steps 6 to 9 and the fresh-install
+exposure checks, and reserve budget for the report. Delegate per-package reviews
+when subagents are available. If budget runs short, skip the remaining optional
+work, list it in the report as not done, and write the report.
+
+## Version policy
+
+- **Third-party maturity:** a run introduces only releases at least 24 hours
+  old: Taze `--maturity-period 1` and Actions Up `--min-age 1` enforce it for
+  candidates, and pnpm's default `minimumReleaseAge` of 1440 minutes covers
+  resolution. Do not add or change `minimumReleaseAge` in `pnpm-workspace.yaml`,
+  never disable an installation safeguard, and never downgrade a previously
+  locked version to satisfy age.
+- **Authored packages:** npm packages and GitHub Actions owned by `kitschpatrol`
+  always target their latest stable release, including majors, however young.
+  They still get security and compatibility review and required migrations, but
+  age alone never causes an older target, a deferral, or a downgrade. The
+  commands below and the configuration policy's exact-version rules make the
+  exemption effective in Taze, pnpm, and Actions Up. If another policy blocks
+  latest, report the blocker and the retained version.
+- **Consumer ranges:** review the newest stable version allowed by each runtime
+  dependency's declared range, not only the locked version; consumers resolve
+  it regardless of this repository's lockfile and maturity settings. Holding one
+  back needs an approved, genuinely restrictive published range such as `~1.8.0`
+  instead of `^1.8.0`; an older lockfile or a local override is no substitute.
+- **No weakening:** never relax tests, lint rules, type checking, or security to
+  get a pass, and never accept changed snapshots or generated output unread.
+  Trace and report every new warning, deprecation, and peer issue against the
+  recorded baseline; the configuration policy defines the only permitted
+  suppressions.
 
 ## Environment
 
-Shell variables do not persist between commands. Save anything later steps need
-under `node_modules/.cache/ksc-update/` and pass values literally.
-
-Plan network access for `registry.npmjs.org`, `raw.githubusercontent.com`,
-`api.github.com`, and `nodejs.org`; identify any additional upstream hosts as
-needed. Prefer registry metadata and raw changelog files over GitHub API calls
-for package reviews. Cache responses and share them between reviewers.
-
-Under Claude Code's sandbox:
-
-- **pnpm store:** pnpm 12 cannot take its store lock inside the sandbox
-  (`ERR_PNPM_STORE_DIR_OPEN_OPERATION_LOCK`), even with writable store, cache,
-  and temp directories. `pnpm install`, `pnpm update`, `pnpm dedupe`,
-  `pnpx taze`, and `pnpx actions-up` must be listed in the user's
-  `sandbox.excludedCommands` and `permissions.allow`. If the Setup install fails
-  this way, stop the affected work and ask the user to add them in interactive
-  mode; in unattended mode, report the missing prerequisite. Do not route around
-  it. Run these commands bare (no pipes, redirects, or command substitution) so the
-  exclusions match. Run each as its own invocation, without `&&` or `||`.
-  Save captured tool output to log files in a separate operation.
-- **Proxy:** Node-based tools ignore the proxy variables. If one fails with
-  `ENOTFOUND`, rerun it with `NODE_USE_ENV_PROXY=1`.
-- **Sockets:** the `tsx` CLI cannot open its IPC socket. Run the same script
-  with `node --import tsx <script>` and report the substitution.
-- **GitHub API:** without `GITHUB_TOKEN`, GitHub allows 60 requests per hour.
-  One Actions Up run plus a few release-note lookups can exhaust it. The sandbox
-  cannot read `gh` credentials, so budget lookups or ask for a token in
-  interactive mode. In unattended mode, report any review blocked by missing
-  credentials or exhausted API limits.
-- **JSON output:** pnpm can emit `[WARN]` lines on stdout. Sync `packageManager`
-  before parsing pnpm JSON; if warnings remain, save them separately, remove
-  only lines beginning with `[WARN]`, and parse the rest strictly. Do not hide
-  malformed output or other diagnostics.
-- **Supply-chain settings:** an unreadable global config or `~/.npmrc` can make
-  a sandboxed config query return `undefined`; this does not mean the policy is
-  disabled. Read accessible workspace settings and record pnpm's successful
-  `Lockfile passes supply-chain policies` message from the actual install.
-  That message confirms the active checks passed, not the numeric release-age
-  threshold. Verify the required 1440 minutes from accessible configuration or
-  release timestamps when the effective setting cannot be read. Do not disable
-  safeguards or access private config through a workaround.
-
-## Setup
-
-1. Read repository instructions. Note uncommitted changes in the working tree
-   and preserve them. If files change during the run that you did not touch,
-   leave them alone and report them.
-   Read the `Known consumers` section in the project's `CLAUDE.md` or `AGENTS.md`.
-   Maintain a short section in the existing instruction file using confirmed
-   consumer names, local paths, consumed packages, test commands, and CLI
-   fixtures. If none are documented, ask for known consumers in interactive
-   mode; in unattended mode, report the missing information and use available
-   repository evidence. Continue independent review; do not invent consumers or
-   treat example paths as real. Report unavailable consumer validation as a gap.
-2. Map the workspace: root, every maintained package root, catalogs, overrides,
-   `pnpm-workspace.yaml`, Taze config. Exclude fixtures, generated files, and
-   dependency directories. Run each step once per shared-lockfile workspace and
-   separately in any independent package root. Check Taze config for anything
-   that overrides mode, adds maturity exemptions, or auto-writes/installs.
-   Record current project and published package versions to determine where the
-   zero-versioned exception applies.
-   Create the baseline folder and preserve the starting manifests and lockfile
-   before the package-manager sync or any other edit.
-3. Sync `packageManager` before installs and parsed pnpm output. Read the actual
-   installed pnpm from an empty directory so the project's stale pin cannot
-   select or download another version:
-
-   ```bash
-   pnpm --version
-   ```
-
-   Run that command with a new empty directory under `${TMPDIR:-/tmp}` as its
-   working directory. Then edit only the workspace root's `packageManager`
-   directly to `pnpm@<observed-version>`, preserving all other manifest fields.
-   Use the editor or a structured JSON edit, not `pnpm pkg set`; use direct
-   edits for later specifiers and engines too. pnpm commands can trigger
-   version-manager downloads after the pin changes. If this crosses a pnpm
-   major, report it and verify the CI installer supports the selected version.
-
-4. Install the starting dependency declarations and record a baseline before
-   dependency updates. Keep the original files saved in Setup 2 even if
-   installation fails.
+Expect Claude Code in GitHub Actions with Node.js, pnpm and pnpx, curl, jq, git,
+Bash, and network access to `registry.npmjs.org`, `raw.githubusercontent.com`,
+`api.github.com`, `nodejs.org`, and upstream documentation hosts. Prefer
+registry metadata and raw changelogs over GitHub API calls, and cache responses
+for reuse between reviewers. Diagnose actual failures rather than assuming
+sandbox restrictions, and never add sandbox workarounds.
+
+The run directory is `${RUNNER_TEMP:-${TMPDIR:-/tmp}}/ksc-update/`. Keep every
+baseline, log, fetched metadata file, and decision record there; it survives
+pnpm rebuilding `node_modules` and never enters the pull request. Preserve exit
+codes when capturing logs, for example with `set -o pipefail` before
+`cmd 2>&1 | tee log`.
+
+### Bundled scripts
+
+`scripts/` holds helpers for the mechanical parts of a run. Each documents its
+usage in a header comment; the references say where each fits.
+
+| Script                   | Purpose                                                       |
+| ------------------------ | ------------------------------------------------------------- |
+| `consumer-ranges.mjs`    | Newest version each published runtime range allows (step 3)   |
+| `release-age.mjs`        | Exemption inventory and young-version detection (steps 0–6)   |
+| `production-engines.mjs` | Declared engines across a production tree                     |
+| `packed-fixture.mjs`     | Packed or published consumer fixture install                  |
+| `run-at-node.mjs`        | Command at an exact Node.js release, with child-process proof |
+| `compare-outputs.mjs`    | Normalized comparison of captured outputs and build trees     |
+
+The scripts are conveniences, not requirements; the procedures they serve are.
+When one fails for a reason that is not the repository's fault, produces output
+that disagrees with what direct inspection shows, or does not fit this
+repository's layout, make at most one quick attempt to understand why, then
+abandon it: write a replacement for that step in the run directory, or do the
+step by hand, and continue. Never let a broken helper stall the run, never edit
+the bundled copy during a run (it is synced from the published package and
+overwritten), and never weaken a check to make a script pass. Name each
+abandoned or replaced script and the reason in the report's gaps so it can be
+fixed upstream. Verify any script's result against one or two direct
+observations before relying on it.
+
+## Step 0: Setup
+
+1. Read repository instructions, including run-specific instructions, and
+   preserve uncommitted changes. Run-specific instructions also live in the
+   `instructions:` input of the skill-running step in
+   `.github/workflows/update-dependencies.yml`; read it even when running
+   locally, where the workflow does not pass it, and follow it as if it had
+   been. Leave files changed by others during the run alone and report them.
+   Keep compatibility validation inside this repository and isolated
+   package-install fixtures. Record the latest release tag and the commits
+   since it (`git describe --tags --abbrev=0`, then `git log <tag>..HEAD`);
+   they explain differences between the published release and the current
+   build and feed the release recommendation.
+2. Map maintained package roots, shared lockfiles, catalogs, overrides,
+   `pnpm-workspace.yaml`, and Taze config, excluding fixtures, generated files,
+   and dependency directories. Run the workflow once per shared-lockfile
+   workspace and separately for each independent root. Check Taze config for
+   mode overrides, maturity exemptions, and automatic writes or installs; Taze
+   and `pnpm update` also read `minimumReleaseAge`, `minimumReleaseAgeExclude`,
+   and `update.ignoreDeps` from `pnpm-workspace.yaml`. Record project and
+   published package versions. Before any edit, copy the starting manifests,
+   lockfile, build approvals, and exact `publicHoistPattern` into the run
+   directory, and inventory release-age exclusions as the configuration policy
+   describes; `scripts/release-age.mjs inventory` classifies each entry once
+   the authored list from item 5 exists.
+3. Sync the workspace root's `packageManager` before any install or parsed pnpm
+   output: fetch the [Homebrew pnpm formula](https://raw.githubusercontent.com/Homebrew/homebrew-core/refs/heads/main/Formula/p/pnpm.rb),
+   read the stable version from its source URL or explicit `version`, and set
+   `pnpm@<homebrew-version>` by direct manifest edit, even across a major.
+   Homebrew is the only source and need not be installed; never substitute the
+   installed pnpm, npm's `latest` tag, or an age-filtered version, and report an
+   unavailable or unreadable formula as an incomplete sync. Review pnpm release
+   notes for lockfile and settings changes, confirm CI installs the selected
+   version, and record the formula URL and version. Make all later specifier
+   and engine changes by direct edit too, preserving other fields.
+4. Apply the configuration policy's build-trust decisions and exclusion
+   normalization, then install the starting declarations:
 
    ```bash
    pnpm install --frozen-lockfile
    ```
 
-   On `ERR_PNPM_OUTDATED_LOCKFILE` only, run this as a separate bare command:
-
-   ```bash
-   pnpm install --no-frozen-lockfile
-   ```
+   Use `--no-frozen-lockfile` only for `ERR_PNPM_OUTDATED_LOCKFILE` and diagnose
+   every other failure individually; a pnpm major change can require a lockfile
+   format migration, which is expected drift to record. Keep the saved originals
+   even if installation fails, and label checks after a repair as repaired.
+   Record the [baseline](references/verification.md#baselines): install
+   attempts, build, test, lint, build artifacts, Node.js requirements, the
+   production-engine inventory, the advisory report, and packed-install fixture
+   results.
 
-   Save the lockfile diff against the starting copy in the baseline folder and
-   report the drift. Treat checks after repair as the repaired baseline, not as
-   proof that the original locked tree passed. Other installation failures need
-   their own diagnosis; do not generalize this fallback or relax safeguards.
-
-   Save the output of each install attempt and of `pnpm build`, `pnpm test`, and
-   `pnpm lint` to `node_modules/.cache/ksc-update/baseline/`. If the repository
-   produces build output (`dist/` or similar), copy it there as well. Use the
-   repository's switches to disable nondeterministic build steps (encryption,
-   timestamps) and note the exact command and environment; later comparison
-   builds must match them. Baseline failures are pre-existing; record them.
-
-   Record each published package's declared `engines.node`, effective consumer
-   Node.js minimum and supported range, and separate development requirement.
-   Include published dependency trees and built artifacts, not just the root
-   manifest or current CI runtime. If no Node.js support policy is declared,
-   establish the existing requirement from the published code and dependencies;
-   do not assume the developer's Node.js version is the consumer minimum.
-   Save production-tree engine inventories and baseline consumer results using
-   [the verification recipes](references/verification.md). Distinguish the
-   starting locked tree, the newest versions a fresh consumer install can
-   resolve, and the published release with its old dependencies when available.
-
-5. Discover authored packages:
+5. Discover authored packages, those whose registry metadata lists
+   `kitschpatrol` in `maintainers`. The ownership endpoint is a shortcut for the
+   full list:
 
    ```bash
    set -euo pipefail
-   mkdir -p node_modules/.cache/ksc-update
+   run_dir="${RUNNER_TEMP:-${TMPDIR:-/tmp}}/ksc-update"
+   mkdir -p "$run_dir"
    curl -fsS https://registry.npmjs.org/-/user/kitschpatrol/package \
      | jq -er 'keys | join(",") | select(length > 0)' \
-       > node_modules/.cache/ksc-update/authored-packages.txt
+       > "$run_dir/authored-packages.txt"
    ```
 
-   If registry discovery fails or returns empty, stop and report. Intersect the
-   result with direct dependency names across the maintained manifests in this
-   workspace, including dev, optional, and peer dependencies and dependencies
-   using catalogs or npm aliases. Save the intersection separately; an empty
-   intersection is valid. `<authored-packages>` below means only those exact
-   matching names, comma-separated and passed literally, with no wildcards.
-   Omit `--maturity-period-exclude` if the intersection is empty. Keep the full
-   ownership list only for evaluating other packages encountered later.
+   If it fails or returns nothing, check each direct dependency's registry
+   metadata instead and report the fallback; do not stop the run. Intersect
+   ownership with the direct dependency names across maintained manifests,
+   including dev, optional, peer, catalog, and npm-alias dependencies, and save
+   that intersection separately; it may be empty. `<authored-packages>` below
+   means those exact names, comma-separated, with no wildcards; omit
+   `--maturity-period-exclude` when the list is empty. Keep the full ownership
+   list for packages met later.
 
-## 1. Workflow actions
+## Step 1: Workflow actions
 
 ```bash
-pnpx actions-up --yes --min-age 1 --style sha
+pnpx actions-up --yes --min-age 1 --min-age-exclude '^kitschpatrol/' --style sha \
+  --dir .github
 ```
 
-Read the whole output. Actions Up can print "All actions are up to date!" after
-checks failed; any `Skipped`, `Failed`, or `Rate Limit` line means the run is
-incomplete. Fix the cause and rerun.
+Add a `--dir` for every other directory of workflows the repository maintains or
+ships, such as templates that an init command copies into consumer projects
+(for example `packages/*/init/.github`); by default only `.github` is scanned.
+Find them with a search for `workflows` directories outside dependency and
+fixture folders.
+
+`Skipped`, `Failed`, or `Rate Limit` anywhere in the output means incomplete,
+even beside "All actions are up to date"; fix the cause and rerun, and report
+unresolved access or service failures instead of claiming success.
 
-Review the diff: major action bumps, runner, input, output, and permission
-changes. Every external GitHub Action and reusable workflow must be pinned to
-its full commit SHA, including `kitschpatrol/*`; retain version comments for
-readability. Do not exclude first-party actions from pinning or allow their
-floating refs in zizmor's `unpinned-uses` policy. Resolve skipped branch/tag
-refs and unchanged versions to verified commits too; if an update is deferred,
-pin the retained version. Check existing zizmor configuration for exceptions
-that contradict this policy. Pin container actions by digest; local `./` actions
-use the checked-out tree. Keep only reviewed changes without disturbing user
-edits. Local tests say nothing about remote workflows.
+Review major bumps and runner, input, output, and permission changes. Pin every
+external action and reusable workflow, including `kitschpatrol/*`, to a verified
+full commit SHA with its version comment, covering branch and tag refs,
+unchanged versions, and the retained version of a deferred update. Pin container
+actions by digest; local `./` actions use the checkout. Remove zizmor
+`unpinned-uses` exceptions the pins make contradictory. Keep only reviewed
+changes and preserve user edits; local tests do not validate remote workflows.
 
-## 2. Discover all candidates (read-only)
+## Step 2: Discover candidates
 
 ```bash
 pnpx taze major -r --force --include-locked \
@@ -284,134 +243,88 @@ pnpx taze major -r --force --include-locked \
   --maturity-period-exclude '<authored-packages>'
 ```
 
-Major mode lists every available update, minor and major. Confirm authored
-packages are offered their latest stable release, not the latest within their
-current major. Do not opt into new prerelease channels. Taze's newest candidate
-does not replace the separate newest-in-range runtime review in step 3.
-
-## 3. Evaluate candidates
-
-### Runtime ranges and review scope
-
-For each runtime dependency of a published package, inspect registry metadata
-for the newest stable version satisfying its current declared range, accounting
-for catalogs and aliases. Record declared range, locked version, newest allowed
-version, and proposed range/version. Review that newest allowed release even
-if it is already in range or too young for this run to install; consumer
-package managers may not enforce this repository's maturity policy. Keep the
-installation safeguards and report any untested consumer exposure.
-
-Review direct candidates and production-tree changes fully. For development-only
-transitives, check advisories, deprecations, and engines; investigate release
-notes only when those checks, validation failures, or output differences give
-cause. A package bundled or shipped with a CLI/config package belongs to the
-consumer review even if this repository also uses it as development tooling.
-
-An in-range behavior change may already reach the published release's consumers.
-Do not describe an older lockfile as protecting them or infer a new breaking
-release solely from the lockfile movement. Test the published release and
-updated build against actual consumer resolution, and separately preserve the
-old locked baseline. To hold back an incompatible allowed release, present a
-specific narrower range and obtain the policy's required approval.
-
-### Breaking candidates
-
-Track breaking-candidate decisions throughout the run; report applied breaks
-and deferred opportunities separately.
-For each candidate, identify affected APIs, behavior, Node.js support, known
-consumers, migration work, validation results or gaps, and release implications.
-Prepare a concrete proposal and, where useful, validate a trial migration in an
-isolated copy before seeking a decision. For stable projects in interactive
-mode, ask explicitly whether to accept each reviewed break unless that exact
-scope was already authorized; continue independent updates while awaiting the
-answer. In unattended mode, defer unapproved stable-project breaks and include
-them under `Breaking changes available` in the report without asking. General
-permission to update dependencies is not approval for an unspecified break.
-For `0.x` projects, both modes authorize reviewed breaking migrations without
-another question, but runtime-range narrowing still needs explicit approval.
-Record accepted, declined, pending, and deferred decisions separately.
+Major mode lists every update size; confirm authored candidates are the latest
+stable across majors. Do not opt into new prerelease channels.
+`--include-locked` surfaces exact pins without authorizing their removal;
+`@types/node` and `pnpm` are managed by the configuration policy and Setup. This
+discovery does not replace the consumer-range review in step 3.
+
+## Step 3: Evaluate candidates
+
+### Scope and consumer ranges
+
+For every runtime dependency of a published package, read registry metadata for
+the newest stable version its declared range allows, accounting for catalogs and
+aliases, and record the range, locked version, newest allowed version, and
+proposed range or version. Review the allowed release even when it is already in
+range or too young to install here, and report untested consumer exposure. Keep
+the published release's fresh-install behavior, the updated build, and the old
+locked baseline distinct; existing in-range exposure is not a break introduced
+by this release. `scripts/consumer-ranges.mjs` builds this table from the
+workspace root and flags rows where consumers resolve something newer than the
+lockfile or something too young to install here; resolve catalog specifiers it
+marks for manual review by hand.
+
+Review direct candidates and production-tree changes fully; shipped or bundled
+tooling belongs to consumer review even when used only for development here.
+For development-only transitives, check advisories, deprecations, and engines,
+and read release notes when those findings, validation failures, or output
+differences warrant it. A full review reads release notes, migration guides, and
+advisories and assesses:
+
+- Security fixes or regressions, publishing or ownership anomalies, and new
+  install scripts or permissions.
+- APIs, types, defaults, configuration, module format, peers, and engines
+  against actual repository usage and the versions this update produces,
+  reviewing coupled packages together since one update may need a newer
+  sibling.
+- Adoptable fixes, performance, capabilities exposed to consumers, and optional
+  feature opportunities for the report. Do not implement extra features.
+
+When delegating, split independent reviews among authored packages, remaining
+runtime packages, and remaining development packages. Give each reviewer a
+disjoint list, actual usage and source paths, consumer requirements, and the
+version policy; reviewers return decisions and sources without editing, the
+primary agent resolves coupling, and all share fetched metadata and the GitHub
+API budget.
+
+Record current and proposed versions, decision, evidence, and approval scope per
+the authorization table. Do not defer a migration merely because it implies a
+major release recommendation. Review exact pins under
+[Version declarations](references/configuration.md#version-declarations).
 
 ### Node.js compatibility
 
-For every candidate, minor and patch included, distinguish consumer requirements
-from development requirements:
-
-- **Consumers:** for projects at 1.0.0 or later, keep the user-facing Node.js
-  minimum and supported range unchanged unless explicitly approved under
-  `Breaking candidates`. A higher effective consumer minimum or loss of any
-  supported Node.js version is a break even if `engines.node` is left unchanged.
-  Check direct, transitive, optional, peer, and workspace dependencies used by
-  published packages, plus bundled code, emitted syntax, and runtime APIs.
-  A tool used only for development here is still a consumer dependency if it
-  ships in a published CLI or configuration package. Compare
-  full engine ranges, not just the lowest version in each range.
-  For authorized breaks or zero-versioned projects, update published
-  `engines.node` to reflect the actual supported range and validate against it.
-- **Development:** a higher Node.js requirement for development-only tools,
-  builds, or CI is allowed when published artifacts remain compatible. If it
-  exceeds the consumer requirement, add or update the Node.js entry in the
-  relevant `package.json`'s `devEngines.runtime` with `name: "node"` and a
-  `version` range covering the actual development requirement. Use the workspace
-  root for shared tooling and package manifests for package-specific tooling;
-  preserve other runtime entries and settings. This is the development Node.js
-  dependency notice; do not raise published `engines.node` to satisfy dev tools.
-  Align development version pins and build CI as needed while retaining consumer
-  compatibility checks at the applicable supported minimums (the original ones
-  unless an approved break or the zero-versioned exception changes them).
+For every candidate, including minors and patches, check consumer and
+development requirements separately:
+
+- **Consumers:** compare full supported Node.js ranges across direct,
+  transitive, optional, peer, and workspace dependencies, bundled code, emitted
+  syntax, and runtime APIs. A higher effective minimum or a lost supported line
+  is a break even when `engines.node` is unchanged. Preserve the contract under
+  the authorization table; for accepted changes publish truthful engines in the
+  [LTS-only shape](references/configuration.md#nodejs-support) and validate the
+  resulting range.
+- **Development:** higher requirements for development-only tools, builds, or
+  CI are fine while artifacts stay consumer-compatible. When they exceed
+  consumer requirements, add or update `devEngines.runtime` with `name: "node"`
+  and the actual range, at the root for shared tooling and in package manifests
+  for package-specific tools, preserving other entries. Align development pins
+  and CI while keeping tests at the applicable consumer minimums. Never raise
+  published `engines.node` for development tooling.
 
 ### TypeScript migrations
 
-Read the accepted `@kitschpatrol/typescript-config` release's TypeScript peer
-range and base configuration. If it requires a new compiler major, offer that
-migration with its concrete effects rather than automatically deferring the
-authored update. Apply it within existing authorization; ask only for additional
-breaking or Node-types changes that the policy actually requires approval for.
-
-- Add `"node"` to `compilerOptions.types` where Node globals are needed,
-  preserving other required type entries and the separation from browser code.
-- Fix errors exposed by newly enabled strict options; do not disable those
-  options just to pass.
-- Check the new base `lib`, emitted syntax, declarations, and APIs used by
-  shipped code against the consumer Node.js floor and browser targets. A newer
-  `lib` can make unavailable APIs type-check; it does not polyfill them.
-
-Run type checks, build, and consumer validation after the migration, retaining
-the distinction between development and consumer Node.js requirements.
-
-### Compatibility review
-
-For direct candidates and production-tree changes, read relevant upstream
-release notes, migration guides, and advisories, and assess:
-
-- **Security:** vulnerabilities fixed or introduced, ownership or publishing
-  anomalies, new install scripts or permissions.
-- **Breaking:** APIs, types, defaults, configuration, module format, peer
-  ranges, runtime requirements, measured against this repository's actual use.
-- **Coupling:** peer and engine requirements against the versions this update
-  will produce, not the current ones. A major can require a newer minor of a
-  sibling package (`@astrojs/mdx` 8 requires `astro` 7.2.10 or later).
-- **Worth it:** fixes and performance adoptable under the version policy.
-  Note features exposed by the update and optional feature opportunities for the
-  report; do not implement new features as extra work.
-
-When delegation is available, run independent release-note reviews in parallel,
-split into authored packages, remaining runtime packages, and remaining direct
-development packages. Give each reviewer its disjoint package list, a short
-survey of actual usage and relevant source paths, consumer requirements, and
-the version policy. Reviewers return decisions and sources without editing
-dependencies; the primary agent resolves coupling and combines the results.
-Share cached metadata and the GitHub API budget. Review sequentially when
-delegation is unavailable.
-
-Record current → proposed version, decision, and sources. Accept only when
-compatibility is preserved, an explicit approval covers the break, or the
-zero-versioned exception permits it; defer the rest with a reason. Do not
-defer a migration merely because it needs a major release recommendation.
-
-## 4. Apply
-
-Apply only accepted candidates, including minors and patches, by exact package
-name. Major mode can apply all accepted update sizes:
+Follow the [tsconfig.json policy](references/configuration.md#tsconfigjson)
+with the accepted config release. When an authored update needs a newer compiler
+major, offer that migration with its concrete effects instead of deferring the
+update, apply it within the authorization table, then run type checks, the
+build, and packed-install validation.
+
+## Step 4: Apply
+
+Apply accepted candidates by exact package name, replacing the example list;
+skip this when nothing was accepted:
 
 ```bash
 pnpx taze major -rw --force --include-locked \
@@ -422,265 +335,138 @@ pnpx taze major -rw --force --include-locked \
   --maturity-period-exclude '<authored-packages>'
 ```
 
-Replace the example names with the accepted set; skip the command if it is
-empty. If only an older compatible target was accepted, set that reviewed
-version manually instead of letting Taze choose the latest. Then check the
-diff: every manifest and catalog covered, only reviewed versions applied, no
-excluded or deferred update slipped in, range style and `workspace:` references
-intact. A package accepted in one workspace package is not automatically
-accepted in every other one. Hand-edit anything Taze missed (catalogs,
-overrides), and add any required development Node.js notice. Use direct edits
-for reviewed compiler versions inside the required peer range and for
-authorized Node-types changes; do not let Taze choose an incompatible compiler.
-Verify `packageManager` remains at Setup's selected version.
+Set a reviewed older target by direct edit when latest was not accepted.
+Acceptance in one workspace package does not apply to the others. Afterwards
+check every manifest and catalog: only reviewed versions, range styles and
+`workspace:` references intact, no deferred or excluded updates. Directly edit
+missed catalogs and overrides, the reviewed compiler and Node-types versions,
+and development Node.js notices. Apply the configuration policy's manifest rules
+and keep Setup's `packageManager`.
 
-## 5. Resolve and validate
+## Step 5: Resolve and validate
 
-Run each command as a separate invocation:
-
-```bash
-pnpm update -r
-```
+Before anything can run install scripts, apply build-trust decisions, review
+overrides and peer rules, and add the exact release-age exemptions that accepted
+young authored targets need, all under the
+[pnpm-workspace.yaml policy](references/configuration.md#pnpm-workspaceyaml).
+Then resolve:
 
 ```bash
+pnpm update -r --no-save
 pnpm dedupe --check
 ```
 
-Inspect the result. If it reports available deduplication, run the following
-separately; other failures need diagnosis, not an unconditional retry:
-
-```bash
-pnpm dedupe
-```
-
-Then run the checks, each separately:
-
-```bash
-pnpm build
-pnpm fix
-pnpm build # only if fix changed source files
-pnpm test
-pnpm lint
-```
-
-Always use bare `pnpm update -r` for the full refresh, without package selectors.
-Named-package updates do not provide the same transitive refresh; do not use
-`!pkg` selectors as a workaround for deferred candidates. It resolves within
-the written ranges and rechecks release age without discarding `node_modules`.
-In pnpm 12 it can also raise range floors in `package.json` and catalogs
-(for example, `^1.8.0` to `^1.9.0`), so review the manifest and catalog diffs
-after every update, not just the lockfile. Preserve excluded declarations and
-undo unreviewed range changes by direct edits, then synchronize the lockfile.
-
-Deduplication consolidates compatible references onto newer versions already
-in the tree; it is not a way to hold back or downgrade a dependency. Review
-production changes fully and development-only transitives under step 3's
-narrower checks. If a deferred version is still allowed by a published runtime
-range, use the explicit range/consumer decision path rather than fighting the
-resolver with an older lockfile or an unapproved override.
-If an authored release is blocked by `minimumReleaseAge`, add only that
-package/version to `minimumReleaseAgeExclude`; never its dependencies.
-
-Compare every result with the baseline:
-
-- **Consumer compatibility:** recheck the resolved published dependency trees
-  and build artifacts against the Node.js baseline, including transitive
-  changes from resolution or deduplication. Validate consumer installation and
-  representative runtime behavior at the applicable supported minimums separately
-  from checks needing the newer development runtime. Review `pnpm fix` changes
-  to `engines.node` and `devEngines.runtime`; a passing fixer or build on newer
-  Node.js does not establish consumer compatibility. Diff the production-engine
-  inventories, test the packed build in known consumers, and run fixtures at the
-  exact supported Node.js floor using [the verification recipes](references/verification.md).
-  For stable projects, do not retain a newly introduced break outside explicit
-  approval; present the candidate or defer it. Do not mask it with an unapproved
-  `engines.node` increase. For authorized breaks and zero-versioned projects,
-  validate the new contracts and Node.js range and report the baseline changes.
-- **Logs:** for each new warning, deprecation, or peer issue, find the package
-  that introduced it (`pnpm why`) and search upstream for a known issue. Report
-  it with the link. For a peer declaration lagging a verified compatible
-  version, offer a scoped `peerDependencyRules.allowedVersions` entry such as
-  `"parent@range>peer": "tested-range"` in `pnpm-workspace.yaml`, explaining
-  that it suppresses a warning rather than fixing incompatibility. Show the
-  exact entry and evidence, and ask before applying unless already authorized.
-  Do not use broad `allowAny` or disable strict peer checks. Revisit such
-  workarounds during step 8.
-- **Build output:** if the baseline includes build output, rebuild with the
-  same command and environment and diff the trees with content-hashed filenames
-  normalized (`name.[hash].js`). Explain every remaining difference with an
-  upstream changelog entry, issue, or reviewed migration/configuration change;
-  anything unexplained needs investigation. Unless explicitly configured,
-  tsdown derives its build target from `engines.node`, so an engine change can
-  legitimately alter emitted syntax. Record the effective targets before and
-  after, distinguish expected output changes from regressions, and check runtime
-  APIs separately because syntax lowering does not provide polyfills.
-- **After `pnpm fix`:** review the diff, then rebuild and diff against the
-  pre-fix build. Formatting changes must produce identical output. A lint
-  rule's suggested fix can change behavior (default parameters do not replace
-  `null`); in that case keep the code and add an inline disable that says why.
-  If the project can or is likely to run in browsers, including alongside
-  Node.js, disable the offending rule for the affected shipped code when its
-  fix would introduce regex flags or DOM APIs unsupported by the project's
-  browser targets. Explain the compatibility reason and keep the compatible
-  code instead of applying the fix; revert the fix if already applied. This
-  also applies to zero-versioned projects, but does not apply to Node.js-only
-  projects.
-  Resolve remaining lint errors by hand.
-
-On failure, make the smallest change consistent with the version policy and
-rerun from the failing step:
-
-- To tell a new failure from a pre-existing one, check the baseline logs.
-  `git stash` does not revert `node_modules`, so rerunning a check after
-  stashing still uses the new dependencies.
-- To isolate a breaking update: set half the accepted updates back to their
-  previous specifiers, `pnpm update -r`, rerun the failing check, repeat.
-  For an out-of-range update, defer the culprit unless an approval or the
-  zero-versioned exception permits it and the migration resolves the failure.
-  For an already allowed runtime release, follow the range decision path in
-  step 3; resetting a specifier or lockfile may not exclude it.
-
-Add focused tests only where a compatibility change touches behavior not
-already covered. Review `readme.md` accuracy and automation opportunities in step 7.
-
-## 6. Exclusion cleanup
-
-Only if `minimumReleaseAgeExclude` is non-empty in any `pnpm-workspace.yaml`
-(at the start, or after step 5). Empty the list (`[]` or remove the key),
-preserving neighboring keys and comments. Repeat step 5's separate bare
-`pnpm update -r` and `pnpm dedupe --check` invocations, followed by a separate
-`pnpm dedupe` only when the check reports available changes. Then run each check
-separately:
-
-```bash
-pnpm build
-pnpm test
-pnpm lint
-```
-
-If `pnpm-lock.yaml` comes out byte-identical and no ranges or build settings
-changed, the installed tree did not change; rerun only `pnpm lint`.
-
-If resolution is blocked: for an authored release, re-add the narrowest
-package/version entry; for a third-party release, choose a mature version or
-defer that upgrade. Obtain approval if that choice requires narrowing a
-published runtime range. Never restore the whole previous list.
-
-If the list was empty throughout, skip this section and continue to step 7.
-If cleanup changes resolution, repeat step 5's consumer compatibility review
-before reviewing documentation.
-
-## 7. Documentation review
-
-Review `readme.md` against the updated project. Correct stale installation
-instructions, requirements, commands, examples, configuration guidance, and
-feature descriptions. If `readme.md` is generated or copied from another file,
-update its maintained source and regenerate it through the existing workflow.
-
-Review each section for content that would be more reliably maintained through
-mdat, especially content duplicated from package metadata, CLI help, source
-files, or other documentation. Prefer a rule bundled with mdat when it fits,
-then a suitable mdat plugin, or a custom rule in `mdat.config.ts` for
-project-specific needs. Check the installed rules and relevant documentation
-before choosing an implementation. Replace manually maintained sections where
-generation reduces duplication or prevents drift while preserving their useful
-content and readability; keep explanatory prose manual when automation adds
-no benefit. Any new plugin dependency must satisfy the dependency review,
-release maturity, and compatibility policies above.
-
-Run the project's mdat generation and documentation checks, inspect the
-rendered content for accuracy, and confirm that a second generation produces
-no further changes. Validate any new dependency under steps 5 and 6 before
-continuing. Include documentation corrections and mdat conversions in the
-final report.
-
-## 8. @kitschpatrol/shared-config override minimization
-
-Run this as the final cleanup after all accepted updates, migrations,
-validation, release-age exclusion cleanup, and documentation review, before
-the release recommendation and report.
-
-Review every shared-config-related configuration file in the project root,
-including dotfiles, companion ignore files, and configuration stored in
-`package.json`. Include the individual `@kitschpatrol/*-config` packages used by
-the project. Inventory every local override beyond the upstream default export
-or equivalent base configuration: rule settings, options, ignores, file globs,
-and other customizations.
-Include scoped peer-warning workarounds added during the update; remove them
-when upstream peer declarations now cover the tested versions.
-
-For each override, compare it with the defaults and effective configuration of
-the exact versions installed after the updates. Check the current code it
-targets and, for upstream workarounds, the relevant upstream changes or fixes.
-Remove overrides that duplicate current defaults, target code or files that no
-longer exist, or compensate for issues now fixed upstream. Do not infer that an
-override is redundant merely because checks pass while it is still enabled.
-
-Validate removals in small groups using the affected tools' checks without
-caches, covering the affected files and any files newly included by removing
-ignores. Recheck effective configuration where merge order or file matching
-matters. Keep overrides that still serve a concrete project requirement,
-including the behavior and browser-compatibility protections from step 5, and
-record why each is needed. If necessity cannot be established, retain the
-override and report the unresolved evidence instead of guessing.
-
-After changing configuration, rerun the affected build, test, type, and lint
-checks and compare results and build output as in step 5. The final report must
-account for every override: removed with evidence, retained with a current
-justification, or unresolved with the missing evidence identified.
+`pnpm update -r --no-save` refreshes every direct and transitive dependency
+within the declared ranges without rewriting manifests or catalogs; named
+updates and `!pkg` selectors do not give that transitive refresh. Run
+`pnpm dedupe` only when the check reports available deduplication, and diagnose
+other failures; deduplication moves compatible references onto newer versions
+already in the tree and cannot hold back a deferred release. Review newly
+resolved packages under step 3, apply the consumer-range decision to deferred
+in-range runtime releases, and confirm after each resolution that authored
+packages reached their accepted targets, investigating mismatches with the
+configuration policy's maturity procedure rather than assuming an age holdback.
+After each resolution, run `scripts/release-age.mjs new-versions` against the
+saved pre-resolution lockfile to list young versions it introduced, and diff
+`minimumReleaseAgeExclude` against the entries you added: pnpm appends entries
+itself when it falls back to young versions, and each one needs the policy's
+review.
+
+Run the [validation procedure](references/verification.md#updated-validation):
+build, fix, rebuild when needed, test, lint, baseline and output comparison,
+warning review, advisory comparison, packed consumer installs, and exact-floor
+checks. Apply the configuration policy's compatibility fixes and warning rules.
+Keep only changes the authorization table permits, revise decisions when
+validation reveals a break, and add focused tests only for affected behavior
+that is not already covered.
+
+## Step 6: Exclusion cleanup
+
+If `minimumReleaseAgeExclude` was ever non-empty during the run, follow the
+[release-age cleanup](references/configuration.md#release-age-exemptions), which
+is version-preserving and names its own validation.
+
+## Step 7: Side effects
+
+Evaluate each published package's shipped code against its `sideEffects`
+declaration under the [side-effects policy](references/configuration.md#side-effects),
+recording evidence and outcome even when nothing changes.
+
+## Step 8: Documentation
+
+Review `readme.md` for stale installation instructions, requirements, commands,
+examples, configuration guidance, and feature descriptions; for generated or
+copied readmes, edit the maintained source and regenerate through the existing
+workflow, never by running mdat from a different package's directory. Convert
+sections that duplicate metadata, CLI help, source files, or other documentation
+to mdat generation where that reduces duplication or drift without hurting
+readability, preferring a bundled rule, then a suitable plugin, then a custom
+rule in `mdat.config.ts`; keep explanatory prose that automation adds nothing
+to. New plugin dependencies get the same review as any other candidate and go
+through steps 5 and 6. Run generation and documentation checks, inspect the
+rendered result, confirm a second generation changes nothing, and record
+corrections and conversions.
+
+## Step 9: Final configuration cleanup
+
+Recheck the complete configuration policy against the final tree and perform
+[override minimization](references/configuration.md#final-override-minimization).
+Run affected fixers and checks after the last edit, and account for every
+override before recommending a release.
 
 ## Release recommendation
 
-Recommend `patch`, `minor`, or `major` from the final consumer-visible changes,
-following the repository's release conventions. Do not infer the recommendation
-from the largest dependency version bump:
-
-- **Patch:** compatible bug or security fixes, performance improvements, or
-  dependency/tooling maintenance with no new consumer-facing capability. A
-  development-only Node.js increase with the required notice can remain a patch.
-- **Minor:** backward-compatible functionality or capabilities actually exposed
-  to consumers by the accepted updates. Explain what consumers gain; an upstream
-  minor or major alone is not a reason for a minor release. For zero-versioned
-  projects, also recommend a minor release for accepted consumer-facing breaking
-  changes unless the repository's pre-1.0 release conventions specify otherwise.
-- **Major:** explicitly approved consumer-facing breaks in projects at 1.0.0
-  or later, including a raised consumer Node.js floor. A dependency major or
-  development-only requirement by itself does not justify a project major.
-
-Give a short rationale per affected published package, or one recommendation
-for a shared release version using the highest applicable level. If nothing
-releasable changed, say no release is needed. An approved major release is
-within scope; an unapproved breaking candidate stays pending or deferred.
-For `0.x`, accepted consumer breaks normally require a minor, not a patch;
-follow an explicit repository convention if it differs. Assess changes already
-reachable through the old published ranges separately from newly introduced
-consumer breaks. Recommend only; do not bump repository versions.
+Recommend from the final consumer-visible changes, following repository
+conventions, with a rationale per published package or the highest level for a
+shared release:
+
+- **Patch:** compatible bug and security fixes, performance, and dependency or
+  tooling maintenance without new consumer capability, including
+  development-only Node.js increases with their notice and corrected or newly
+  added `sideEffects` declarations.
+- **Minor:** backward-compatible functionality actually exposed to consumers;
+  explain the gain. For `0.x`, also accepted consumer breaks unless explicit
+  pre-1.0 repository conventions differ.
+- **Major:** authorized consumer breaks in packages at 1.0.0 or later, including
+  a raised Node.js floor or a declared line removed by the LTS-only range.
+
+Dependency version labels and development-only requirements never decide the
+level. Separate pre-existing exposure through published ranges from new breaks.
+Say that no release is needed when nothing releasable changed, and leave
+repository versions unchanged.
+
+The next release also ships every unreleased commit recorded in Setup. Give the
+level this run's changes need and, when the unreleased commits raise it, the
+level for the next release overall, citing those commits.
 
 ## Report
 
-State the execution mode and why it was selected. Include a `Breaking changes
-available` section for deferred breaking candidates: current and proposed
-versions, affected consumers/contracts, required migration, validation results
-or gaps, recommended release level, and the decision still needed. Distinguish
-these from applied breaks authorized explicitly or by the `0.x` policy. In
-unattended mode, record decisions needed as follow-up items, not questions or
-pending waits. Report unavailable checks and blocked work even when independent
-updates succeeded.
-
 Review the full diff for unrelated changes, excluded-package edits, and stray
-exemptions first. Then summarize: applied updates; major decisions with
-sources; consumer impact, approvals, declined/deferred decisions, and breaks
-accepted under the zero-versioned policy;
-output differences and their upstream or migration explanations;
-consumer Node.js requirements before and after, development Node.js changes and
-their `devEngines.runtime` notices; the release recommendation and its rationale;
-baseline lockfile drift; runtime ranges, fresh-install exposure, and approved
-range restrictions; TypeScript migrations; new warnings and scoped peer
-workarounds; what was validated, at which exact Node.js versions, and in which
-known consumers, including CLI/fixture comparisons and unavailable baselines;
-remaining `minimumReleaseAgeExclude` entries with reasons; deferred upgrades,
-documentation corrections and mdat conversions;
-shared-config overrides removed or retained with their justifications and any
-unresolved override reviews; unresolved failures, checks that could not run,
-and steps run differently because of the environment. Passing checks do not
-prove the absence of breaking changes. Leave everything uncommitted.
+exemptions. Start the report with a summary of at most ten lines: what was
+applied, the release recommendation per package, and the decisions needed. Raw
+logs stay in the run directory. Then cover, from the decisions and evidence
+recorded above and in both references:
+
+- **Updates and decisions:** execution mode and reason, applied versions with
+  sources, approvals and applied breaks including `0.x`, declined and deferred
+  candidates, migrations, and optional feature opportunities. Under a
+  `Breaking changes available` heading list each deferred break's versions,
+  consumer impact, migration, validation or gaps, release level, and the
+  decision needed.
+- **Consumer impact and release:** runtime ranges and fresh-install exposure,
+  approved restrictions, consumer Node.js before and after, development
+  requirements and notices, TypeScript migrations, and the release
+  recommendation with rationale.
+- **Maintenance:** the Homebrew pnpm selection; every configuration decision
+  with its justification, including build trust, overrides and peers, preserved
+  hoisting, keywords, Node.js ranges and types, exact pins, CSpell, and side
+  effects; remaining age exemptions with reasons and removal dates;
+  documentation changes and mdat conversions.
+- **Evidence and gaps:** the original versus Setup baseline distinction and any
+  lockfile drift, checks with their exact runtimes, installation and fixture
+  results, explained output differences, advisories, warnings and suppressions,
+  missing historical baselines, unresolved failures, blocked work, skipped
+  optional steps, and environment-driven deviations.
+
+Passing checks do not prove the absence of breaks. Leave all changes
+uncommitted.