---
id: TST-PFM-SEC-147
title: Catalog releases database and service checks
kind: integration
product_area: platform
module: security
revision: 2
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/security/tests/integration/services/persistence/catalog-releases.integration.spec.js
implements: []
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 3
isolation: Use the prepared test database and suite-owned fixture rows; retain shared seed records.
assertion_evidence:
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/catalog-releases.integration.spec.js#security
      persistence: security_catalog_releases
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/catalog-releases.integration.spec.js#catalogChecksum
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/catalog-releases.integration.spec.js#checksums
      a catalog in a canonical order, so the order it is published in does not matter
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/catalog-releases.integration.spec.js#recordRelease
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/catalog-releases.integration.spec.js#records
      a release it has not seen, with what it changed and the catalog it checksums
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/catalog-releases.integration.spec.js#supersedes
      the release that was current, so exactly one release is current
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/catalog-releases.integration.spec.js#rewrites
      the release stored under the same identifier when the reconciliation changed something
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/catalog-releases.integration.spec.js#writes
      nothing at all on the redeploy of an unchanged catalog, so no version moves
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/catalog-releases.integration.spec.js#records
      an unchanged reconciliation of a release it has not seen, because there is nothing to leave
      alone
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/catalog-releases.integration.spec.js#the
      release reads
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/catalog-releases.integration.spec.js#answers
      the current release, one by its identifier, and the list newest first
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/catalog-releases.integration.spec.js#keeps
      exactly one current release, whatever has been reconciled
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/catalog-releases.integration.spec.js#answers
      no current release, rather than refusing, when none is stored
dependency_evidence: >-
  The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here.
  The file declares no substituted collaborators.
evidence:
  - >-
    services-platform:modules/security/tests/integration/services/persistence/catalog-releases.integration.spec.js
  - >-
    Static review at the recorded source revision; executable results remain not-run and conformance
    remains not-verified.
binding_note: >-
  The file has no scenario binding established by this examination. Its executable checks remain
  registered without assigning them broader acceptance coverage.
examiner: codex
examined_at: '2026-10-23'
final_text: OpenAI
dependency_review:
  provenance: test
  source: >-
    services-platform:modules/security/tests/integration/services/persistence/catalog-releases.integration.spec.js
  explicit_no_doubles: true
  identified_double_boundaries: []
---
# Catalog releases database and service checks

## Verification Boundary

The file exercises database or service behavior through the local integration harness. The assertion references identify the source checks for catalog releases.

## What This Suite Proves

The file supplies executable engineering checks for the named subject. No complete acceptance scenario is inferred from the file’s existence.

## What It Does Not Prove

This examination does not run the suite. Passing behavior, deployed conformance and the behavior of substituted dependencies require separate execution evidence.

## Real Dependencies and Test Doubles

The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here. The file declares no substituted collaborators.

## Must Not Be Doubled

Keep the queried database, applicable constraints and transaction boundaries real. Provider substitutes cannot establish delivery, cloud execution or cross-service recovery.