# Shared report HTML contract
Canonical rendering contract for polished local CSE report artifacts: the war room agenda,
team shoutouts, and any other briefing an operator opens in a browser or prints for a meeting.
The stylesheet lives beside this file at [`report-html/cse-report.css`](report-html/cse-report.css).
This contract governs presentation only. Evidence rules stay with the calling skill; a pretty
report built on unsourced claims is still a failed report.
## When to render HTML
Render the HTML artifact when the report is meant to be read by a group: a meeting agenda, a
shoutouts segment, an onsite briefing, a readout an operator will screen-share or print.
Skip it for working notes, scratch analysis, and anything headed straight into another tool.
Always write the markdown source first, then render HTML beside it with the same basename.
The markdown stays the editable source of truth; the HTML is the presentation copy.
## Document shape
One self-contained `.html` file. No build step, no external CSS, no JavaScript framework.
The only permitted remote references are the Postman logo, Google Fonts, and the Postman
Degular `@font-face` sources already present in the stylesheet.
Assemble in this order:
1. `` and ``.
2. ``: UTF-8 charset, viewport, a one-sentence `meta name="description"`, a title in
`Subject - Qualifier` form, the Postman favicon, font preconnects and the fonts stylesheet
link, then the entire canonical stylesheet inlined in a single `