chore: adopt automatic version updates

[timeleft--]

Keep versions current in the original change PR with a self-contained updater and a read-only Version policy PR check. Chores (including transitive dependencies) and other maintenance increment patch; features increment minor; breaking changes increment minor before 1.0 and major afterward. One largest increment is calculated from current main and PR intent, idempotently. No tag, GitHub Release, or publication is created.

This adoption applies one increment from verified upstream metadata and synchronizes configured mirrors/lockfile metadata without changing resolved dependencies. Independent components are mapped in .version-policy.json; excluded templates/vendor captures remain outside the policy.

Shared implementation and behavioral tests: https://github.com/MachineWisdomAI/wise-agents-toolkit/pull/103. All 21 shared acceptance tests and the toolkit full verification passed; Claude review was attempted but unavailable (not logged in), so native review was used.

Validation: Full pytest suite: 1116 passed; three assertions tied to 0.7.0 identified. After fixing current-candidate expectations while preserving historical benchmark provenance, all 34 affected tests passed, including exact wheel/sdist fresh install and upgrade tests. CI reruns the complete suite. Repository-local update/check and diff checks passed.

Expected versions:

repo: 0.7.0 -> 0.7.1
Version policy passed.

Enforcement: require Version policy with an up-to-date branch while preserving existing approvals, merge methods and stronger protections. Publication remains with the existing release routine.

[yia-mw-agent]

Approved at exact head 3e3a59d after both isolated Hermes review packets and native consequence-based triage. Hermes found no concrete correctness blockers.

The packets collectively confirm pyproject, uv.lock and runtime fallback 0.7.1, current-version tests derived from metadata, historical benchmark 0.7.0 and frozen commit provenance retained, and the read-only no-publication helper. The helper is byte-identical to the independently reviewed toolkit source, whose 21 acceptance tests and full verification passed; those tests are maintained centrally, not duplicated in this repository. All existing full CI test matrices and security/semantic checks passed. Required Version policy enforcement and strict branch currency are active. The protected merge will use a merge commit, retaining FAVA merge-only settings and existing organization rules.

Encoding/table-format robustness suggestions are nonblocking under the supported macOS/Linux Python environments. Merge queues are not enabled; no queue trigger is required. Historical provenance remains explicit rather than tracking a new version retroactively. No unresolved material findings. No tag, release, package publication or runtime upgrade is part of this adoption merge.