release: srdcheck 0.7.0

README.md

@@ -9,7 +9,7 @@ cited when a rule is applied, reproducible, offline, and honest enough to refuse
 questions outside the shipped scope. The rules lawyer for agents — including an
 agent acting as the authorized DM.
 
-> **Status: v0.6.0 alpha — young but real, building in the open.** The kill tests that shaped the product — including the one that killed half our original idea — are in [eval/RESULTS-phase0.md](eval/RESULTS-phase0.md); the with/without-rails demo is in [demo/mage-hand/](demo/mage-hand/); the truth scorecard below is generated by CI.
+> **Status: v0.7.0 alpha — young but real, building in the open.** The kill tests that shaped the product — including the one that killed half our original idea — are in [eval/RESULTS-phase0.md](eval/RESULTS-phase0.md); the with/without-rails demo is in [demo/mage-hand/](demo/mage-hand/); the truth scorecard below is generated by CI.
 
 Runtime and operating-system guarantees are defined in the [support matrix](docs/support-matrix.md): Python 3.10–3.13, a full Ubuntu suite, and explicit installed-artifact smoke contracts on Windows and macOS.
 

docs/capability-map.json

@@ -3,21 +3,21 @@
  "generated_from": "srdcheck/capability_claims.json + srdcheck capabilities + adapter queries.json",
  "engine": {
   "name": "srdcheck",
-  "version": "0.6.0"
+  "version": "0.7.0"
  },
  "machine_contracts": {
   "verdict_schema_version": "1.0",
   "capabilities_schema_version": "2.0",
   "refusal_contract_version": "1.0",
   "compatibility_window": "N/N-1",
   "supported_engine_minors": [
-   "0.6",
+   "0.7",
    "0.5"
   ],
   "why_stability": "non-contractual"
  },
  "release_tuple": {
-  "engine_version": "0.6.0",
+  "engine_version": "0.7.0",
   "adapters": [
    {
     "identifier": "srd-5.1",

docs/capability-map.md

@@ -24,7 +24,7 @@ Machine metadata lives in `data`; agents branch on it instead of parsing `why`.
 
 ## Release identity
 
-Engine `0.6.0`; verdict schema `1.0`; compatibility `N/N-1` over `0.6, 0.5`.
+Engine `0.7.0`; verdict schema `1.0`; compatibility `N/N-1` over `0.7, 0.5`.
 
 | adapter | adapter version | data version | rules version | digest |
 |---|---:|---:|---:|---|

pyproject.toml

@@ -9,7 +9,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "srdcheck"
-version = "0.6.0"
+version = "0.7.0"
 description = "Deterministic rules verdicts for game-running agents — cited, reproducible, honest about jurisdiction. SRD 5.2.1 is adapter #1."
 readme = "README.md"
 requires-python = ">=3.10"

server.json

@@ -2,7 +2,7 @@
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "name": "io.github.chaoz23/srdcheck",
  "description": "Scoped deterministic SRD 5.2.1 rules checks for agents \u2014 applied rules cited, boundaries explicit.",
- "version": "0.6.0",
+ "version": "0.7.0",
  "repository": {
   "url": "https://github.com/chaoz23/srdcheck",
   "source": "github"
@@ -12,7 +12,7 @@
    "registryType": "pypi",
    "registryBaseUrl": "https://pypi.org",
    "identifier": "srdcheck",
-   "version": "0.6.0",
+   "version": "0.7.0",
    "runtimeHint": "uvx",
    "runtimeArguments": [
     {

srdcheck/contract.py

@@ -31,7 +31,9 @@
 # shipped minor might be 0.7 rather than an invented 0.8.  Make each new minor
 # name its actual predecessor so a version bump cannot silently claim a window
 # that has no fixture.
-PREVIOUS_ENGINE_MINOR = {"0.6": "0.5"}
+# 0.6 lived on main but was never published; 0.5 is therefore the actual
+# previous public minor for both the internal 0.6 line and the 0.7 release.
+PREVIOUS_ENGINE_MINOR = {"0.6": "0.5", "0.7": "0.5"}
 
 
 def is_semver_2_0(value):

tool.json

@@ -1,6 +1,6 @@
 {
  "name": "srdcheck",
- "version": "0.6.0",
+ "version": "0.7.0",
  "description": "Deterministic rules verdicts over the SRD for game-running agents. Exit codes are scoped results: 0 passes the named checked scope, 1 conflicts with it, 2 cannot-adjudicate (unknown content or a DM-authority decision, including when the caller is the agent-DM — an honest refusal, not an error). Applied rules carry citations; boundary refusals do not invent them.",
  "status": "alpha; versioned machine schemas and the N/N-1 semantic window are reported by `capabilities`",
  "rulesets": [