feat(blob): push cleaned posts/assets/ to new website-blob store

[wab]

Parent

#32

What to build

Push the cleaned posts/assets/ to the new website-blob store, preserving pathnames so the only downstream change is the hostname swap.

Approach: re-purpose posts/scripts/upload-assets.js --all against the new store. Optionally add a --target new flag that selects NEW_BLOB_READ_WRITE_TOKEN over BLOB_READ_WRITE_TOKEN, with addRandomSuffix: false to preserve pathnames. Batches of 5 concurrent uploads to avoid rate limits.

After upload, run a verification step: HTTP HEAD against every uploaded URL using the new hostname. 0 failures required.

Acceptance criteria

• All cleaned posts/assets/** files pushed to website-blob store with identical relative pathnames (content/clients/..., content/team/..., content/posts/<slug>/...)
• Upload script supports --target new (or equivalent) selecting the new store token
• addRandomSuffix: false so pathnames match the legacy convention exactly
• Verification step (HEAD on each new URL) reports 0 failures
• Runnable as NEW_BLOB_READ_WRITE_TOKEN=... pnpm upload-assets:all --target new

Blocked by

• feat(blob): create website-blob store under Ocobo team account #35 (new store created)
• feat(assets): compress oversized team photos before blob migration #41 (team photos compressed — to avoid migrating uncompressed bytes)