Implement provider-side contract schema validation in rerum_server_nodejs so CI verifies runtime behavior against seam baselines in cubap/rerum_openapi.
Context
Provider Implementation Plan
- Add a provider CI workflow in this repo that calls:
uses: cubap/rerum_openapi/.github/workflows/seam-runtime-validation.yml@main
- Pin inputs for this provider:
- contract_repo_ref: main (or pinned tag/commit)
- seam_manifest_path: seams/tinynode-to-rerum/manifest.yaml (and/or deer-to-rerum, tpen-services-to-rerum, etc. as phased jobs)
- target_base_url: deployed provider URL for CI environment
- compare_paths: true
- compare_operations: true
- Add a provider fixture file in this repo for representative interactions and pass it with fixture_file.
- Run this gate on pull_request and push to main; block merge on failure.
Suggested Acceptance Criteria
- CI fails if provider health/readiness/spec endpoints fail for the seam test endpoints.
- CI fails if provider OpenAPI misses expected paths, operations, or response codes from seam baseline.
- CI fails if provider fixture request/response bodies violate baseline schemas.
- CI passes with deterministic fixture data and stable environment config.
Notes
- This adds local deterministic contract gates without introducing a hosted validation service dependency.
- Follow-up optimization can pin contract_repo_ref to release tags instead of main.
Implement provider-side contract schema validation in rerum_server_nodejs so CI verifies runtime behavior against seam baselines in cubap/rerum_openapi.
Context
https://github.com/cubap/rerum_openapi/blob/main/.github/workflows/seam-runtime-validation.yml
Provider Implementation Plan
uses: cubap/rerum_openapi/.github/workflows/seam-runtime-validation.yml@main
Suggested Acceptance Criteria
Notes