Fix CI: stop hard-coding version in test_version_is_set

The boot test asserted __version__ == "0.3.6"; the 0.3.7 bump made it
stale and CI on main went red (the local run had passed because the
suite ran before the version bump). Assert the version is set and
PEP 440-ish instead, so future release bumps don't require editing
this test. Release + Integration workflows were unaffected.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: vosesoft

tests/unit/test_server_boot.py

@@ -1,11 +1,19 @@
+import re
+
 import pytest
 
 from modelrisk_mcp import __version__
 from modelrisk_mcp.server import mcp
 
 
 def test_version_is_set() -> None:
-    assert __version__ == "0.3.6"
+    # Don't hard-code the literal — that turns every release bump into a
+    # required test edit (and a red CI when it's forgotten). Assert the
+    # version is set and PEP 440-ish instead.
+    assert isinstance(__version__, str)
+    assert re.fullmatch(r"\d+\.\d+\.\d+([.-]?[A-Za-z0-9.]+)?", __version__), (
+        f"__version__ not a valid version string: {__version__!r}"
+    )
 
 
 def test_server_name() -> None: