refresh-public-messaginglisted

# Refreshing Chimaera's public messaging The public face is **README.md** + the **GitHub Pages site** (`site/`). It drifts because capabilities ship faster than copy — a flagship feature can land and never reach the homepage. This skill closes that gap. It has two jobs, and the split is load-bearing: - **Facts** — what the product does — are **derived**. You verify them against the code and the feature catalog and fix them freely. Old public copy is a *suspect, not a source*. - **Positioning** — the tagline, the selling points, the audience the page leads with — is the **maintainer's ground truth**, exactly like a feature's `## Intent`. You never invent or "helpfully improve" it alone. You surface the tensions and *brainstorm*; the maintainer decides. ## The public surfaces (keep them in sync) | File | What it is | |---|---| | [README.md](../../../README.md) | The GitHub repo landing page — headline, why, quickstart, feature list. | | [site/index.html](../../../site/index.html) | The marketing homepage: hero, why, features, how-it-works, download, FAQ. Hand-written static HTML/CSS (**not** the web-ui). | | [site/docs.html](../../../site/docs.html) | The install/usage docs page (sidebar + sections). | All three must agree on the **headline**, the **feature list**, and the **billing story**. A change to one is usually a change to all three. ## Sources of truth (read these first — derive, don't remember) | Source | Gives you | |---|---| | [docs/features/](../../../d