Fix VCS versioning after dev tags

[S1ro1]

Summary

• Make renderers installable from commits after the renderers-v0.1.8.dev4 tag by using setuptools-scm semver-pep440 versioning.
• This lets the routed-experts sidecar parser from PR Handle routed experts as response sidecar #54 be consumed directly from a git/submodule commit instead of falling back to stale installed code.

Verification

• uv run --frozen python - <<PY ... imported renderers.client from the workspace and resolved version 0.1.9.dev1+g3177399b7.d20260521.
• Mocked compact /inference/v1/generate JSON and verified renderers.client.generate() returns routed_experts.data as memoryview.

Note

Fix VCS versioning by setting version_scheme to semver-pep440 in Hatch config

Sets version_scheme = "semver-pep440" under [tool.hatch.version.raw-options] in pyproject.toml to correct version resolution after dev tags. The default scheme was producing incorrect versions in this scenario.

^{Macroscope summarized ae4d9b8.}

---

Note

Low Risk
Build and packaging metadata only; no runtime application logic changes.

Overview
Configures Hatch VCS versioning to use semver-pep440 via [tool.hatch.version.raw-options], passing through to setuptools-scm so versions resolve correctly after dev release tags (e.g. renderers-v0.1.8.dev4). The default guess-next-dev scheme was not advancing those tags, which blocked installing renderers from arbitrary git commits with sensible PEP 440 dev versions.

^{Reviewed by Cursor Bugbot for commit ae4d9b8. Bugbot is set up for automated code reviews on this repo. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved

This change adds a versioning scheme configuration for the hatch build tool to fix dev release tag versioning. It's a minor build configuration tweak with no runtime impact.

^{You can customize Macroscope's approvability policy. Learn more.}