artifactslisted

# Artifacts Author Markdown once, add semantic HTML or inline SVG where layout requires it, then compile the source to responsive HTML. Do not hand-author a complete HTML document and do not edit generated HTML. ## Choose the kind - `plan`: implementation intent, behavior, architecture, validation, risks, and tracking. - `visual`: one visual explanation, infographic, dashboard, comparison, or data story. - `report`: findings, evidence, and recommendations. Follow the shared pipeline; choose figures that make the evidence easier to understand. The kind changes the content contract, not the rendering pipeline. ## Shared pipeline 1. Check the installed CLI: ```bash command -v artifacts ``` If it is missing, report that prerequisite. Do not replace it with a hand-written HTML fallback. 2. Resolve the artifact directory. It lives in the DURABLE HOME, never in a git checkout: ```bash DATE=$(date +%F) ARTIFACTS_DIR="$HOME/.agents/artifacts/$DATE/<slug>" mkdir -p "$ARTIFACTS_DIR" ``` `~/.agents/artifacts/` is outside every repository, is never reaped, and is already date-partitioned. The `<slug>` level exists so two agents working on the same day cannot collide on `plan.md`. Do NOT write into `<repo>/.agents/artifacts/`. That directory is TRACKED — untracked files inside it are what make `git checkout` and `git merge` refuse with "would be overwritten". Writing there also means writing into a primary checkout, which