release: npm latest remains on 1.8.7 after v1.8.8 publish failure

Summary

The public GitHub release and source are at v1.8.8, but the npm latest tag still resolves to v1.8.7 because release workflow run 33325731547 failed at Publish to npm.

Current evidence

• GitHub release/tag: v1.8.8
• source package.json: 1.8.8
• npm view @jackwener/opencli version dist-tags --json: version/latest 1.8.7
• release run: https://github.com/jackwener/OpenCLI/actions/runs/33325731547
• the job completed build and GitHub Release creation, then npm returned a 404 while publishing; the website rebuild step was skipped

Impact

Users following the documented npm install -g @jackwener/opencli@latest path receive 1.8.7 even though v1.8.8 is the current GitHub release.

Suggested next step

Please verify the npm package scope/ownership and publishing credentials, republish or reconcile v1.8.8, and rerun the website dispatch if appropriate. This needs maintainer release authority; no workflow or credential change is proposed here.

I searched current issues and all-state PRs for the v1.8.8/npm failure and found no equivalent report.