HOLD until the Show HN morning — feat(www): the launch post, A name on every fact (#5610)

[msywulak]

Closes #5610. Do not merge before the morning of the Show HN. posts.ts has no date gate: a post in the array is live the moment it merges (see the header comment in apps/www/src/data/posts.ts). Merging this PR is publishing.

#5632 has merged, so this branch is now a single commit on top of main: the post, its posts.ts entry, and the superseded banners. Nothing else.

The post: /blog/a-name-on-every-fact, 874 words in the article body, one argument — auto-write memory is a trust liability and the fix is a human gate with a name on every fact. Shape as the issue asks: the return-window case, the three tiers in the PRD's language, the warehouse as the tier that cannot go stale, nothing counts until a person approves it, what that costs (breadth and adoption, stated as plainly as the claim), then the demo. The MCP command is the only CTA. Hyper is linked to its own launch thread and characterised nowhere. No feature list, no competitor named pejoratively. Vocabulary per ADR-0038: brain only as the category ("company memory"), Atlas as the product.

The recording renders from /launch/demo.gif (public/launch/); #5605 lands the dated file and points this src at it in the same commit as the README and the hero.

Before merging, on the day:

• Set isoDate/dateLabel/publishedTime (currently 2026-09-10, a placeholder) to the actual date in posts.ts and page.tsx.
• Confirm the recording file exists at the path the post embeds.
• The AC "reviewed by someone other than its author for the one thing that will get flamed" is the maintainer's read; my guess at that thing is the adoption paragraph (explicit tool call vs. silent hook), which is why it links Hyper's thread rather than paraphrasing it.

Also marks the April drafts in .claude/research/launch/ as superseded, per docs/prd/launch-cycle.md.

Verified: next build green with the post rendered; word count measured from the article body.

[github-actions]

Lighthouse budget

Budget defined in lighthouserc.js. Baselines under apps/www/.design/{landing,pricing,demo}/lighthouse-baseline.md.

First-month policy: budget assertions are warn-only and never fail a PR. This comment is the signal.

Desktop

Surface	Perf	A11y	Best Practices	SEO	LCP	CLS
/	99	100	100	92	1018 ms	0.00
/pricing	99	100	100	92	1017 ms	0.00
/demo	99	100	91	100	959 ms	0.00

Mobile

Surface	Perf	A11y	Best Practices	SEO	LCP	CLS
/	80	100	100	92	5259 ms	0.00
/pricing	79	100	100	92	5435 ms	0.00
/demo	78	100	91	100	4460 ms	0.00

_{Full HTML reports are in the lighthouse-reports artifact on this run · workflow: .github/workflows/lighthouse.yml}