Skip to content

v0.2.1_stabilization_plan.md

Latest commit

 

History

History
73 lines (52 loc) · 3.52 KB

v0.2.1_stabilization_plan.md

File metadata and controls

73 lines (52 loc) · 3.52 KB
Raw

v0.2.1 Stabilization Plan

Status: completed in v0.2.1. See v0.2.1_release_description.md and 2026-04-12_release_prep.md for the shipped scope and verification sweep.

v0.2.1 should be a narrow stabilization release on top of the v0.2.0 boundary-and-handoff work.

The goal is not to reshape the public role of CompTox MCP again. The goal is to harden the downstream-consumer experience without reopening the boundary with aop-mcp, pbpk-mcp, or the future ToxClaw orchestrator.

Scope

v0.2.1 should focus on exactly three follow-ups:

  1. CTX-backed golden payload capture for interop outputs

    • Capture live CTX-backed payload fixtures for:
      • assemble_comptox_evidence_pack
      • build_aop_linkage_summary
      • build_pbpk_context_bundle
    • Store them separately from deterministic stub fixtures so live normalization drift can be reviewed intentionally.
    • Add a maintenance path to refresh these fixtures only when upstream CTX changes are accepted deliberately.

  2. Contract manifest resource

    • Publish a small, read-only public resource that inventories:
      • portable object schemas under schemas/
      • MCP response schemas under docs/contracts/schemas/
      • the current live public resources/tools exposed by the default server
    • Keep it machine-readable first; documentation links are a secondary concern.
    • The manifest should help downstream MCPs and orchestrators discover the current contract surface without scraping multiple docs files.

  3. Targeted workflow-contract expansion only where the public surface is already stable

    • Add dedicated workflow contracts only for stable, high-value public surfaces that materially help downstream consumers.
    • Do not expand schema coverage merely to make the tree look more complete.
    • Avoid reopening predictive/orchestrator publication work in this release.

Explicit Non-Goals

v0.2.1 should not:

  • change the suite boundary established in v0.2.0
  • publish predictive or orchestrator tools as part of the default public surface
  • duplicate aop-mcp OECD semantic objects
  • duplicate pbpk-mcp execution, qualification, uncertainty, or internal-exposure objects
  • introduce BER logic or final-decision ownership into CompTox MCP

Suggested PR Order

PR 1: Interop golden payload capture

  • Add live CTX-backed fixture capture for the three interop tools.
  • Add validation helpers so fixture refresh is explicit and reviewable.
  • Keep deterministic stub-based tests in place; this is additive hardening, not a replacement.

PR 2: Contract manifest resource

  • Add a read-only public manifest resource that inventories:
    • server discovery metadata
    • portable schemas
    • MCP response schemas
    • interop/public contract references
  • Add tests that the manifest stays aligned with live tools/list and resources/list.

PR 3: Narrow workflow-contract follow-up

  • Expand workflow contracts only where there is a stable public surface and a real downstream need.
  • Re-run live interop smoke plus the new manifest/golden-fixture checks before release.

Definition Of Done

v0.2.1 is done when:

  • interop outputs are covered by both deterministic tests and CTX-backed golden payloads
  • downstream consumers can discover the public contract surface from one machine-readable manifest resource
  • no new boundary ambiguity is introduced around predictive/orchestrator assets
  • the repo remains in a stabilization posture rather than drifting back into architectural churn