feat: schema.org BlogPosting structured data on reports

[0xd3lta]

Adds schema.org BlogPosting structured data to every report.

Why

The site already carries canonical, OpenGraph, Twitter cards, sitemap and RSS autodiscovery. Structured data was the one thing missing: without it search engines infer authorship, date and section from the prose instead of being told. Declaring them explicitly is what makes an article eligible for a rich result — author and date shown in the snippet rather than title and description alone.

What it emits

A single <script type="application/ld+json"> per post, built at build time from frontmatter that already exists:

Field	Source
headline, description	frontmatter
datePublished	pubDate, as ISO 8601
articleSection	category
keywords	tags, omitted when absent
image	the per-post OG image
url / mainEntityOfPage	the canonical URL
author	author, linked to the operator profile
publisher	0xDelta Research + site logo

The edge case it handles

author.url is only emitted when the nick matches an existing operator. A discontinued nick must not become a dead link inside structured data — Google treats a broken author.url worse than an absent one.

Verified on the two ANKHCORP reports, whose profile was removed in #62: both emit the author name with no url.

Verification

• Build clean, 31 pages
• 20 of 20 reports carry valid JSON-LD, parsed and checked field by field — 0 parse failures
• Every URL inside the payload resolves 200: profile, OG image, logo

Scope

Reports only. Operator pages could later carry ProfilePage/Person, but the SEO value is in the articles.

Static output only — no backend, no runtime, no new dependency.

🤖 Generated with Claude Code