[birkholz-cubert]

What

• Bump [project].version from 3.6.0.0 to 3.6.1.0.
• Raise the cuvis-il requirement from >=3.6.0,<3.7.0 to >=3.6.1,<3.7.0.
• Add ## [3.6.1.0] - 2026-10-16 to CHANGELOG.md with the SDK statement lines and a ### Changed entry for the requirement.
• tests/test_processing_context.py::test_spectra_survive_legacy_cu3_round_trip: match the .cu3sp sidecars by glob instead of exact name.

Why

• cuvis SDK 3.6.1 is released, and the version scheme ties GENERATION.MAJOR.MINOR to the SDK the wrapper targets.
• CONTRIBUTING.md ties the cuvis-il requirement to the targeted SDK, so cuvis 3.6.1.0 resolves only an interface layer compiled against 3.6.1.
• No wrapper code changes: cuvis.BindingInfo.built_against comes from cuvis-il at runtime, so it reports 3.6.1 as soon as cuvis-il 3.6.1.0 is installed.
• SDK 3.6.1 appends a content hash to the reference spectrum sidecars (target_spectrum_ref_<md5>.cu3sp instead of target_spectrum_ref.cu3sp). The sidecars are still written once per slot and reload bit-identically; only the hardcoded names in the test broke.

Notes

• cuvis-il 3.6.1.0 is on PyPI and cubertgmbh/cuvis_pyil:3.6.1-ubuntu24.04 exists, so both the CI tests and the release's image check have what they need.
• Full test suite, ruff format --check . and ruff check . pass in both cuvis_pyil:3.6.0-ubuntu24.04 and cuvis_pyil:3.6.1-ubuntu24.04 (172 passed, 5 skipped).
• Validated locally: check_changelog.py --version 3.6.1.0 passes. >=3.6.1,<3.7.0 accepts SDK 3.6.1 and does not open the range to pre-releases, which is what the Verify the cuvis-il requirement agrees with the version step checks.

Pitfalls

• Adjust the changelog date if the merge or tag happens on a later day.
• Users on SDK 3.6.0 can no longer install the latest cuvis; they need to pin cuvis==3.6.0.0. This was already the case in practice, because the old range resolved to cuvis-il 3.6.1.0 as well.
• Merging does not release anything; the release starts when v3.6.1.0 is tagged on main.
• Code that looks up the sidecar files by their exact 3.6.0 name breaks against SDK 3.6.1. That is an SDK behavior change, not a wrapper change, but it is worth a line in the SDK release notes.