chore(infra): decommission legacy Vercel Blob store

[wab]

After PR #48 migrated all content to the new blob store (ipjmp3k0z0p479cb.public.blob.vercel-storage.com), the legacy store (jr0deqtyc8c5pvr8.public.blob.vercel-storage.com) is no longer referenced anywhere in this repo.

Gate before decommissioning

• Consuming website confirmed live and rendering against the new store for at least one deploy cycle
• No other repos/services still reference the legacy host (search ocobo-revops org)
• Snapshot legacy bucket contents to cold storage if any historical assets are not present in the new store (compare assets/ vs legacy store listing)

Action

1. Revoke BLOB_READ_WRITE_TOKEN from project envs
2. Delete the legacy store in the Vercel dashboard
3. Remove BLOB_READ_WRITE_TOKEN references from scripts/upload-assets.js (currently the default --target legacy path) — see follow-up: at that point --target becomes single-valued and can be retired

Out of scope

The 3 tools without iconUrls (hyperline, outreach, vitally) are tracked separately.

[wab]

This was generated by AI during triage.

Created at the tail end of PR #48 to capture the legacy store decommission gate before the context evaporated. Initial AI labelling jumped straight to ready-for-human — reset to needs-triage for maintainer evaluation.

My recommendation: enhancement + ready-for-human. Reason: operational call (Vercel dashboard access, decision about cold-storage snapshotting) rather than codebase work. No urgency — gated on the consuming website confirming new-store rendering.