compact launch post, then publish one focused feature explainer per reply.

Follow-up replies should not repeat "new in VERSION" or the version number

when the thread context already makes it obvious.

- Peter's preferred thread workflow: first agree on the generic launch tweet,

then proceed through follow-up tweets one by one. When he says `next`, provide

or copy the next follow-up only; do not dump the full thread again unless asked.

- Every follow-up tweet should include a docs URL for that specific feature.

Prefer a bare URL over `Docs: <url>` unless the label is needed for clarity.

Keep follow-ups concise: around 160-220 raw characters is usually the sweet