themed_markdownlisted

# themed_markdown — the authoring format A document `body` IS themed-markdown — the format md-converter renders. Your job is structure; styling is the renderer's. NEVER write visual instructions (colors, fonts, sizes, themes) — apply the four semantic classes; the theme picks colors. Use ONLY the constructs below; anything else drops silently or breaks the render. `req` = required · `opt` = optional · `≤N` = soft character cap (over-cap wraps awkwardly / overflows a fixed UI slot). ## Frontmatter ``` --- title: Document Title tags: [tag1, tag2] date: YYYY-MM-DD project: Project Name purpose: Brief description --- ``` | Field | Status | Cap | |---|---|---| | `title` | req | ≤40 | | `tags` | req (YAML list; `[]` ok) | — | | `date` | opt | `YYYY-MM-DD` | | `project` | opt | ≤40 | | `purpose` | opt | ≤40 | `date`/`project`/`purpose` -> footer meta cards. The render injects `feature`, `roadmap_status`, `frozen`, `rendered_by`, `source` on top — NEVER write those yourself. Tags = YAML list only; comma-separated (`tags: a, b`) breaks. ## Structure | Syntax | Role | Cap | |---|---|---| | `# Title` | doc title (opt; falls back to `frontmatter.title`) | — | | `## Section` | sidebar tab | ≤28 | | `### Heading` | subsection -> `<h3>` | ≤80 | H4–H6 ⛔. **Tab rule:** every H2 = one tab; content between two H2s belongs to the first. Content between H1 and the first H2 is silently dropped — put intro under an H2 (e.g. "Overview"). Single-section docs may omit H2s (whole doc = one ta