INTERNAL QA SMOKE TEST - SAFE TO DELETE

This is an automated QA smoke test post for the seo-factory publish tool integration with cms.tokenomics.net. It exists temporarily to verify that the staging, publishing, smoke-probing, and rollback path works end-to-end against the live CMS.

#What this post tests

The publish tool performs eight discrete operations during a single-slot publish, and this post verifies all of them in sequence against the real Payload v3 instance running on cms.tokenomics.net. The operations are: admin login via the users collection JWT endpoint, idempotent slug check against the existing posts collection, multipart hero image upload to the media collection backed by Vercel Blob storage, post document creation in draft status with the full schema mapping populated, status flip to published, ISR revalidation hook firing back at tokenomics.net, and four smoke probes hitting the live URL after revalidation settles.

#Why this exists

A bulletproof publish tool requires verification against the real production CMS, not just mocked unit tests. Mocks confirm the adapter constructs the right HTTP payloads but cannot confirm that Vercel Blob actually accepts the upload, that Payload's revalidation hook actually fires Next.js ISR, or that the consumer site renders the post within the expected window. Phase C of the QA pass covers that gap by staging a clearly-marked throwaway slot, putting it briefly live, and verifying each step.

#What happens next

Within sixty seconds of this post going live, an automated cleanup will delete the post document, the associated media document, and remove this content from the consumer site. If this post is still visible an hour after publication, the QA test was interrupted and the operator should manually delete the test post from the Payload admin.