render-html

# Render HTML Take an artifact (file path or in-context material) plus a one-line intent and produce a single, self-contained HTML file optimized for the moment a human reads it once to make a decision. **Core principle (from Thariq's HTML-over-Markdown thesis):** every invocation produces bespoke HTML, picked widget-by-widget for *this* artifact. **No templates.** A template forces the format back into the Markdown mindset of pre-baked structure and defeats the point. ## When to use Use when **all three** are true: 1. The artifact is a synthesis the human will read once to decide something. 2. The Markdown version would exceed ~100 lines or carry signal a table/SVG/collapsible would express more cleanly (severity, dependency, status, time). 3. No downstream pipeline (Ralph, GitHub, another LLM, grep) consumes the artifact. Common targets in this harness: - `/audit harness` tier-ranked report → filterable findings dashboard - `/strategic-proposal` council artifact → phase-column roadmap with critic challenges inline - `/audit skills` verdict matrix → sortable scoring table with CURRENT/STALE/BROKEN/DELETE badges - Weekly memory digest from N days of `log.md` → timeline coloured by skill outcome ## When NOT to use Skip when the artifact is **source or pipeline input** — Markdown stays the substrate of the harness: - PRDs (`.oh/tasks/*/prd.md`), briefings, commit messages, PR bodies, `CHANGELOG.md` - Memory log entries themselves (`.oh/memory/<date>/log.md`) - Skill/iden...