---
id: TST-PFM-INT-611
title: Extension failure policy
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/extensions/src/failure-policy.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/extensions/src/failure-policy.spec.ts#is the point’s default
      without an override or a policy for the mode
  - provenance: test
    source: >-
      macroservice-libraries:packages/extensions/src/failure-policy.spec.ts#is the point’s policy for the
      mode when it declares one
  - provenance: test
    source: >-
      macroservice-libraries:packages/extensions/src/failure-policy.spec.ts#is the binding’s override
      when the point allows it
  - provenance: test
    source: >-
      macroservice-libraries:packages/extensions/src/failure-policy.spec.ts#ignores an override the point
      does not allow
  - provenance: test
    source: >-
      macroservice-libraries:packages/extensions/src/failure-policy.spec.ts#a ${kind} under ${policy} in
      ${mode} mode: ${expected}
  - provenance: test
    source: >-
      macroservice-libraries:packages/extensions/src/failure-policy.spec.ts#names the point and the
      handler in the problem, with the class and code, never a payload
  - provenance: test
    source: >-
      macroservice-libraries:packages/extensions/src/failure-policy.spec.ts#answers a resolver refusal
      with the same problem
evidence:
  - 'macroservice-libraries:packages/extensions/src/failure-policy.spec.ts'
---
# Extension failure policy

## Verification Boundary

This unit suite exercises extension failure policy 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.