artifact-reviewlisted

# Artifact Review Artifact Review is the browser loop for proposed work. Build or update one HTML file, let the user point, choose, draw, or write, then edit that same source until the review is complete. Direct factual answers and fully specified edits can stay in conversation. ## Core contract - Keep the artifact in the user's workspace. The review runtime observes it but never edits it; the source HTML or Mermaid remains authoritative. - Resolve `SKILL_ROOT` to this file's directory. On POSIX use `AREV="$SKILL_ROOT/scripts/arev"`; on Windows use `scripts\arev.cmd`. Never assume `arev` is on `PATH` or hardcode an agent-specific install directory. - Treat every printed `SESSION` URL as a bearer secret. ## Start one artifact Run the combined install/design/playbook brief once. Name known playbooks; if the type is unclear, inspect the index and fetch only matching ids: ```bash "$AREV" brief plan table "$AREV" new "/absolute/path/to/review.html" --title "Review title" ``` Fill only the scaffold's `<!-- arev:content -->` region. Every diagram is Mermaid in `<pre class="mermaid" id="stable-id">` - never hand-built div boxes, and never a CDN script; the review server renders Mermaid offline and attaches the editable whiteboard only to those blocks. Diagram colors and fonts derive from the page palette automatically and follow theme flips, so never set a Mermaid theme or `%%init%%` colors. Then audit the file before anyone opens it. `check` reads the artifact and the