[AAASM-2742] 🔗 (profile): Fix stale release badge, docs-deploy branch, and install/Docker links

[Chisanan232]

Jira Ticket

• AAASM-2742

Summary

• Fix genuinely-broken badges and install links found in the AAASM-2742 audit of profile/README.md. Every fix is grounded in what actually exists today (verified with curl / gh).

Changes

• Core release badge — added ?include_prereleases&sort=semver and pointed the link at /releases. Before it showed v0.0.1-alpha.1; after it tracks the real latest v0.0.1-alpha.5, matching the core repo's own badge.
• agent-assembly-docs Deploy badge — ?branch=master → ?branch=main in both the badge src and the link query; also fixed the docs last commit link /commits/master → /commits/main. The docs repo default branch is main and deploy.yml runs there (?branch=master rendered "no status", ?branch=main renders "passing").
• Docker — removed the broken docker pull ghcr.io/agent-assembly/python:latest (no public container package exists in the org; slug was also wrong) and replaced it with a "coming soon" note.
• Install consistency — brew install agent-assembly/tap/aasm (non-existent org/tap) → brew install ai-agent-assembly/homebrew-agent-assembly/aasm (the real tap, with Formula/aasm.rb); the get.agentassembly.dev curl host is parked, replaced with the same raw.githubusercontent.com/.../install-cli.sh used in the agent-assembly README, with the hosted alias noted as coming-soon.
• Left the "no tags found" tag badges as-is (truthful — those repos have 0 tags).

Validation

• Content reviewed for accuracy
• Links verified (curl: release badge before=alpha.1 / after=alpha.5; docs deploy master="no status" / main="passing"; install.ai-agent-assembly.dev=NXDOMAIN; ghcr org packages=empty; homebrew tap + Formula/aasm.rb exist; install-cli.sh raw=HTTP 200)
• No unintended scope changes

Checklist

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

🤖 Generated with Claude Code

[Chisanan232]

🤖 Claude Code — PR review

Ticket: AAASM-2742 — Audit + fix broken/stale badges and links across doc surfaces
Scope: profile/README.md (org-profile)

CI status

This is a docs/profile repo with no CI workflows — gh pr checks reports "no checks reported", which is expected and = PASS. mergeStateStatus is BLOCKED only on the review-required gate (mergeable: MERGEABLE), not a failing check. No real check exists or fails.

Scope coverage — 5 fixes (each curl-verified, no CI here)

#	Fix	Verification	Result
1	Core release badge → ?include_prereleases&sort=semver, link → /releases	curl SVG <title> (cache-buster, past shields token-pool flake)	✅ Now renders release: v0.0.1-alpha.5 (old form returned stale v0.0.1-alpha.1 — repo has alpha.1 flagged "Latest" but alpha.5 is newest tag → prerelease-aware sort is the correct fix). /releases → HTTP 200. Param syntax validated against rust-lang/rust (v1.96.0).
2	docs Deploy badge ?branch=master → ?branch=main (src and link)	curl SVG <title> both forms	✅ ?branch=main → Build and Deploy Docs - passing; old ?branch=master → no status. Fix is correct (docs default branch is main).
3	Dead ghcr.io/agent-assembly/python Docker example → coming-soon note	diff review	✅ Removed; replaced with an honest "image coming soon, none on ghcr.io yet" note. No false pull command remains.
4	Parked get.agentassembly.dev installer → working raw-GitHub install-cli.sh	curl -sI raw URL	✅ raw.githubusercontent.com/.../scripts/install-cli.sh → HTTP 200. Parked hosted alias clearly labelled "planned, not yet live".
5	Wrong Homebrew tap agent-assembly/tap/aasm → real tap	gh repo view	✅ ai-agent-assembly/homebrew-agent-assembly/aasm — tap repo exists (public).

No new broken badge/link introduced. The diff touches only the 5 intended lines; the "no tags found" placeholder badges (spec, etc.) and the healthy SDK/CI badges were correctly left alone.

Readiness

Ready to merge from a content-correctness standpoint. All five fixes render/resolve healthy. Holding per author: no formal approval review and not merging here (review-required gate is the only thing blocking).

Caveats (owner decisions, not code)

• Container image — ghcr.io/ai-agent-assembly/... is parked "coming soon". Owner decides whether/where to publish a real image, then un-park the Docker block.
• Install domain — install.ai-agent-assembly.dev hosted alias is "planned, not yet live". Owner decides whether to register it; the raw.githubusercontent.com URL works in the interim.

Note: during verification, shields.io intermittently returned Unable to select next GitHub token from pool (a transient server-side token-pool exhaustion, not specific to this URL). A cache-buster retry cleared it and returned the real alpha.5 value — the badge itself is healthy.