solo-artifacts

# solo-artifacts Warm Archive fork of `work-canvas`: produce or publish **one self-contained HTML file** that renders a Solo task/thread for a human to understand and act on. Prefer the real deliverable over a summary page. ## Workflow 1. **Publish Existing Deliverable** if the current task/run names one. Trust only explicit current-task evidence, such as: ```text Deliverable: ./path/to/result.html ``` You may also use a file path named in the current task/thread, or a file you personally created for this task now. Do not scan the workspace by newest file, mtime, or vague filename match; old workspace files can be stale. If several files are named, prefer the product/final deliverable over review/report/panel files unless the user explicitly asks for the review page. Do not switch to review-decision just because the task is in_review. - Existing `.html`: publish it directly. ```bash solo artifact publish --task <task-id> --mode <latest|final> --file <path-to-html> ``` - Existing `.md`, `.txt`, `.json`, `.csv`, or other text/data: create a small self-contained HTML viewer that renders the exact source content, labels the source file near the top, then publish that wrapper. Do not summarize or rewrite the content. - Multiple deliverables or a directory: create a small index artifact with explicit links/file names and a short note about what each file is. If a real deliverable exists, stop here. 2. **Pick the artifact type** a...