Preview OG — Share-Card Validation & Fix

Runs the metaprev CLI against a URL (local dev server or deployed), reads how the link renders on Facebook / X / LinkedIn / Discord-Slack, fixes what's broken in the codebase, then re-verifies. Routing: routing.yaml · why / when-not / install / pushback: references/playbook.md [PLAYBOOK].

Core question: When someone pastes this link into a chat or feed, does the card render — right image, right size, right title — or is it broken or blank?

Critical Gates — load first

1. CLI present before running. metaprev runs on Bun. Probe for it; install if missing — never stall on a missing tool. Exact probe + install commands: references/playbook.md § Install.
2. Verify after fixing (objective gate). Re-run metaprev after every fix; the tool, not the agent's judgment, is the pass/fail signal. The re-run passes only when:
   • metaprev issues <url> --json exits 0 — zero errors (advisory warns allowed)
   • og:image is an absolute URL returning HTTP 200 with an image content-type
   • declared og:image:width/og:image:height match the real file's dimensions Auto-fail: a 4th fix cycle — stop at 3 and report DONE_WITH_CONCERNS.
3. og:image must be an absolute URL. A relative /og.png resolves to nothing when a crawler fetches it standalone — the #1 silent break. Always emit a full https://….
4. Noise pushback. title is short / description is short are advisory SEO heuristics, not breaks — a canonical brand or product title is intentional. Surface them; never pad copy to hit a char count. § Pushback in the playbook.
5. Scope. Touch only the meta / OG surface (head tags, og:image config). No unrelated refactors.

Before Starting