Align current-boundary docs with v0.2.2 (#25)

Author: senseibelbi

docs/dev_experience_content_plan.md

@@ -1,6 +1,6 @@
 # Documentation Refresh Content Plan (Phase 2)
 
-> Historical planning artifact. The `v0.2.0` release has since repositioned the public server around evidence federation and interop; use this document as background context, not as the current public contract.
+> Historical planning artifact. The `v0.2.2` release preserves the public server boundary around evidence federation and interop; use this document as background context, not as the current public contract.
 
 ## Goals
 - Update public and internal documentation to reflect MCP Phase 2 architecture, guardrails, observability, and developer tooling.

docs/development_guide.md

@@ -2,7 +2,7 @@
 
 This document provides guidance for developers who want to extend or modify the EPA CompTox MCP implementation.
 
-The released `v0.2.0` public server is an evidence-and-federation MCP. Predictive and orchestrator code still exists in-repo, but it is not part of the default public MCP surface unless explicitly registered and documented.
+The released `v0.2.2` public server is an evidence-and-federation MCP. Predictive and orchestrator code still exists in-repo, but it is not part of the default public MCP surface unless explicitly registered and documented.
 
 ## Project Structure
 

docs/model_cards_and_policies.md

@@ -1,6 +1,6 @@
 # Model Cards & Guardrail Policies
 
-> This guide primarily covers in-repo predictive and orchestrator assets. These components remain experimental and are not part of the default public MCP tool catalog in `v0.2.0`.
+> This guide primarily covers in-repo predictive and orchestrator assets. These components remain experimental and are not part of the default public MCP tool catalog in `v0.2.2`.
 
 This guide explains how to publish human-readable summaries for machine-readable model cards and applicability-domain (AD) policies, interpret guardrail outcomes, and follow the governance workflow required for release sign-off.
 

docs/observability_requirements.md

@@ -1,6 +1,6 @@
 # Observability & Governance Requirements (MCP Phase 2)
 
-> Historical/internal planning document. These requirements cover broader transport, predictive, and orchestrator ambitions beyond the current default public MCP surface released in `v0.2.0`.
+> Historical/internal planning document. These requirements cover broader transport, predictive, and orchestrator ambitions beyond the current default public MCP surface released in `v0.2.2`.
 
 ## Overview
 To support MCP Phase 2, the platform must expose consistent telemetry, audit, and policy hooks across transport, metadata, predictive services, and the GenRA orchestrator. This document captures the requirements aligned with stakeholder needs.

docs/predictive_services.md

@@ -1,6 +1,6 @@
 # Predictive Micro-Server Harness
 
-> Experimental/internal guide. The predictive service harness described here is not part of the default public MCP tool catalog released in `v0.2.0`.
+> Experimental/internal guide. The predictive service harness described here is not part of the default public MCP tool catalog released in `v0.2.2`.
 
 Phase 2 introduces a shared harness for the TEST, OPERA, and GenRA predictive services. The goal is to give all model micro-servers a consistent structure for request validation, applicability-domain enforcement, and response formatting.
 

docs/releases/mcp_phase2_planning_snapshot.md

@@ -1,6 +1,6 @@
 # MCP Phase 2 Planning Snapshot (2025-10-25)
 
-> Historical planning snapshot retained for archive purposes. It does not describe the current public `v0.2.0` release boundary.
+> Historical planning snapshot retained for archive purposes. It does not describe the current public `v0.2.2` release boundary.
 
 This snapshot captures the planning workspace state after completing the MCP Phase 2 rollout and associated CTX migration tasks.
 

docs/workflow_testing_strategy.md

@@ -1,6 +1,6 @@
 # Workflow Testing Strategy – MCP Phase 2
 
-> Historical/internal workflow-planning document. The released `v0.2.0` public MCP server is centered on evidence federation and interop; predictive and orchestrator workflow coverage described here remains experimental and non-canonical for the default public surface.
+> Historical/internal workflow-planning document. The released `v0.2.2` public MCP server is centered on evidence federation and interop; predictive and orchestrator workflow coverage described here remains experimental and non-canonical for the default public surface.
 
 ## Objectives
 - Guarantee transport, predictive, and orchestrator services behave reliably across success, guardrail, and failure scenarios.

tests/test_release_metadata.py

@@ -26,6 +26,15 @@
 )
 DEVELOPMENT_GUIDE_PATH = ROOT_DIR / "docs" / "development_guide.md"
 INTEROP_SMOKE_SCRIPT_PATH = ROOT_DIR / "scripts" / "mcp_interop_smoke.py"
+CURRENT_BOUNDARY_DOC_PATHS = (
+    ROOT_DIR / "docs" / "development_guide.md",
+    ROOT_DIR / "docs" / "predictive_services.md",
+    ROOT_DIR / "docs" / "model_cards_and_policies.md",
+    ROOT_DIR / "docs" / "workflow_testing_strategy.md",
+    ROOT_DIR / "docs" / "dev_experience_content_plan.md",
+    ROOT_DIR / "docs" / "observability_requirements.md",
+    ROOT_DIR / "docs" / "releases" / "mcp_phase2_planning_snapshot.md",
+)
 
 
 def _read_text(path: Path) -> str:
@@ -152,3 +161,12 @@ def test_live_interop_fixture_refresh_path_is_documented() -> None:
     assert "tests/golden/interop_live" in docs
     assert "--capture-dir" in docs
     assert "--refresh-live-fixtures" in docs
+
+
+def test_current_boundary_docs_reference_current_release_version() -> None:
+    version = _project_version()
+    for path in CURRENT_BOUNDARY_DOC_PATHS:
+        text = _read_text(path)
+        assert (
+            f"v{version}" in text
+        ), f"{path} should reference the current release version"