Skip to content

v0.3.0-downstream-validation-path.md

Latest commit

 

History

History
97 lines (69 loc) · 4.37 KB

v0.3.0-downstream-validation-path.md

File metadata and controls

97 lines (69 loc) · 4.37 KB
Raw

Traverse v0.3.0 Downstream Validation Path

This page defines the deterministic Traverse-side validation path that youaskm3 can cite for its first release against Traverse v0.3.0.

It exists to answer one release question:

Can a downstream app pin Traverse v0.3.0 and validate the documented MCP and HTTP/JSON app surfaces without relying on private Traverse internals?

Supported Baseline

  • Traverse release: v0.3.0
  • Consumer: youaskm3
  • Packaging model: source-build consumption
  • MCP surface: cargo run -p traverse-mcp -- stdio
  • HTTP/JSON app surface: cargo run -p traverse-cli -- serve

This validation path complements docs/v0.3.0-public-surface-compatibility.md and docs/v0.3.0-source-build-consumer-packaging.md.

Clean Checkout Commands

Run this sequence from a clean Traverse checkout pinned to the released tag:

git clone https://github.com/enricopiovesan/Traverse.git
cd Traverse
git checkout v0.3.0
cargo build
bash scripts/ci/mcp_consumption_validation.sh
bash scripts/ci/app_consumable_acceptance.sh
bash scripts/ci/youaskm3_compatibility_conformance.sh
bash scripts/ci/repository_checks.sh

The sequence intentionally includes both release-facing surfaces:

  • MCP-facing validation through scripts/ci/mcp_consumption_validation.sh
  • app-facing HTTP/JSON validation through scripts/ci/app_consumable_acceptance.sh
  • compatibility aggregation through scripts/ci/youaskm3_compatibility_conformance.sh
  • discoverability and documentation guardrails through scripts/ci/repository_checks.sh

Expected Success Evidence

The successful validation run should prove:

  • the Traverse workspace builds from the pinned v0.3.0 source checkout
  • the downstream MCP path exposes the public Traverse MCP consumption surface
  • the MCP evidence includes consumer_name: youaskm3
  • the MCP evidence includes validated_flow_id: youaskm3_mcp_validation
  • the app-consumable path can exercise the public HTTP/JSON browser adapter and app acceptance flow
  • the compatibility wrapper can run the downstream Traverse-side conformance checks together
  • repository checks confirm that the validation path remains documented and discoverable

The validation output is command-line evidence. No private youaskm3 repository checkout is required for this Traverse-side proof.

Expected Failure Evidence

The path should fail deterministically when:

  • Rust or Cargo is unavailable
  • the checkout is not pinned to a compatible Traverse release
  • the public MCP server path cannot be discovered or exercised
  • the app-consumable acceptance path cannot start or validate the local HTTP/JSON surface
  • a local port needed by an app smoke check is already occupied
  • required validation docs or scripts are missing from the repository

When a failure occurs, keep the failing command output with the release evidence. The failing command name is part of the triage signal.

Claims This Supports

This validation supports these first-release claims:

  • youaskm3 can pin Traverse v0.3.0.
  • youaskm3 can cite a source-build Traverse consumer path.
  • youaskm3 can rely on the documented MCP stdio path for first-release integration work.
  • youaskm3 can rely on the documented HTTP/JSON app path for first-release integration work.
  • The Traverse-side evidence uses public docs and scripts, not private internals.

Claims Still Owned By youaskm3

This validation does not prove:

  • the youaskm3 product UI is complete
  • every youaskm3 application feature works
  • every possible external MCP client is compatible
  • production hosting, native installers, or package-manager distribution
  • private downstream release gates inside the youaskm3 repository

youaskm3 still owns its product release validation. Traverse owns this public runtime and integration-surface validation path.

Related Docs