publishlisted

# Platform publishing — public immediately after HITL approval Publishes the finished artifacts in `output/` with the per-platform publish tools. **The publish tools have no review gate, so calling one = instantly public.** This skill's approval gate (§2) and the native permission prompt that fires on every publish call (never pre-approved) are the two lines of defense. Don't nudge the user into promoting that prompt to "always allow". ## Absolute rules (violation = stop immediately) 1. **User approval before publishing is mandatory (HITL)** — before any call, present the full final text for each platform with AskUserQuestion and get explicit approval. IG can't swap the image after publishing, and every platform pins it to a brand account (irreversible). 2. **No cross-post copy-paste** — the same sentence must not go out on two platforms verbatim. 3. **Never expose a token in plain text** — handle tokens only as files under `~/.config/social-flow/<channel-slug>/`. Even when debugging with curl, use inline `$(cat …)` references only; never print token values or the access_token field into the conversation. 4. **No distorting the facts** — publish only within the approved artifacts. If a caption needs fixing on the spot, take the corrected version back through the approval gate. 5. **Respect the limits** — Threads 250/24h, IG 100/24h, YouTube uploads 100/day (the videos.insert-only Video Uploads bucket, 1 unit per call — no reason to ration e