release

```d2 understand: |md Understand the release automation by reading AGENTS.md and .github/workflows/release*.yml. | check_changes: |md Check each package under packages/, sdks/, and repo root for changes since the last release (by tag). Note packages/pythinker-code is a thin wrapper and must stay version-synced with pythinker-code. | has_changes: "Any packages changed?" confirm_versions: |md For each changed package, confirm the new version with the user. Follow the project versioning policy: patch is always 0, bump minor for any change, major only changes by explicit manual decision. | update_files: |md Run `uv run python scripts/release.py --set-version X.Y.Z [--bump-core A.B.C --bump-host A.B.C]`. It rewrites pyproject.toml:3, the sub-package pins, uv.lock, all three changelog files (preserving the authored Unreleased body), and the README/asset names from the single source of truth, then runs the local gates and opens the `release/X.Y.Z` PR. There is no `--bump-review` (review is frozen at 0.1.0). | root_change: "Is the root package version changing?" sync_pythinker_code: |md Sync packages/pythinker-code/pyproject.toml version and dependency `pythinker-code==<version>`. | sync_kagent: |md Sync rust/Cargo.toml workspace version to match the root package version. | uv_sync: "release.py already runs `uv lock` + `uv sync --frozen --all-extras --all-packages` as Phase-2/3 steps; no separate uv sync needed." gen_docs: |md Follow the gen-docs ski...