[hmziqagent]

From the what-next dossier (R1). Everything merged since the v0.1.0 tags — the runner remaining-work closeout (#20) and the snap backend (#21, #22) — is invisible to registry consumers until a 0.2.0 cut. This is the prep; the publish itself is the publish.yml dispatch (dry-run first).

What this does

• Bumps the workspace version to 0.2.0 and rewrites all 114 intra-workspace dependency requirements to match — the lockstep gate requires a single version across the 33-crate PUBLISH_SET, so all crates republish together.
• Writes the [0.2.0] - 2026-10-12 changelog sections for the six crates that keep changelogs: runner gets the full API additions (TokioRunnerOptions/TokioRunnerBuilder, stdin_bytes, timeout_policy, StdinFailed kill-and-reap parity, redact-by-default logs, spans) and apps gets the snap surface. registry/fs/installer/mise changed nothing publicly since 0.1.0 and say so honestly — registry's stale [Unreleased] content was actually inside the v0.1.0 tag, so it was folded into [0.1.0] as a bookkeeping fix rather than re-documented as new.
• No code changes: manifests and changelogs only. cargo metadata lockstep-verified at 0.2.0 across all 33 packages; the CI Publish readiness gate is the authoritative check.

After merge

Dispatch Publish crates with dry_run=true, inspect the ordering/lockstep output, then re-dispatch for real. Then tunnel's git-rev pin can repoint at the published 0.2.0.