fix(cli): align utils/update/ + utils/command/ error messages with 4-ingredient strategy

[John-David Dalton (jdalton)]

Summary

PR 4 in the error-message cleanup series. Covers packages/cli/src/utils/update/ (the update-checking stack) and packages/cli/src/utils/command/registry-core.mts (the custom command-registry layer). ~17 messages across 3 source files + 3 test files.

What's fixed

utils/update/checker.mts (8 throws)

Registry / network / input validation errors. Before, most said "Package name must be a non-empty string" or "Invalid registry URL: foo". After, each message names:

• the function that was called
• the received value (with its type when it matters)
• the valid shape

Example:

Before: Invalid version data in registry response
After: https://registry.npmjs.org/foo/latest responded without a .version string (got: {"name":"foo"}); the registry may be misconfigured or foo may not exist — verify the URL in a browser

utils/update/manager.mts (3 warn guards)

Mirror validation on the manager layer — same options, checked again before the checker call. Previously shared wording with checker.mts which was confusing when both fired. Now each message explicitly prefixes checkForUpdates options.X so you can tell which layer complained.

These are loggerLocal.warn + return false, not throws, so the tone stays soft ("skipping update check" rather than "throw").

utils/command/registry-core.mts (6 throws)

The custom CLI command-registry layer. Conflict errors now name both commands involved; middleware errors name the index; flag errors name the flag and the expected type. Examples:

Before: Alias "test" conflicts with existing command "test"
After: cannot register command "other" alias "test": conflicts with command "test"; rename the alias or unregister the conflicting command first

Before: Missing value for flag --name
After: flag --name requires a string value but none was provided; pass it as --name=<value> or --name <value>

Tests updated

• test/unit/utils/update/checker.test.mts — 6 assertions switched to regex
• test/unit/utils/update/manager.test.mts — 3 assertions switched to expect.stringContaining
• test/unit/utils/command/registry-core.test.mts — 5 assertions

153/153 tests in the affected suites pass.

Test plan

• CI green
• Sanity: pass --page foo or similar invalid flag into the custom registry's built-in parser (it's not wired to most commands, but the tests exercise it)

---

Note

Low Risk
Low risk: changes are limited to error/warn message wording and corresponding test assertion updates, with no functional logic changes to command execution or update checking paths.

Overview
Improves CLI diagnostics by rewriting command registry and update-checking validation errors to include the calling function/context, the received value, and clear remediation guidance (e.g., duplicate command/alias conflicts, middleware next() double-invocation, missing/invalid flag values, invalid registry inputs/registry responses).

Updates unit tests to match the new, more descriptive messages (switching several assertions to regex/stringContaining).

^{Reviewed by Cursor Bugbot for commit 952b914. Configure here.}

[John-David Dalton (jdalton)]

bugbot run

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 952b914. Configure here.}