dashclaw-ship

# dashclaw-ship — full accuracy sweep After a feature lands in DashClaw, many *descriptions* of the system go stale: generated artifacts, hand-authored docs, SDK READMEs, plugin/skill reference narratives, and the marketing site. This skill brings all of them back in line with the live code in one disciplined pass. ## The mission: GET TO MAIN AND LIVE — never defer dashclaw-ship is the single command that resolves **everything** that could keep a change off production, and then **lands it on main and ships it live**. It does not stop at "the docs are accurate," it does not hand back a checklist, and it never says "leave it for you to land." If something blocks main — a failing gate, a stale count, an unbumped version, or a feature stranded on a branch — the job is to *resolve that blocker and drive the code to main*, then confirm the deploy. The accuracy sweep below is the *means*, not the end; stale docs are just one blocker. The end state is: **our code is on main and the deploy is live.** Registry publishing is automated: pushing the version tag fires `release.yml`, which publishes the SDKs **and `@dashclaw/cli`** via OIDC trusted publishing (each job skips versions already on the registry). `npm run release:sdks` is the local fallback (needs the owner's `npm login` + a PyPI token) and the Actions "Run workflow" button on release.yml is the manual re-trigger. **If `cli/**` source changed this ship, bump `cli/package.json` in the same commit** — npm serves stale content...