chore: bump version to 0.2.1

[0xKT]

Summary

Bump the package version from 0.2.0 to 0.2.1 for the next release. Only pyproject.toml and uv.lock change.

Since v0.2.0, main merged 31 PRs (3 feat, 22 fix, 5 docs, 1 refactor), none carrying a BREAKING CHANGE footer. The three features are small UI additions (wizard steps, file-bar download button, task-palette stop buttons), so this is a patch bump, as v0.1.12 and v0.1.13 were. The tag and release notes follow once this lands.

Type

• Fix
• Feature
• Docs
• CI / tooling
• Refactor
• Other

Verification

• uv lock in a fresh worktree: Resolved 250 packages, Updated raven v0.2.0 -> v0.2.1

• git diff --stat origin/main..HEAD: pyproject.toml and uv.lock, 2 insertions, 2 deletions

• PYTHONPATH=. python scripts/check_commit_messages.py origin/main..HEAD: exit 0

• npx commitlint --from origin/main --to HEAD --config commitlint.config.cjs: exit 0

• No test run: the change is version metadata only.

• Relevant tests pass locally

• Relevant lint / type checks pass locally

• User-facing docs or screenshots are updated when needed

Risk

No code change. Rollback is reverting this commit before any v0.2.1 tag is pushed.

• Security impact considered
• Backward compatibility considered
• Rollback path is clear for risky changes

Related Issues

N/A

[gloryfromca]

No blockers; this can merge as far as I am concerned.

Reviewed the complete github/main...HEAD diff and the surrounding release/version flow. The package version and editable lock entry move together to 0.2.1, matching the established release-bump pattern; runtime callers obtain raven.__version__ from package metadata. The remaining 0.2.0 strings are independently versioned plugins, historical documentation, or dependency versions rather than missed core-version sites.

I also covered repository rules (AGENTS.md, CLAUDE.md, and CONTEXT-MAP.md), commit and branch conventions, callers, release history, backward compatibility, test integrity, and architecture boundaries. No tests were changed or weakened, and this metadata-only diff crosses no architecture boundary.

Local verification:

• uv lock --check
• uv run --frozen --python 3.12 --extra dev pytest -q tests/test_package_skeleton.py tests/test_a2a_card.py tests/test_evolver_node_core_version.py (32 passed)
• commit-message and PR-title policy checks
• git diff --check github/main...HEAD
• installed metadata reports 0.2.1

All completed GitHub checks are green; three unit-test shards were still running when reviewed.