--- id: TST-PFM-SEC-247 title: Workspace deletion schedule jobs.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/tenant-deletion-schedule-jobs.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/tenant-deletion-schedule-jobs.queries.integration.spec.js#tenant deletion schedule jobs queries: reading a schedule nothing has become of yet - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#answers every field of the schedule, the job contract’s and this family’s own - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#answers each instant as the one the row holds, and nothing for the instants of a schedule that has not run - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#answers an instant the row holds and never raw PostgreSQL timestamp text - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#answers nothing for a job id nobody made - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#tenant deletion schedule jobs queries: reading a schedule that ended in a failure - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#answers every field of the failed schedule, each from a value of its own - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#answers the settlement’s instants, which are the settlement’s and not the submission’s - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#tenant deletion schedule jobs queries: the request’s most recent schedule - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#answers the schedule that superseded the first and not the first itself - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#maps the later row and not the earlier one, whose submission identity and request instant are another - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#breaks a shared request instant by descending id, so two schedules submitted together have one order - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#answers nothing for a request that was never scheduled - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#tenant deletion schedule jobs queries: every schedule a request ever had - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#answers every schedule the request ever had, settled ones included - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#answers them newest first, with the id as the tie-breaker of two submitted at one instant - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#answers what each schedule came to, which is how many times a resume replaced one - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#answers none of another request’s schedules (the collision control) - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#answers every field of a schedule of the history, mapped exactly as the single read maps it - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#answers nothing for a request that was never scheduled - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#tenant deletion schedule jobs queries: the schedule a submission identity already made - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#answers the schedule of the submission identity it is given - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#answers nothing for a submission identity nobody has used - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#answers none of the schedule another submission identity made (the collision control) - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#tenant deletion schedule jobs queries: every schedule the database believes is running - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#answers the four schedules of the suite that are still running (the premise) - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#answers them newest first, by the instant each schedule was submitted - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#breaks a shared request instant by descending id, so the order is one the rows are in nowhere else - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#answers no schedule that has settled, though the same read listed it while it was pending - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#answers a schedule of every tenant, which is what the orphan report is built on - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.queries.integration.spec.js#answers every field of a running schedule, mapped exactly as the single read maps it dependency_evidence: >- The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here. The suite controls workflow execution at the declared seams; those collaborators remain outside its live proof. evidence: - >- services-platform:modules/tenants/tests/integration/services/persistence/tenant-deletion-schedule-jobs.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/tenant-deletion-schedule-jobs.queries.integration.spec.js explicit_no_doubles: false identified_double_boundaries: - workflow execution --- # Workspace deletion schedule jobs.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 workspace deletion schedule jobs.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 workflow execution 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.