fix(sdk): match Windows runtime archive name on npm publish

[arul28]

Problem

The first Publish ADE runtime packages run against v1.2.72 failed at checksum verification: it expected 10 runtime SHA256SUMS lines and found 9.

Cause

runtimeAssetNames("win32-x64") and the workflow grep looked for ade-win32-x64.exe.native.tar.gz. Releases and SHA256SUMS publish ade-win32-x64.native.tar.gz (the .exe is only on the launcher).

Change and boundary

The helper now returns the real Windows archive name. The checksum step reads those names from the helper instead of a second grep. No packages were published by the failed run.

Verification

• node --test apps/ade-cli/scripts/build-runtime-npm-packages.test.mjs apps/ade-cli/scripts/verify-runtime-package-contents.test.mjs: 41 passed
• Helper matched all 10 v1.2.72 SHA256SUMS runtime lines

Authored with Cursor Grok 4.6 via ADE.

Made with Cursor

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
ade	Ignored	Preview	Sep 2, 2026 4:52pm UTC

[coderabbitai]

Warning

Review limit reached

Next included review available in 1 minute.

Check out review usage here.

View limit details

Limit details: You’ve used all 2 included reviews currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Team

Run ID: 10da887f-4c4b-41b6-b3ed-9085383c0067

📥 Commits

Reviewing files that changed from the base of the PR and between 234df59 and 98df7d5.

📒 Files selected for processing (3)

• .github/workflows/publish-runtime-packages.yml
• apps/ade-cli/scripts/build-runtime-npm-packages.mjs
• apps/ade-cli/scripts/build-runtime-npm-packages.test.mjs

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_f6078f9b-029f-4ffa-9328-5be5855ac770)