chore: bump version to v0.1.3-rc.1

[kaiitunnz]

Purpose

Release-prep bump for the v0.1.3-rc.1 release candidate. Synchronizes all published package versions and first-party pins ahead of tagging and the TestPyPI publish.

Changes

• pyproject.toml, cli/pyproject.toml, cli/stack/pyproject.toml, hook/pyproject.toml, sdk/pyproject.toml, sdk/stack/pyproject.toml — bump version to 0.1.3rc1 and update internal first-party == pins to match.
• sdk/src/flowmesh/_version.py (_STATIC_VERSION) and src/shared/_version.py (FLOWMESH_RELEASE_VERSION) — bump the runtime version literals.
• uv.lock — re-locked for the new synchronized version.

All edits are mechanical output of scripts/dev/bump_version.py 0.1.3rc1 + uv lock. 0.1.3rc1 is the PEP 440 normalization of the v0.1.3-rc.1 tag.

Design

N/A — version bump only.

Test Plan

uv run scripts/dev/bump_version.py 0.1.3rc1
uv lock
uv run scripts/ci/check_release_version.py --tag v0.1.3-rc.1

Test Result

$ uv run scripts/ci/check_release_version.py --tag v0.1.3-rc.1
Release package versions are synchronized at 0.1.3rc1.

---

Pre-submission Checklist

• I have read the contribution guidelines.
• I have run pre-commit run --all-files and fixed any issues. (Ran on the bump commit via pre-commit hooks.)
• I have added or updated tests covering my changes (if applicable).
• I have verified that uv run pytest tests/ passes locally.
• If I changed shared schemas or proto definitions, I have checked downstream compatibility across Server and Worker. (No schema/proto changes.)
• If I changed the SDK or CLI, I have verified the affected packages work (uv sync --all-packages --group ci --frozen). (uv lock re-locked cleanly.)
• If this is a breaking change, I have prefixed the PR title with [BREAKING] and described migration steps above. (Not a breaking change.)
• I have updated documentation or config examples if user-facing behavior changed. (No user-facing behavior change.)

[timzsu]

LGTM.