This release is mostly about saying the right thing in public: the CLI registry, the website, and generated AGENTS.md files now share one vocabulary for preset support.
What changed
Registry-driven labels
Presets expose Requires validation, Experimental, or Stable from packages/registry. The /families page and /docs/presets catalog read the same rows the CLI uses—no hand-maintained status badges on the site.
Verification matrix in code
PRESET_VERIFICATION_MATRIX drives both docs and tests. A preset cannot be labeled Stable until presetHasStableEvidence passes for its route (structure, package managers, generated CI steps, route-specific gates like Cargo or Anchor).
Documentation split
We finally stopped mixing three different command lists in one paragraph:
| Context | Example |
|---|---|
| Arche CLI | bun run dev:cli -- my-app --yes |
| Generated project | bun install && bun run ci |
| Source template | bun run repo:doctor |
The new Getting started page is the hub.
Convex preset in registry
convex-product is listed alongside TypeScript and Solana routes with its own capability set (web, convex, auth, deployment).
What did not change
- npm publish is still guarded. Use source checkout commands until release gates clear.
- No preset was promoted to Stable without new green columns—check the matrix on Verification.
Try it
bun run dev:cli -- my-app --yes --preset=typescript-fullstack --dir=../projects
cd ../projects/my-app && bun install && bun run ciIf CI fails, read root AGENTS.md before blaming the template—env URLs are the usual culprit.