Matrix Announcement

Content rules for Matrix announcements. matrix-communication does the sending.

The five rules

1. One headline, one purpose.
2. formatted_body in the HTML subset, not Markdown. body is the plaintext fallback — clients aren't required to parse Markdown.
3. Lists beat paragraphs. Enumerable items — findings, projects, failures, tickets — are a <ul>, however long each runs. A bold-led paragraph is emphasis, not structure.
4. Wrap code — and name the thing itself. Commands, paths, versions, IDs, env vars in <code>; multi-line in <pre><code class="language-…">. Name the identifier, not a category standing in for it (html-subset.md).
5. Layout > words → render an HTML card to PNG. Comparisons, dashboards and multi-row tables die in formatted_body.

Type tags (pick one — never stack)

New skill first release · Release feature version · Patch bugfix-only · Digest weekly roundup · Heads-up breaking change or deprecation · Postmortem incident · Findings investigation or audit · RFC proposal seeking feedback

Findings reports group by category of finding, never by who was wrong (structure.md).

Glyphs