fix(release): synchronize Python project version

[itsmiso-ai]

Bump pyproject.toml version from 0.1.0 to 0.7.0 to resolve stale metadata gap (issue #174)

Fixes #174

Opened by foreman on review GO (workload wl-misospace-foreman-dispatch-bridge-174).

[its-saffron]

AI Automated Review

Full PR review.

Analysis engine: dsv4f@https://litellm.jory.dev/v1 (openai) — primary route

Recommendation

Approve. This PR synchronizes the pyproject.toml project version from the stale 0.1.0 to the current release 0.7.0, directly resolving the metadata drift described in issue PR 174. The change is a single-line metadata correction with no runtime impact, and CI (docker, test) passed.

Change-by-Change Findings

• pyproject.toml — version = "0.1.0" → version = "0.7.0". The new value matches the current release: the .release-please-manifest.json pins ".": "0.7.0", the v0.7.0 tag exists (commit f97a4c9), and CHANGELOG.md documents [0.7.0]. The version is now consistent with the manifest, tags, and changelog.

Linked Issue Fit

Issue PR 174 asks: "Bump the pyproject.toml version to the current release (or wire it into release-please) so the package metadata stops reporting a stale 0.1.0."

• Ask satisfied: The version is bumped to the current release (0.7.0), which is the first acceptance-criteria option.
• Expected files: The issue names pyproject.toml and release-please-config.json. The PR touches pyproject.toml (one of the two named files). The issue's acceptance criteria are met by the version bump alone — wiring release-please is the alternative, not a requirement.
• Acceptance criteria: pyproject.toml version now matches the current release. pytest tests/ and mypy bridge/ still pass per CI (test check: success). No runtime behavior change — the diff touches only the version line.
• Note: The issue's expected-files list includes release-please-config.json, which this PR does not touch. That is acceptable because the acceptance criteria are satisfied by the version bump alone; the config change was the alternative path, not a mandatory one.

Standards Compliance

The repository's AGENTS.md defines how issues are filed for the autonomous loop (one imperative ask + named file paths). This PR is a fix branch responding to issue PR 174, which was filed with both required elements. The diff touches a file named in the issue (pyproject.toml), so the scope-overlap rail is satisfied. No repository convention is violated.

Tool Harness Findings

Tool harness planning was pending; no harness output was available for this review.

Unknowns or Needs Verification

• Release-please wiring: The issue offered an alternative of wiring pyproject.toml into release-please so the version stays in sync automatically. This PR chose the one-time bump instead, so the version may drift again on the next release unless release-please is later configured. This is not a blocker — the acceptance criteria are met — but it is worth noting that the root cause (release-please not updating pyproject.toml) remains unaddressed.
• No dependency changes: The PR classification lists must_check items for dependency upgrades (breaking API changes, full test suite). This PR is not a dependency upgrade — it is a project version metadata bump — so those checks do not apply. The test suite did run and passed via CI.