fix(cli): publish under fallback npm package

[mrgoonie]

Summary

Switches the npm package identity from uipro-cli to ui-ux-pro-max-cli while preserving the installed uipro binary command.

Why

Issue #353 is still blocked on npm ownership for the official uipro-cli package. The repository release pipeline can build the correct package, but the current NPM_TOKEN authenticates as mrgoonie while npm owner ls uipro-cli still lists only viettranx. This PR applies the maintainer fallback decision to publish under a different package name.

Changes

• Rename cli/package.json and cli/package-lock.json to ui-ux-pro-max-cli.
• Update uipro update so automatic/manual updates install ui-ux-pro-max-cli@<version>.
• Update GitHub request user agent to the new package name.
• Update README, CLI README, skill.json, and contributor/docs references to use ui-ux-pro-max-cli.
• Keep bin.uipro = dist/index.js, so user commands remain uipro ... after install.

Verification

• npm view uipro-cli version still returns 2.2.3.
• npm owner ls uipro-cli still lists only viettranx <viettranx@gmail.com>.
• Current NPM_TOKEN identity check returns mrgoonie, so it cannot publish uipro-cli.
• npm view ui-ux-pro-max-cli version returns 404, so the fallback package name is available.
• npm --prefix cli run check:assets passes.
• npm --prefix cli run typecheck passes.
• npm exec --yes --package bun -- bun build src/index.ts --outdir dist --target node passes.
• npm publish --dry-run --json from cli/ passes and reports ui-ux-pro-max-cli@2.5.0 with dist/index.js included.

Closes #353 after a release proves npm publish and clean install succeed.

[mrgoonie]

Summary: PR #393 applies the maintainer fallback for issue #353 by moving the npm package identity to \ while preserving the installed \ binary.

Risk level: Medium. This is a package identity migration, so docs/update paths must move together, but the runtime command remains backward-compatible after install.

Mandatory gates:

• Duplicate / prior implementation: clear. PR #384 and #392 fixed workflow/bin metadata; neither solved npm ownership. No other PR changes to \ were found.
• Project standards: docs found. README/CLAUDE sync rules and no-direct-main workflow followed.
• Strategic necessity: clear value. Current token authenticates as , while \ is owned only by ; fallback package unblocks npm distribution.

Findings:

• Critical: none.
• Important: none.
• Suggestions: none.

Verification:

• \

ui-ux-pro-max-cli@2.5.0 check:assets
node scripts/sync-assets.mjs --check

CLI assets are in sync. passed.

• \

ui-ux-pro-max-cli@2.5.0 typecheck
tsc --noEmit passed.

• \ passed.
• {
  "error": {
  "code": "ENOENT",
  "summary": "Could not read package.json: Error: ENOENT: no such file or directory, open '/Volumes/GOON/www/nlb/ui-ux-pro-max/skill/package.json'",
  "detail": "This is related to npm not being able to find a file."
  }
  } passed from \ and reported package \ with \ included.
• PR merge state is clean; GitHub reports no checks on the branch.

Verdict: Approve. This is ready to merge, then release. After release, close #353 only when , {
"error": {
"code": "E404",
"summary": "Not Found - GET https://registry.npmjs.org/ui-ux-pro-max-cli - Not found",
"detail": "The requested resource 'ui-ux-pro-max-cli@*' could not be found or you do not have permission to access it.\n\nNote that you can also install from a\ntarball, folder, http url, or git url."
}
}, and clean \ all pass.

Posted by /ck:review-pr at 2026-06-26T04:00:39Z

[mrgoonie]

Supersedes the previous malformed review comment; the earlier body was corrupted by local markdown shell expansion before posting.

Summary: PR #393 applies the maintainer fallback for issue #353 by moving the npm package identity to ui-ux-pro-max-cli while preserving the installed uipro binary.

Risk level: Medium. This is a package identity migration, so docs/update paths must move together, but the runtime command remains backward-compatible after install.

Mandatory gates:

• Duplicate / prior implementation: clear. PR #384 and #392 fixed workflow/bin metadata; neither solved npm ownership. No other PR changing to ui-ux-pro-max-cli was found.
• Project standards: docs found. README/CLAUDE sync rules and no-direct-main workflow followed.
• Strategic necessity: clear value. Current NPM_TOKEN authenticates as mrgoonie, while uipro-cli is owned only by viettranx; fallback package unblocks npm distribution.

Findings:

• Critical: none.
• Important: none.
• Suggestions: none.

Verification:

• npm view uipro-cli version still returns 2.2.3.
• npm owner ls uipro-cli still lists only viettranx <viettranx@gmail.com>.
• npm view ui-ux-pro-max-cli version returns 404, so the fallback package is available.
• npm --prefix cli run check:assets passed.
• npm --prefix cli run typecheck passed.
• npm exec --yes --package bun -- bun build src/index.ts --outdir dist --target node passed.
• npm publish --dry-run --json passed from cli/ and reported package ui-ux-pro-max-cli@2.5.0 with dist/index.js included.
• PR merge state is clean; GitHub reports no checks on the branch.

Verdict: Approve. This is ready to merge, then release. After release, close #353 only when npm view ui-ux-pro-max-cli version, npm view ui-ux-pro-max-cli bin --json, and clean npx --yes ui-ux-pro-max-cli@<new-version> init --ai claude all pass.

Posted by /ck:review-pr at 2026-06-26T04:01:19Z