[MOCK-03] Publish container or package and run SDK conformance in CI

[jaavid]

Background

CoreLink is one product across multiple implementation repositories. This work is owned by mock-server under EPIC-05.

Problem

MOCK-03 previously depended on the vague phrase SDK generators and left downstream outcomes unresolved, which obscured the actual release/conformance gate shared by the SDK, CLI and MCP toolchain.

Goal

Publish a versioned mock artifact and run repeatable cross-language/tool conformance in CI against immutable contract inputs.

Parent

• Primary Product Epic: EPIC-05
• Backlog ID: MOCK-03

Scope

• Package the accepted MOCK-02 scenario set as an installable container/package with immutable provenance.
• Run conformance against the generated TypeScript, Python and Java SDK baselines and supported CLI/MCP consumers as they become available.
• Distinguish prerelease/scaffold compatibility from supported Beta compatibility.
• Retain CI artifacts, dependency versions and exact contract/mock revisions.

Out of Scope

• Treating a green mock CI run as runtime Product Acceptance.
• Stable support claims for SDK/tool surfaces that have not passed their own release gates.
• Hand-written divergence from normative contract/scenario behavior.

Acceptance Criteria

• MOCK-02 scenario coverage used by the artifact is version-identifiable and immutable.
• Container/package can be reproduced from documented inputs and carries contract/scenario provenance.
• TypeScript, Python and Java generated baselines can execute the supported scenario set where their generation gates are available.
• CLI/MCP consumers can use the same accepted sandbox/mock path where their Beta scope requires it.
• Positive, denied, malformed, retry and recovery conformance results are retained.
• Prerelease versus supported compatibility is explicit.
• Evidence is linked and EPIC-05 runtime-contract-SDK/tool conformance criteria are measurably advanced.

Dependencies and acceptance state

• Execution prerequisite: MOCK-02 deterministic scenario set.
• SDK generation inputs: TS-01, PY-01, and JAVA-01 provide the generated SDK baselines; a language does not block initial artifact packaging if clearly classified as unavailable/scaffold, but supported compatibility requires its accepted baseline.
• Blocks: TS-03, PY-03 and JAVA-03 signed release/conformance gates; CLI-02/03; MCP-02/04; DOCS-04 runnable-tool guidance; and EPIC-05 conformance acceptance.
• Current dependency state: See the CoreLink Product organization Project.

Planning Metadata

• Type: Technical Task
• Priority snapshot: P0
• Product milestone snapshot: Beta
• Domain snapshots: devex, deployment
• Area snapshot: infra
• Complexity: M
• Created in status: Triage
• Current status and DRI: See the CoreLink Product organization Project.
• Intended repository labels: type:technical-task

Definition of Done

• Acceptance criteria demonstrated.
• Artifact/package provenance and reproducibility are verified.
• Required conformance checks pass for the supported consumer set.
• Security/tenancy and synthetic-data boundaries are reviewed.
• Packaging, versioning and rollback/deprecation behavior are documented.
• Documentation/maturity claims are reconciled.
• Pull request(s), package/container revisions and retained CI evidence are linked.