Test Post: Pipeline Smoke Test (Will Be Archived)

This is a test post. We are validating the publish-to-blog pipeline end-to-end: image generation, image-URL tracking, draft POST, status PATCH to published, and front-end rendering. The text below is intentionally short and is not part of the final W1 Mon editorial calendar slot.

What this test post proves

If you can read this on revamperd.com/blog/ and the cover image above renders, every piece of the publishing pipeline works:

1. The image was generated by grok-imagine-image at 1K resolution and is hosted by xAI at a public URL. No S3 upload required for this run.
2. The URL is recorded in our durable image tracker at /home/hermeswebui/.hermes/workspace/revamperd/image_urls.jsonl so we never lose it.
3. The post was created via POST /api/blog.php with status: "draft", then promoted to published with a PATCH.
4. The on-site grid at /blog/ should now show this card, and the article URL should be reachable.

Why we used the xAI URL directly

We started by routing generated images through an S3 webhook at https://n8n.dialiox.shop/webhook/file-uplode-s3-1. After probing that endpoint we found it currently accepts GET only and returns 404 for POST — the upload workflow is not yet wired up. While we wait for that to be reconfigured, the xAI-hosted URL is the simplest path. The image_generate tool reported that storage is enabled for the xAI account, so the public URL is expected to persist.

What we will validate on this run

• Render check: Open the live URL in a browser. The cover image must render at 1K (≤ 1920px wide), with loading="eager" and fetchpriority="high" on the LCP element.
• Card check: The post must appear in the blog grid with its description, category tag, and reading time.
• URL persistence: Re-fetch the xAI URL after 24 hours — confirm it still resolves 200, not a 403/404 from expired storage.
• Sitemap ping: If everything above works, the next step is calling POST /api/blog.php's sibling sitemaps endpoint to push the new article URL to Bing and Google.

What happens next

If the xAI-hosted URL stays stable for 48 hours, we will continue using it for all blog cover images and inline illustrations. If it expires, we will resume the S3 webhook plan with the workflow reconfigured to accept POST requests and parse a JSON body shaped as:

{
  "image_name": "<filename>.<ext>",
  "image": "<base64-encoded file bytes>",
  "content_type": "image/jpeg",
  "source": "revamperd-blog"
}

Either way, every URL — xAI-hosted or S3 — is logged to the tracker with date, post slug, role, and resolution. No image goes into a published post without a row in image_urls.jsonl.

Test post — generated 2026-07-05 by the Revamperd blog marketing agent. Pipeline smoke test only. Will be archived once validation completes.