feat(docs): release 0.15.0 with tighter spacing, a redrawn landing and an archive strip

[tmccoy14]

Need

Guardian, Integrity Python SDK, Verifiable Compute and the component site are long pages of prose and examples. Readers should see a section's text together, and the landing page should get them to the right section fast.

Problem

• Spacing: 0.14.1 puts 80px above a 20px h2 and 48px above an h3, more than any of 11 prose docs sites (median 53px: Stripe 46, Next.js 45, Starlight 53, GitHub 68) and 12 component-library docs sites (median about 45px above an h2, 25px above an h3). The footer area runs 445px below the last paragraph, against Starlight's 265px.
• Landing: a grey header panel on every card, underlined links, a fixed three-column grid that leaves empty space beside a two-card row, and a title that wraps with the sidebar open.
• Archive banner: a boxed alert inside the article that says interactive examples are not shown, which holds only for pages with live component examples.

Change

One spacing scale for every site, no options:

• 48px above an h2, 32px above an h3, 32px under the page header
• 16px below paragraphs, lists, code, tables, tabs, alerts and rules
• 64px around the article footer, and a one-line site footer the header's height (69px)
• Labels and h4 to h6 keep their gaps; heading labels stay automatic, as on main
• The README's spacing table is updated

Landing page

• Larger title that takes the full width and stays on one line at 1024px and up; mono section labels like the sidebar's
• Cards with a 16px title, an optional Lucide icon beside it, quiet link rows and a brand hover
• Columns follow each section's card count, so every row spans the width; a lone card lays out sideways. Descriptions share a row height through subgrid

Every page

• Dark mode only: a faint brand wash behind the page header, drawn by the content column so it spans it at any width. It fades out above the body text, so only the title and description sit on it, at 9.8:1 or better
• Archived versions open with a full-width strip like Studio's archived banner: "You're viewing archived documentation for v1.2.0. See the latest version (v1.2.1)." The link still opens the same page in the latest version

Evidence

Heading gaps, measured in the browser:

	Above h2	Above h3
0.14.1	80px	48px
This PR	48px	32px
12 component-library docs (median)	~45px	~25px
11 prose docs (median)	53px	—

Component sites measured: shadcn/ui, Radix Themes, MUI, Mantine, Chakra, Primer, Carbon, Atlassian, Ant Design, Headless UI, Tailwind (React Aria and Polaris didn't measure).

• On the component site's Alert, Card and Toast pages, each example still reads as its own block; pages run 8 to 12% shorter
• Guardian's Troubleshooting page goes from 2458px to 2090px; the site footer from 101px to 69px, the header's height
• Run locally on all three docs sites from this branch's build: every page loads, every landing link returns 200, titles stay on one line from 1024px to 1920px, and Guardian's docs ci passes
• 218 docs tests pass

Not covered

• Headless Chromium only
• Each site's config and landing changes land in their own repos after 0.15.0 is published. Guardian also adds an intro sentence under the h2s that would otherwise become labels, and updates its archive-banner check for the new wording

🤖 Generated with Claude Code

[Shrinks99]

If the spacing is not as desired, I don't want to add site-level overrides that change it on a per-site basis. This should be a global style and we should fix it so it looks nice on all of them.

[tmccoy14]

@Shrinks99 agreed, thanks. d37a6ae removes spacing and headingLabels: the tighter scale is now the only one, on every site, and heading labels behave as on main.

Since #198 moved the headings to 80/48 for the component site, I checked component docs as well as prose ones before making it global:

	Above h2	Above h3
0.14.1	80px	48px
This PR	48px	32px
12 component-library docs (median)	~45px	~25px

Sites: shadcn/ui, Radix Themes, MUI, Mantine, Chakra, Primer, Carbon, Atlassian, Ant Design, Headless UI, Tailwind. On our own Alert, Card and Toast pages each example still reads as its own block, and the pages run 8 to 12% shorter. @matthewmr-eqty, worth a look at those three since they were the ones #198 fixed.

Where labels misfired on Guardian, the fix is in Guardian's content (an intro sentence under the h2), not in equality.