v0.2 fixes every issue an adopter filed.

An adopter built a marketing site on clear v0.1.4 and filed seven issues — most of them papercuts, two of them genuine bugs. v0.2 ships fixes for all seven, plus a few extras.

What changed

• clear-admin reindex now rebuilds pages_index too, plus a dedicated clear-admin sync-pages for the pages-only case

• CLEAR_SKIP_SAMPLE_SEEDS=1 — bootstrap no longer force-injects sample posts when this is set

• renderTipTap() is now exported from @clearcms/astro so consumers don't write their own renderer

• clearLoader and pagesLoader now watch the bucket via chokidar in fs mode — Astro HMR picks up content edits without a restart

• New diagnostics: clear-admin doctor, clear-admin env, clear-admin config

• clear-admin --help now lists every env var the admin reads, not just the four most common

• --port and --host flags now work on clear-admin start (matching the help text)

The principle

Every issue here is small. Several are one-line fixes. None of them moved the architectural needle. But each one was the first thing a real adopter hit when they sat down with clear, and each one was the moment they had to stop building and start debugging us.

We treat papercuts as bugs. The job of a CMS is to get out of your way; every minute you spend grepping our source for an env var is a minute we owe you back. v0.2 ships in two days because the cost of letting these accumulate is higher than the cost of fixing them.

Upgrade

$ pnpm up @clearcms/admin@latest @clearcms/astro@latest @clearcms/sdk@latest

No protocol changes — your bucket from v0.1.x reads cleanly under v0.2. The new CLI commands are additive; existing scripts keep working.