chore: bump version to v0.1.4

[kaiitunnz]

Purpose

Release-prep bump for the v0.1.4 release. Synchronizes all published package versions and first-party pins ahead of tagging and the PyPI publish. Ships the changes merged since v0.1.3 (#74–#79): Docker-gated SSH dispatch, capability gate extended to all task types, the trl 1.6.0 worker-stack bump, component version reporting, and the vllm_omni / Qwen3 vLLM fix.

Changes

• pyproject.toml, cli/pyproject.toml, cli/stack/pyproject.toml, hook/pyproject.toml, sdk/pyproject.toml, sdk/stack/pyproject.toml — bump version from 0.1.3 to 0.1.4 and update internal first-party == pins to match.
• sdk/src/flowmesh/_version.py (_STATIC_VERSION), cli/src/flowmesh_cli/_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 the mechanical output of scripts/dev/bump_version.py 0.1.4 + uv lock.

Design

N/A — version bump only.

Test Plan

uv run scripts/dev/bump_version.py 0.1.4
uv lock
uv run scripts/ci/check_release_version.py --tag v0.1.4
uv build --all-packages --out-dir dist && uv run scripts/ci/check_package_build.py --dist dist
uv sync --all-packages --group ci --frozen
uv run pre-commit run --all-files
uv run pytest tests/ --ignore=tests/worker/test_mp_executor_cleanup_gpu.py

Test Result

$ uv run scripts/ci/check_release_version.py --tag v0.1.4   # synchronized at 0.1.4
$ uv build --all-packages && check_package_build            # all distributions built + smoke-tested, exit 0
$ uv run pre-commit run --all-files                         # isort / black / ruff / mypy / codespell / gitleaks / sync-requirements passed
$ uv run pytest tests/ --ignore=...gpu                      # 1134 passed

---

Pre-submission Checklist

• I have read the contribution guidelines.
• I have run pre-commit run --all-files and fixed any issues.
• I have added or updated tests covering my changes (if applicable). (Version bump only.)
• 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; built and smoke-tested all distributions).
• 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.)