[AAASM-2958] 🐛 (profile): Fix SDK version badges in org repo table

[Chisanan232]

Jira Ticket

• AAASM-2958

Summary

• The per-SDK rows of the org landing page repo table showed stale/wrong version badges (node-sdk GitHub tag v0.0.1-alpha.4 + npm /alpha 0.0.1-alpha.9.1; python-sdk GitHub tag drifted to v0.0.2a1). This points each SDK row at the source that now resolves to the current v0.0.1-beta.1 release, and refreshes the obsolete alpha/zero-checksum prose.

Changes

• node-sdk row: GitHub badge github/v/tag → github/v/release?include_prereleases&sort=semver (node-sdk now has a v0.0.1-beta.1 Release); npm badge dist-tag /alpha → /beta.
• python-sdk row: GitHub badge github/v/tag → github/v/release?include_prereleases&sort=semver (python-sdk now has a v0.0.1-beta.1 Release); PyPI badge unchanged.
• go-sdk row: kept github/v/tag (go-sdk has only git tags, no Release objects) and added sort=semver so it picks v0.0.1-beta.1; Go Reference badge unchanged.
• agent-assembly (core) row: left as-is — it already resolves to v0.0.1-beta.1 without sort=semver. (Adding sort=semver was verified to mis-sort it to the foreign spec/v0.0.1 tag, so it was intentionally not added.)
• Release and Homebrew Notes prose: rewrote the "pre-stable alpha channel" and "checksum placeholders are still all zero" bullets to reflect the beta channel and the Homebrew tap's real published sha256 checksums (referencing the Core release badge instead of hard-coding a version).

Validation

• Content reviewed for accuracy
• Links verified
• No unintended scope changes

Verified each new badge renders the expected version via shields.io:

• node-sdk GitHub release → GitHub: v0.0.1-beta.1; npm beta → npm: v0.0.1-beta.1
• python-sdk GitHub release → GitHub: v0.0.1-beta.1; PyPI (unchanged) → PyPI: v0.0.1b1
• go-sdk GitHub tag (semver) → GitHub: v0.0.1-beta.1
• core GitHub tag (untouched) → GitHub: v0.0.1-beta.1

Checklist

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

Closes AAASM-2958

[Chisanan232]

Claude Code review — AAASM-2958 (org profile SDK badge table)

CI state

No PR checks run on profile/README.md in this repo (README-only org-profile repo) — nothing to fix. MERGEABLE.

Scope vs. acceptance criteria

AC	Status
node-sdk row shows current release + registry	✅ GitHub tag → github/v/release?include_prereleases&sort=semver; npm /alpha → /beta
python-sdk row shows current release + registry	✅ GitHub tag → github/v/release?include_prereleases&sort=semver; PyPI kept
go-sdk row shows current release	✅ kept github/v/tag + added sort=semver (go has no Release objects)
Stale alpha/bootstrap prose refreshed	✅ "pre-stable alpha channel" → "beta channel"; "zero-checksum bootstrap" → "real published sha256 checksums"
Via PR, base master, granular commits	✅ 4 commits

Reviewer note (good catch): the agent-assembly core row was deliberately left without sort=semver — that repo carries a foreign spec/v0.0.1 tag that would out-rank v0.0.1-beta.1 under semver sort; the date-based default correctly resolves to v0.0.1-beta.1. Verified, not assumed.

Dependency satisfied: node-sdk / python-sdk now have v0.0.1-beta.1 GitHub Releases (AAASM-2955 / AAASM-2956), so the github/v/release badges in this table resolve correctly.

Verdict

Ready for approval and merge. Scope complete; all SDK rows resolve to the current release + registry version.

— Claude Code