* chore(release): add v1.0.8 changelog, customer email, and thumbnail artifacts
* chore(release): sharpen the v1.0.8 email and encode the rules in /release
The subject and section headers named areas (Facebook Pages, Asset
Library) instead of what got better, so a subscriber could not tell
from the inbox what the release did for them.
- Lead on the widest-reach change (Business Portfolio Pages) rather
than the newest one, and match the section order to the subject
- Say plainly that Asset Library reuse is new for the API and MCP
only, since the in-app path already worked
- Drop the four bullets that repeated a theme section verbatim
- Reorder the thumbnail chips to follow the sections
.claude/commands/release.md carries the same rules so the next release
starts there: subject pattern, ordering by reach, the already-existed-
in-app trap, header wording, and no duplication between prose and lists.
c66c68b115