fix(ci): add post-publish verification for platform binaries

[MoerAI]

Summary

Add post-publish verification step and fix missing NODE_AUTH_TOKEN in the platform publish workflow to prevent silent publish failures.

Problem

The v3.1.2 Windows binary was not published to npm while the main package was published successfully (#1171). This caused users to receive a version mismatch:

• oh-my-opencode@3.1.2 (main package) - published
• oh-my-opencode-windows-x64@3.1.2 - NOT published (latest was still 3.1.1)

Users still experienced the cross-compilation segfault bug (oven-sh/bun#18416) because they got the old v3.1.1 binary.

Solution

1. Add post-publish verification step: After npm publish, verify the package is actually available on npm registry

   • Polls npm registry for up to 60 seconds to account for propagation delay
   • Fails explicitly if package is not found, making the issue visible in CI

2. Add NODE_AUTH_TOKEN env var: Ensure npm authentication is properly configured for the publish step

Changes

• .github/workflows/publish-platform.yml:
  • Add NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} to publish step
  • Add new "Verify publish" step with retry logic

Testing

This is a CI workflow change. To test:

1. Trigger publish-platform.yml manually with a test version
2. Verify the new verification step runs and confirms package availability

Related Issues

• Fixes [Bug] oh-my-opencode-windows-x64@3.1.2 not published to npm #1171
• Related to [Bug]: Can't install beta 8 or 9 on Windows. #873, [Bug] Beta version (3.0.0-beta.x) fails to install on Windows due to missing platform binary #844, fix(ci): build Windows binary natively to fix segfault #1019

---

Summary by cubic

Adds a post-publish verification step for platform binaries and sets NODE_AUTH_TOKEN in the publish workflow. This prevents silent npm publish failures like the missing Windows v3.1.2 binary; fixes #1171.

• Bug Fixes
  • Add NODE_AUTH_TOKEN to npm publish step for proper authentication.
  • Add a verification step that polls the npm registry for up to 60s and fails if the package isn’t found.

^{Written for commit 5f34fba. Summary will update on new commits.}

[github-actions]

All contributors have signed the CLA. Thank you! ✅
_{Posted by the CLA Assistant Lite bot.}

[cubic-dev-ai]

No issues found across 1 file

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

[MoerAI]

I have read the CLA Document and I hereby sign the CLA

[MoerAI]

recheck