@aurodesignsystem-dev/auro-cli 0.0.0-pr350.0 → 0.0.0-pr350.2

package/README.md

@@ -215,7 +215,7 @@ Only public API counts. Members are filtered on the manifest's `privacy` field,
 
 The manifest is rebuilt at both refs in temporary git worktrees, by default with `npm ci` and `npm run build`. The rebuild is skipped when only `test/`, `.github/` or `docs/` changed. If the head doesn't build, the check errors (fails closed). If the base doesn't build, the check uses the base's committed manifest, or skips the API comparison, and says so in `warnings` (fails open): a PR shouldn't be blocked by a base it didn't break.
 
-**Declared bump.** The highest bump among the non-merge commits, worked out by `@semantic-release/commit-analyzer` with the repo's own release config (usually `@aurodesignsystem/auro-config/releaserc`, including its custom rules: `refactor`, `style` and `docs(README)` release a patch). It's loaded from the repo's `node_modules` when installed, so the check reads commits exactly as the release will. Otherwise auro-cli's own copy and the shared rules are used. The PR title never counts, because merge commits don't affect the version.
+**Declared bump.** The highest bump among the non-merge commits, worked out by `@semantic-release/commit-analyzer` with the repo's own release config (usually `@aurodesignsystem/auro-config/releaserc`, including its custom rules: `refactor`, `style` and `docs(README)` release a patch). The analyzer is loaded from the repo's own `node_modules`, so the check reads commits exactly as the release will. Run `npm ci` in the repo first: the check errors when the analyzer isn't installed. If the repo's release config can't be resolved, the shared rules are used and `warnings` says so. The PR title never counts, because merge commits don't affect the version.
 
 **Outcome.**
 
@@ -223,7 +223,7 @@ The manifest is rebuilt at both refs in temporary git worktrees, by default with
 - `warn`: no release is required, but the commits declare one (for example, a `fix:` that only touches tests).
 - `pass`: otherwise. Declaring more than required is allowed, because behavior can break without the API changing.
 
-The JSON starts with `required` and `reasons`, followed by `declared`, `outcome`, a one-line `summary` for PR comments, the refs, each change and commit with its bump, the release config and analyzer used, and any `warnings`:
+The JSON starts with `required` and `reasons`, followed by `declared`, `outcome`, a one-line `summary` for PR comments, the refs, each change and commit with its bump, the release config used, and any `warnings`:
 
 ```json
 {
@@ -235,7 +235,7 @@ The JSON starts with `required` and `reasons`, followed by `declared`, `outcome`
 }
 ```
 
-Exit codes: `0` when the analysis ran, `1` with `--enforce` when the outcome is `fail`, `2` when the analysis couldn't run (an unknown ref, or a head that won't build).
+Exit codes: `0` when the analysis ran, `1` with `--enforce` when the outcome is `fail`, `2` when the analysis couldn't run (an unknown ref, a head that won't build, or no commit-analyzer installed in the repo).
 
 ### AI assistant context