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: npm ci --ignore-scripts, node --check kc-check-imports.mjs and the CLI --help smoke check passed. Repository-local update/check and diff checks passed.

Expected versions:

repo: 0.1.0 -> 0.1.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 81c3d1b after native Codex fallback review. Hermes repository enrollment is unavailable outside its existing static allowlist; this review does not claim an independent Hermes verdict.

package.json and both owned lock metadata fields advance to 0.1.1 without dependency resolution changes or release-engineering behavior changes.

The full repository diff, standalone engine, component configuration, pinned read-only PR workflow and applicable acceptance tests were reviewed. The helper is byte-identical to the shared tested source (21 acceptance tests plus full toolkit validation passed). Existing repository checks passed. The approval gate rechecks the actual PR title/body and current upstream base, synchronized mirrors, and required CI before normal protected merge. No blockers found. No release, tag or package publication is authorized by this approval.