---
id: TST-PFM-INT-001
title: sql
kind: integration
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/tests/integration/sql.integration.spec.ts
implements: []
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: >-
  Use the suite-owned database fixtures and its declared cleanup; prepare the test database before
  integration or lifecycle execution.
evidence:
  - 'macroservice-libraries:packages/extensions/src/tests/integration/sql.integration.spec.ts'
test_cases:
  - source: >-
      macroservice-libraries:packages/extensions/src/tests/integration/sql.integration.spec.ts#answers
      the tenant’s enabled and shadow bindings of the point, with their handlers, as the application role
    provenance: test
  - source: >-
      macroservice-libraries:packages/extensions/src/tests/integration/sql.integration.spec.ts#reads in
      the caller’s transaction when there is one
    provenance: test
  - source: >-
      macroservice-libraries:packages/extensions/src/tests/integration/sql.integration.spec.ts#answers
      another tenant only its own rows
    provenance: test
  - source: >-
      macroservice-libraries:packages/extensions/src/tests/integration/sql.integration.spec.ts#answers
      nothing for a retired point
    provenance: test
  - source: >-
      macroservice-libraries:packages/extensions/src/tests/integration/sql.integration.spec.ts#relies on
      the policy too: as the application role with no tenant in the session, no binding is visible
    provenance: test
  - source: >-
      macroservice-libraries:packages/extensions/src/tests/integration/sql.integration.spec.ts#inserts
      the row with the execution id as its id
    provenance: test
  - source: >-
      macroservice-libraries:packages/extensions/src/tests/integration/sql.integration.spec.ts#updates
      the operational columns
    provenance: test
  - source: >-
      macroservice-libraries:packages/extensions/src/tests/integration/sql.integration.spec.ts#refuses to
      update a row the tenant cannot see
    provenance: test
  - source: >-
      macroservice-libraries:packages/extensions/src/tests/integration/sql.integration.spec.ts#installs
      the table with its forced policy and the claim index, and installs again without harm
    provenance: test
  - source: >-
      macroservice-libraries:packages/extensions/src/tests/integration/sql.integration.spec.ts#refuses a
      schema name that is not one
    provenance: test
  - source: >-
      macroservice-libraries:packages/extensions/src/tests/integration/sql.integration.spec.ts#act writes
      the pending invocation and the queue row in the caller’s transaction
    provenance: test
  - source: >-
      macroservice-libraries:packages/extensions/src/tests/integration/sql.integration.spec.ts#a rollback
      takes both rows back
    provenance: test
  - source: >-
      macroservice-libraries:packages/extensions/src/tests/integration/sql.integration.spec.ts#another
      tenant sees none of the queue
    provenance: test
  - source: >-
      macroservice-libraries:packages/extensions/src/tests/integration/sql.integration.spec.ts#resolve
      over the SQL source and recorder answers the winning handler and leaves its row
    provenance: test
dependency_evidence:
  provenance: test
  source: 'macroservice-libraries:packages/extensions/src/tests/integration/sql.integration.spec.ts'
  reviewed:
    - Suite introduction
    - Fixture setup
    - Client substitutions
    - Assertions and cleanup
---
# sql

## Verification Boundary

This database and service suite exercises sql. Its registration records the executable definition; no run result is asserted.

## What This Suite Proves

The suite contains executable checks, but no detailed scenario binding is verified in this pass.

## What It Does Not Prove

In-process execution does not establish deployed infrastructure or a real provider response. Several bindings can supply different parts of a detailed scenario; no single-file completeness is implied.

## Real Dependencies and Test Doubles

The suite definition identifies its database fixtures and replaced clients, hooks, clocks or executors. Integration runs use the prepared database; lifecycle runs exercise the in-process route or adapter path.

## Must Not Be Doubled

The database constraints, transactions and service behavior claimed by an integration binding must execute. Replaced external seams cannot establish live provider or infrastructure behavior.