HSLG Media

m56-sqlite-outbox.test.cjs

m56-sqlite-outbox.test.cjs

Source file: tests/contracts/m56-sqlite-outbox.test.cjs

Module: tests-contracts

Size: 64 lines

SHA-256: 75fc405532b7173303aff7dc9445b4dd622598bcc66344ff4d8809f3ac4c4014

Responsibility

Checks service and UI contract invariants.

Declared entry points

  • assert — source line 2.
  • test — source line 3.
  • path — source line 5.
  • src — source line 6.
  • driver — source line 8.
  • rows — source line 9.
  • row — source line 19.
  • row — source line 21.
  • basket — source line 28.
  • key — source line 35.
  • key — source line 42.
  • probes — source line 43.
  • timeout — source line 44.
  • recovered — source line 47.
  • ready — source line 48.
  • key — source line 54.
  • ready — source line 55.
  • key — source line 61.

Imports and dependencies

  • Line 2: const assert=require('node:assert/strict');
  • Line 3: const test=require('node:test');
  • Line 4: const {pathToFileURL}=require('node:url');
  • Line 5: const path=require('node:path');

Behaviour and audit locations

  • Line 17: rows.set(key,{idempotency_key:key,venue_id:venue,table_number:table,lines_json:json,state,server_order_id:null});
  • Line 52: test('M6 confirmed not-found may safely POST the exact same idempotency key',async()=>{
  • Line 56: assert.equal(submitted.idempotency_key,key);assert.equal(ready.state,'draft_saved');

Relationship to the system

This page is the file-level source reference, not the architecture rationale. Read the module explanation, the corresponding architecture decision and user guide before changing behaviour. Names and line locations above are extracted from this exact source version; they are reference points, not proof that an external service or a phone feature works.

Change verification

Review the entry points and errors in this file, then run the module’s associated tests, source dependency gate, history gate and documentation coverage check. If the file changes an API response, user interaction, data model, deployment or third-party dependency, revise those human explanations and disaster recovery/licensing when relevant. Do not infer actual native or external API operation from source presence.