---
id: TST-PFM-SEC-244
title: Staff workspace shortcuts.queries 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/tenants/tests/integration/services/persistence/staff-tenant-shortcuts.queries.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/tenants/tests/integration/services/persistence/staff-tenant-shortcuts.queries.integration.spec.js#staff
      tenant shortcuts queries: the two lists of the HQ home page
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/staff-tenant-shortcuts.queries.integration.spec.js#answers
      both lists and nothing else
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/staff-tenant-shortcuts.queries.integration.spec.js#answers
      every element of a shortcut, and only those elements
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/staff-tenant-shortcuts.queries.integration.spec.js#answers
      the tenant as the tenants API answers it, field for field
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/staff-tenant-shortcuts.queries.integration.spec.js#joins
      the name of the customer that owns the tenant
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/staff-tenant-shortcuts.queries.integration.spec.js#answers
      a shortcut that was only opened with no pinned instant
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/staff-tenant-shortcuts.queries.integration.spec.js#answers
      a shortcut that was only pinned with no opened instant
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/staff-tenant-shortcuts.queries.integration.spec.js#answers
      both instants and the count for a shortcut that was pinned and opened twice
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/staff-tenant-shortcuts.queries.integration.spec.js#answers
      every instant in the wire form, milliseconds and a Z
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/staff-tenant-shortcuts.queries.integration.spec.js#puts
      a tenant that was pinned and opened in both lists, as the person did both things to it
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/staff-tenant-shortcuts.queries.integration.spec.js#orders
      the pinned list by the instant each was pinned, newest first
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/staff-tenant-shortcuts.queries.integration.spec.js#orders
      the recent list by the instant each was last opened, newest first
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/staff-tenant-shortcuts.queries.integration.spec.js#leaves
      a tenant that was only pinned out of the recent list
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/staff-tenant-shortcuts.queries.integration.spec.js#leaves
      a tenant that was only opened out of the pinned list
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/staff-tenant-shortcuts.queries.integration.spec.js#answers
      a staff member who has no shortcuts two empty lists
dependency_evidence: >-
  The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here.
  The suite controls the clock at the declared seams; those collaborators remain outside its live
  proof.
evidence:
  - >-
    services-platform:modules/tenants/tests/integration/services/persistence/staff-tenant-shortcuts.queries.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/tenants/tests/integration/services/persistence/staff-tenant-shortcuts.queries.integration.spec.js
  explicit_no_doubles: false
  identified_double_boundaries:
    - the clock
---
# Staff workspace shortcuts.queries 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 staff workspace shortcuts.queries.

## 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 suite controls the clock at the declared seams; those collaborators remain outside its live proof.

## 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.