e2e-report-rendererlisted

# E2E Report Renderer — HTML Rendering Protocol This skill is **normative**. **MUST / MUST NOT / SHOULD** carry RFC-2119 meaning. Rules are cited by ID (`REN-n`). > **Authority**: [`AGENTS.md`](../../../AGENTS.md) is binding. This skill is a *view* layer over `e2e-runner`'s data; it never re-interprets results or fabricates them. > **Shared contract**: [`docs/e2e-scenarios/CONTRACT.md`](../../../docs/e2e-scenarios/CONTRACT.md) is the SSOT for the run-result JSON schema and mask classes. Its bootstrap source and validator ship with the required `e2e-scenario-author` dependency. If this skill disagrees with the project contract, the project contract wins. > **Input**: a run JSON (or set of run JSONs) under `test-report/e2e/`. **Output**: an HTML file in the same directory. HTML output is git-ignored by project policy; if you want history, the JSON beside it is the SSOT. > **Reference loading:** Apply the common REN contract below and the project report/masking contract. > Only `trend` or `compare` loads [comparison modes](reference/comparison-modes.md), the canonical REN-18..21 > definitions. Read [HTML security](reference/kb/self-contained-html-security.md) if safe embedding is unclear, > [artifact handling](reference/kb/artifacts-screenshots-traces.md) for missing/truncated evidence, or > [accessibility](reference/kb/readable-failure-reporting.md) when changing the shipped visual template. > [Principles](reference/principles.md) explain rationale; [the KB index](referenc