docs: stop positioning Askr as new and unused

[smiggleworth]

Why

Askr serves production applications today — static marketing sites and admin consoles, this site included — but the copy read as pre-adoption. The site never overclaimed (no fake logos, no invented adoption); it undersold.

The framing was concentrated in /contribute, which described Askr as "an early open-source project maintained by one person" that was "young enough that some paths will be unfinished," under an "Early contribution opportunities" heading, an "Early contributors" footer link, and a <title> of "Become an early contributor." One opportunity card asked contributors to "build real applications, find rough edges" — implying none existed. Meanwhile /production explained deployment mechanics in detail and never mentioned that anything was actually deployed.

What changed

File	Change
marketing/contribute.tsx	Lead with production use; drop the maintainer headcount while keeping the "you work directly with the people maintaining it" substance; replace the "young/unfinished" paragraph with a pointer to the docs' experimental/limited badges as the map of where the surface is thin
marketing/production.tsx	New "What already runs on this" section, naming this site as the inspectable instance
marketing/home.tsx	Hero line "In production today on static marketing sites and admin consoles — this site included," plus a closing-CTA clause
marketing/_routes.tsx	/contribute title → "Contribute to Askr"; "early" dropped from the meta description
site-footer.tsx	"Early contributors" → "Contribute"
styles.css	.hero__proof rule + mobile spacing
public/llms.txt	Production fact added to the canonical summary agents read
todo.md	Items 2 and 3 were stale (cited 0.0.x versions, "pre-adoption framework," "no production story"); item 3 recommended adding the hedging this PR removes

Also included as a separate commit: @askrjs/askr 0.3.1 (the only @askrjs package with a newer release — the other 16 were already current). package.json is unchanged since the declared ranges already covered it; the regenerated snapshot diff is version strings only, so the release is API-identical.

Deliberate boundaries

• All claims are first-party and unattributed. Nothing implies third-party adoption or outside teams, because that isn't true yet. No logos, no named deployments.
• Marketing carries no version or stability hedging. The docs' per-page experimental/limited badges remain the single place status is asserted, and /contribute now points readers at them. The accurate per-feature caveats there (e.g. selective hydration) are untouched — dropping marketing hedging doesn't make those dishonest, it makes them authoritative.
• One claim was narrowed during review: an earlier draft said this site "is scaffolded by the Askr CLI." The README attests that it's built with Vite Plus and the Askr CLI and rendered by askr ssg, not that it came from askr create. It now says only what the build actually does.

Verification

npm run check plus the browser suite, all passing:

• fmt:check, lint, typecheck
• 40 unit tests
• build + 288 SSG routes, 2 static-output contracts
• 41 Playwright layout tests (desktop/mobile × light/dark across all marketing pages)

New copy confirmed present in the rendered dist/ HTML. A final grep shows no early/young framing left in any published surface.