[AAASM-2742] 🔗 (profile): Point node-sdk npm badge at the alpha tag

[Chisanan232]

Jira Ticket

• AAASM-2742

Summary

• The org-profile repo-status table read the node-sdk npm version from the default latest dist-tag, which is pinned at 0.0.1-alpha.3, while the newest published release is 0.0.1-alpha.5 under the alpha dist-tag. Pointing the badge at the alpha tag makes it reflect the real latest pre-release.

Changes

• profile/README.md: node-sdk npm badge URL now reads the alpha dist-tag (…/npm/v/%40agent-assembly%2Fsdk/alpha). Verified it renders v0.0.1-alpha.5.

Validation

• Content reviewed for accuracy
• Links verified — badge renders v0.0.1-alpha.5; all other profile badges (CI, release, tag, codecov, last-commit, issues/PRs) probed and render real values
• No unintended scope changes

Checklist

• PR title follows: [<ticket ID>] <GitEmoji> (<change scope category>): <key point as summary>
• PR body follows this template

Owner follow-ups (not code — out of scope for this README PR)

• The profile "Core release" badge (github/v/release/… without include_prereleases) renders v0.0.1-alpha.1 because that release is the one flagged "Latest" on GitHub, while alpha.5 is the newest pre-release. This is a release-marking/ops decision, not a broken badge — left as-is.
• The repo-status table still lists agent-assembly-spec. Per project policy the protocol spec lives in the agent-assembly monorepo; the spec repo's tag/issue/PR badges show no-data. This is a content decision owned by the docs-content stories, not a badge URL fix.

🤖 Generated with Claude Code

[Chisanan232]

Review — Claude Code

CI: ✅ No checks (README-only, path-excluded). Nothing to fix.

Scope vs AAASM-2742: ✅ The org-profile repo-status table's node-sdk npm badge had the same stale-latest issue → pointed at /alpha (shows v0.0.1-alpha.5). Verified 200.

Two items correctly left as owner follow-ups (noted in the PR, not badge-URL bugs): the "Core release" badge shows alpha.1 because that release is GitHub-flagged "Latest"; and the profile still lists agent-assembly-spec (a content decision).

Verdict: ✅ Ready for approval + merge.