#3153 fix(cli): retrigger release after npm-stage publish fix

Summary (AI generated)

• Adds a one-line comment in cli/src/utils.ts with no behavior change.
• Intentionally touches a path matched by scripts/release-scope.ts (cli/src/**) so the Bump version workflow sets run_cli=true on merge to main.

Motivation (AI generated)

PR #3152 (fix(ci): publish CLI via npm stage like plugins) fixed .github/workflows/publish_cli.yml to publish through the npm stage, but it merged without any CLI source changes. Bump version skipped the CLI release because release-scope.ts only triggers on changes under watched CLI paths (cli/src/**, cli/package.json, etc.).

PR #3151 already tagged cli-8.41.1, but that publish failed. npm still shows @capgo/cli@8.39.0, so SuperFrete and other customers cannot get the fixes from 8.41.x until a new tag is cut and published with the fixed workflow.

Business Impact (AI generated)

Unblocks publishing @capgo/cli@8.41.2 with the corrected npm-stage publish pipeline. Customers waiting on recent CLI fixes (including SuperFrete) can install the latest release once this merges and CI completes.

Test Plan (AI generated)

• Change is comment-only; no logic, tests, version, or workflow edits.
• File path cli/src/utils.ts matches componentMatchers.cli pattern /^cli\/src\// in scripts/release-scope.ts.
• After merge: confirm Bump version tags cli-8.41.2 and publish_cli.yml runs successfully.
• Do not retag or republish cli-8.41.1.

Generated with AI

  

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}