[MOCK-01] Replace stale scaffold with contract-driven HTTP mock baseline

[jaavid]

Background

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

Problem

The repository does not yet provide a supported, reproducible and acceptance-tested way to replace stale scaffold with contract-driven HTTP mock baseline.

Goal

Replace stale scaffold with contract-driven HTTP mock baseline, aligned with tagged contracts and the shared CoreLink release train.

Parent

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

Scope

• Deliver the title outcome inside mock-server.
• Reconcile contract version, authentication, tenancy, error, compatibility, packaging and documentation behavior where applicable.
• Retain evidence for the Developer Platform gate.

Out of Scope

• Hand-written divergence from the normative contracts.
• Unsupported production claims before an artifact and conformance evidence exist.
• A separate repository roadmap.

Acceptance Criteria

• The outcome is reproducible from documented inputs and tagged dependencies.
• Expected, error, retry/recovery and compatibility behavior is verified.
• Authentication, tenant context and sensitive-data handling are safe where applicable.
• Installable artifacts or explicit scaffold status are documented accurately.
• Examples and documentation are versioned and runnable.
• Conformance evidence is linked to the parent Epic.

Technical Notes

Generated artifacts must identify immutable contract provenance. Security-sensitive tools use least privilege, explicit consent, audit and safe token handling. Package channels must distinguish prerelease from stable.

Dependencies

• Prerequisite completed: API-01 established the contract lifecycle baseline.
• Active blocker: API-05 must provide the parity/conformance gate and tagged-contract release path used by the mock baseline.
• Blocks: contract-driven HTTP mock readiness, runnable developer scenarios, and EPIC-05 sandbox/mock acceptance.
• Cross-repository: Link concrete contract, mock, documentation and release Issues; do not duplicate implementation.
• Current dependency state: See the CoreLink Product organization Project.

Planning Metadata

• Type: Technical Task
• Priority: P0
• Product milestone: Developer Platform
• Domains: devex, api
• Area: backend
• 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.
• Tests/conformance and required evidence pass.
• Contracts are updated or confirmed unaffected.
• Security and tenancy boundaries are reviewed.
• Packaging, provenance and rollback are verified.
• Documentation and release notes are updated.
• Pull request(s) are merged and linked.