Ship @amd-gaia/agent-email v0.2.0 (real R2 + npm)

[kovtcharov-amd]

Why this matters

Turns the email agent from "demo-proven with placeholders" into actually installable via npm i @amd-gaia/agent-email. Ships on the existing one-off release_agent_email.yml (rclone → assets.amd-gaia.ai) — the registry-driven generalization is tracked separately in milestone #51 and lands shortly after.

Checklist

• Land the rclone cutover PR — release_agent_email.yml (rclone), gen_binaries_lock.py refactor, real win32 hash in binaries.lock.json. (Keep the Worker code from feat(email-packaging): no-Python email-agent binary + thin @amd-gaia/agent-email npm client #1654 in place — out of scope to remove.)
• Repo config (maintainer): secrets R2_ACCESS_KEY_ID / R2_SECRET_ACCESS_KEY / R2_ACCOUNT_ID; var ASSETS_BASE_URL; register npm trusted publisher for @amd-gaia/agent-email against release_agent_email.yml.
• Tag agent-pkg-email-v0.1.0 → CI freezes all 4 platforms (win32-x64, darwin-arm64, darwin-x64, linux-x64), uploads to R2, regenerates lock with real hashes, fetch-verifies, npm publish.
• Verify npm i @amd-gaia/agent-email pulls + runs on a clean box.

Known limitation

First release ships unsigned binaries (#732 / #733 / #1650 not done) → SmartScreen/Gatekeeper warnings. Acceptable for an early/preview publish; note it in release comms.

[github-actions]

Tracking issue looks accurate against main. A few grounded notes for the cutover PR:

• Lock file is still fully placeholder. hub/agents/npm/agent-email/binaries.lock.json has baseUrl: https://PENDING-R2-BUCKET.example/... and PENDING-1648-replace-with-real-sha256 for all four platforms (sizes 0). Item 1's "real win32 hash" replaces just that one entry; the tag-driven CI run (item 3) regenerates the other three. Worth confirming gen_binaries_lock.py writes the new ASSETS_BASE_URL-derived baseUrl, not the .example placeholder.

• The two "repo config" sets don't overlap. release_agent_email.yml on main today still uses the Worker path (AGENT_HUB_PUBLISH_TOKEN / AGENT_HUB_BASE_URL). The new R2_* secrets + ASSETS_BASE_URL var only become meaningful once the rclone PR lands — so item 2 is gated on item 1, and the old vars can be left in place (you noted keeping the feat(email-packaging): no-Python email-agent binary + thin @amd-gaia/agent-email npm client #1654 Worker code).

• 🟡 Don't rename the workflow file. npm trusted publishing binds the OIDC subject to the exact filename release_agent_email.yml (the workflow header calls this out). The rclone refactor should edit in place — a rename silently breaks npm publish at item 3.

On the unsigned-binary limitation: agreed it's fine for a preview, just make sure the SmartScreen/Gatekeeper note lands in the npm README too, not only release comms — that's where a clean-box installer (item 4) will actually hit it.

[kovtcharov]

Shipped. @amd-gaia/agent-email is live on npm at 0.2.4 (0.2.0 first published Jun 23) with real per-platform binaries served from R2 and SHA-verified fetch. Superseded by the 0.2.x release line — closing.