[0xKT]

Summary

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

Since v0.2.2, main merged 13 PRs: three features (#802 an experimental Curator that cultivates harness-of-harnesses workers, #805 one header per desk pane, #806 upgrade from the page with progress), four fixes (#792 and #799 name grok and copilot connection failures, #807 records the questions an unattended turn could not ask, #808 keeps the report shape on interrupted research turns) and six docs PRs. None carries a BREAKING CHANGE footer, so this is a patch bump, the way v0.2.1 and v0.2.2 were for their features. The tag and release notes follow once this lands.

Type

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

Verification

• uv lock on a clean worktree cut from origin/main: Resolved 251 packages, Updated raven v0.2.2 -> v0.2.3

• 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

• uv version in the worktree: raven 0.2.3

• 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.3 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.

The release metadata is consistent: pyproject.toml, the root raven entry in uv.lock, uv version, and installed package metadata all report 0.2.3. I found no other Raven version source that this release convention requires updating. Since v0.2.2, the merged history contains no BREAKING CHANGE footer, and recent release commits establish the same patch-bump treatment for feature-bearing release intervals.

Verification: uv lock --check, uv version, installed metadata lookup, scripts/check_commit_messages.py github/main..HEAD, commitlint, git diff --check, and git merge-tree --write-tree HEAD github/main all passed. uv run --all-extras pytest tests/test_rpc_system.py -q -x passed (40 tests). An initial run without extras failed at fixture setup because raven_everos was absent; rerunning with the declared extras passed.

Covered: repository rules, the complete refreshed github/main...HEAD diff, version consumers and release history, backward compatibility, absence of weakened tests, and architecture constraints (no runtime or dependency-graph change).