feat(release): embed workspace_version in config/general.yaml

[Jammy2211]

Summary

Update the release pipeline to embed the workspace version inside config/general.yaml (under version.workspace_version) in addition to version.txt, so the new config-aware autoconf.workspace.check_version (PyAutoLabs/PyAutoConf#100) finds a source on every workspace clone. Update verify_workspace_versions.sh to mirror the new precedence (general.yaml → version.txt) and fail if the two sources disagree on a checked-out workspace.

API Changes

None — internal CI/CD and pre-build tooling.

Test Plan

• pytest tests/ stays green
• bash verify_workspace_versions.sh dry-run passes against the local checkout (6 workspaces ok, euclid_pipeline SKIP — same as pre-change baseline)
• Next dispatched release writes version.workspace_version into each workspace's config/general.yaml correctly (verify by inspecting the resulting commit)

Full API Changes (for automation & release notes)

Changed Behaviour

• release.yml "Write workspace version" step (was "Write workspace version.txt") — now writes both version.txt and config/general.yaml's version.workspace_version key. The general.yaml edit is a Python shim (regex-based, comment-preserving); sed-based YAML edits are too fragile.
• verify_workspace_versions.sh — resolves the workspace version from config/general.yaml's version.workspace_version first, falls back to version.txt. Fails if both exist and disagree on a workspace.
• CLAUDE.md — documents the new precedence and that the runtime check now fires on every library import.

Migration

• None for users. The new general.yaml key is added by the next release dispatch.

🤖 Generated with Claude Code