deps: refresh measure-mirror pin 3e2aaf24 + catalog count 38→39 — v0.2.4

CHANGELOG.md

@@ -5,6 +5,22 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
 
 ---
 
+## [0.2.4] — 2026-07-09
+
+### Changed
+- **Refreshed measure-mirror pin** (`5a61ae4` → `3e2aaf24`, both v0.25.0):
+  picks up measure-mirror #25 (catalog specimen `provenance-not-in-the-value`,
+  v1.4 / 39 entries). Docs-only downstream; no probe/API change.
+
+### Fixed
+- **Connect-time DISCIPLINE catalog count 38 → 39** (`server.py`) — the illusion
+  catalog grew to 39 (measure-mirror #25). This stale count was missed by the
+  cross-repo checker's CP2 (which only inspected measure-mirror's own READMEs,
+  not this server's reference) — the checker's CP2 has since been extended to
+  cover this cross-repo reference.
+
+---
+
 ## [0.2.3] — 2026-07-09
 
 ### Changed

mirror_stack_mcp/__init__.py

@@ -1,2 +1,2 @@
 """🪞🔎🪪 Mirror Stack unified MCP server."""
-__version__ = "0.2.3"
+__version__ = "0.2.4"

mirror_stack_mcp/server.py

@@ -65,7 +65,7 @@
 NORMATIVE FORMAT: the ledger format is defined by MIRROR-SPEC v1.0 (measure-mirror
 docs/SPEC.md, ratified & frozen 2026-07-02) — these tools are a reference implementation.
 KNOWN ILLUSIONS: before trusting a surprising result (good OR bad), scan the catalog of
-measurement illusions (measure-mirror catalog/, 38 real sealed cases: gaming, self-catch,
+measurement illusions (measure-mirror catalog/, 39 real sealed cases: gaming, self-catch,
 false-negative guards, contamination). When you retract, consider adding a specimen.
 """
 

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "mirror-stack-mcp"
-version = "0.2.3"
+version = "0.2.4"
 description = "Unified MCP server for the Mirror Stack — claims, actions, provenance + verify-all in one server"
 readme = "README.md"
 requires-python = ">=3.10"
@@ -16,7 +16,7 @@ dependencies = [
     # tracks each mirror's default branch, so an install made before a mirror's release
     # freezes on whatever was HEAD then and never refreshes — that is how a local install
     # ran stale measure-mirror 0.14.3 long after 0.15.1 landed. Bump these on purpose.
-    "measure-mirror @ git+https://github.com/bhyi4/measure-mirror@5a61ae4d9eaad733c60bc87d688f5fed723e419d",   # v0.25.0 — anchor-discipline probes ㉔㉕ + SPEC amendment A2 (anchor_cell/anchor_line_source/known_confounds); v0.24.0 grounding ㉑㉒㉓ + A1; v0.23.0 kill_threshold validation
+    "measure-mirror @ git+https://github.com/bhyi4/measure-mirror@3e2aaf24a614613a3685e7e31581af6dcb5e8ee7",   # v0.25.0 — anchor-discipline probes ㉔㉕ + SPEC amendment A2 (anchor_cell/anchor_line_source/known_confounds); v0.24.0 grounding ㉑㉒㉓ + A1; v0.23.0 kill_threshold validation
     "action-mirror @ git+https://github.com/bhyi4/action-mirror@fd46e90c3e3f0706792c261316f4699d7a6799d8",     # v0.1.0 (ledgers conform to MIRROR-SPEC v1.0)
     "provenance-mirror @ git+https://github.com/bhyi4/provenance-mirror@8edbbfd94772d3718de93271c1f80297c0476043",  # v0.1.0 (ledgers conform to MIRROR-SPEC v1.0)
 ]