publishlisted

# Publish an artifact Share a finished HTML artifact (usually a progress report or the academic map) so another adult in the child's life — a co-parent, a tutor — can view it. Same config vs status contract as AgentWorks: - `publish.json` (at the workspace root) — declarative config: `enabled`, the destination, and which files it covers. - `publish/status.json` — the operational result of the last publish (state, timestamps, published URLs/paths, errors). Never write status into `publish.json`. ## Steps 1. **Read config.** `cat publish.json`. If it is missing, do NOT publish silently: tell the parent publishing isn't set up and ask where they'd like to share (a shared/synced folder, a static host, Google Drive, GitHub Pages). Setting up the destination is a one-time decision. 2. **First publish is ATTENDED.** Never do the first (verifying) publish unattended — confirm the destination with the parent so nothing goes to the wrong place. Only re-publish automatically once `publish/status.json` shows the destination is already `verified`. 3. **Publish** the covered files (e.g. `reports/*.html`) using your shell. Easiest: **Google Drive via the `gws` CLI** — `gws drive +upload` the report, then share the link (the parent already has `gws` authenticated). Other options: copy to a synced folder, or push to a Pages branch, as configured. Never publish parent-only files — any `*-KEY.md`/`*-KEY.html` answer key, or `memory/` — or secrets. 4.