---
id: TST-PFM-INT-625
title: Published contract package contents
kind: unit
product_area: platform
module: integrations
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: macroservice-libraries
files:
  - packages/integration-contracts/src/package.spec.ts
implements: []
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: 'The test process owns its inputs, fake clocks and any replaced runtime ports.'
test_cases:
  - provenance: test
    source: >-
      macroservice-libraries:packages/integration-contracts/src/package.spec.ts#depends on no
      @rhythmsoftware package but macroservice-money
  - provenance: test
    source: >-
      macroservice-libraries:packages/integration-contracts/src/package.spec.ts#depends on ajv,
      ajv-formats and money at run time, json-schema-to-typescript to build, and nothing else
  - provenance: test
    source: >-
      macroservice-libraries:packages/integration-contracts/src/package.spec.ts#has generated types and
      schemas in sync with schemas/ (the generation script, in check mode, finds no difference)
evidence:
  - 'macroservice-libraries:packages/integration-contracts/src/package.spec.ts'
---
# Published contract package contents

## Verification Boundary

This unit suite exercises published contract package contents within the shared package. It records engineering coverage at the pinned revision without claiming a deployed run.

## What This Suite Proves

The source assertions cover the package behavior under controlled inputs. No detailed capability or feature scenario binding is verified in this registration.

## What It Does Not Prove

The suite does not establish deployed authorization, database behavior, provider effects or a complete customer workflow.

## Real Dependencies and Test Doubles

Imported package functions execute against the source-defined fixtures. Runtime ports, clocks and external transport responses remain controlled wherever the suite replaces them.

## Must Not Be Doubled

The shared function under test and its result assertions must execute. Returning an expected answer from a substitute does not prove the package behavior.