chore(schema): bump kurrent-agent-schema (Python) to 0.4.0

[alexeyzimarev]

Summary

• Aligns Python package version with the .NET schema package, which landed at 0.4.0 in DEV-1668 / #45 but inadvertently left the Python `pyproject.toml` at 0.3.1.
• Required before tagging `schema-python-v0.4.0`: the PyPI publish workflow verifies that the tag's version matches `pyproject.toml`.

Test plan

• `uv run pytest` passes locally (23/23).
• No code changes — pure version bump in `pyproject.toml`.

🤖 Generated with Claude Code

[qodo-code-review]

Review Summary by Qodo

Bump kurrent-agent-schema Python package to 0.4.0

📦 Other

Walkthroughs

Description

• Bump kurrent-agent-schema Python package version to 0.4.0
• Aligns Python version with .NET schema package (DEV-1668)
• Enables PyPI publish workflow tag verification

Diagram

flowchart LR
  A["pyproject.toml<br/>version 0.3.1"] -- "version bump" --> B["pyproject.toml<br/>version 0.4.0"]
  B -- "matches" --> C["schema-python-v0.4.0 tag"]

Loading

File Changes

1. schema/python/pyproject.toml ⚙️ Configuration changes +1/-1

Version bump to 0.4.0

• Updated version field from 0.3.1 to 0.4.0
• Aligns Python package with .NET schema package version
• Enables PyPI publish workflow to verify tag matches version

schema/python/pyproject.toml

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (2) 📘 Rule violations (0)

1. Stale uv.lock version 🐞 Bug ☼ Reliability

Description

schema/python/pyproject.toml sets version to 0.4.0, but schema/python/uv.lock still records the
editable project as 0.3.1, leaving the lockfile inconsistent with the package metadata. This is
particularly risky because CI workflows sync with uv sync --frozen in schema/python, which relies
on uv.lock being up-to-date.

Code

schema/python/pyproject.toml[7]

+version = "0.4.0"

Evidence

The PR updates the project version to 0.4.0, but the checked-in uv.lock still declares the local
editable kurrent-agent-schema package as version 0.3.1. Multiple CI workflows run `uv sync
--all-extras --frozen` in schema/python, so the repository’s frozen environment definition should be
regenerated to match the updated pyproject metadata.

schema/python/pyproject.toml[5-10]
schema/python/uv.lock[23-29]
.github/workflows/schema-ci-python.yml[36-39]
.github/workflows/schema-cross-language.yml[33-36]
.github/workflows/schema-publish-pypi.yml[46-49]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`schema/python/pyproject.toml` was bumped to version `0.4.0`, but `schema/python/uv.lock` still declares the editable `kurrent-agent-schema` package as `0.3.1`. CI uses `uv sync --frozen` in `schema/python`, so the lockfile should be updated to reflect the new package metadata.

## Issue Context
The repo has multiple workflows that run `uv sync --all-extras --frozen` in `schema/python`, which assumes `uv.lock` is already consistent with `pyproject.toml`.

## Fix Focus Areas
- schema/python/uv.lock[23-29]
- schema/python/pyproject.toml[5-10]
- .github/workflows/schema-ci-python.yml[36-39]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. Release docs version drift 🐞 Bug ⚙ Maintainability

Description

The package version is now 0.4.0, but the Python package docs still describe older versions
(CHANGELOG starts at 0.3.1; README states Package: 0.2.0). This creates misleading release
documentation when tagging/publishing 0.4.0.

Code

schema/python/pyproject.toml[7]

+version = "0.4.0"

Evidence

After the pyproject version bump to 0.4.0, the adjacent release documentation in this package
directory remains on older versions (CHANGELOG top entry 0.3.1; README ‘Package: 0.2.0’). This
inconsistency is directly observable in-repo and will confuse consumers reading docs for the 0.4.0
tag.

schema/python/pyproject.toml[5-10]
schema/python/CHANGELOG.md[1-4]
schema/python/README.md[55-58]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The package was bumped to `0.4.0` in `pyproject.toml`, but `CHANGELOG.md` and `README.md` still present older package versions. Update these files so the release documentation matches the package being tagged/published.

## Issue Context
This PR is explicitly intended to prepare for tagging `schema-python-v0.4.0`, so version-facing docs should not contradict the package version.

## Fix Focus Areas
- schema/python/CHANGELOG.md[1-10]
- schema/python/README.md[55-58]
- schema/python/pyproject.toml[5-10]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

[qodo-code-review]

1. Stale uv.lock version 🐞 Bug ☼ Reliability

schema/python/pyproject.toml sets version to 0.4.0, but schema/python/uv.lock still records the
editable project as 0.3.1, leaving the lockfile inconsistent with the package metadata. This is
particularly risky because CI workflows sync with uv sync --frozen in schema/python, which relies
on uv.lock being up-to-date.

Agent Prompt

## Issue description
`schema/python/pyproject.toml` was bumped to version `0.4.0`, but `schema/python/uv.lock` still declares the editable `kurrent-agent-schema` package as `0.3.1`. CI uses `uv sync --frozen` in `schema/python`, so the lockfile should be updated to reflect the new package metadata.

## Issue Context
The repo has multiple workflows that run `uv sync --all-extras --frozen` in `schema/python`, which assumes `uv.lock` is already consistent with `pyproject.toml`.

## Fix Focus Areas
- schema/python/uv.lock[23-29]
- schema/python/pyproject.toml[5-10]
- .github/workflows/schema-ci-python.yml[36-39]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools