Preservation regression run

The suites that existed before feature 054-desktop-runtime-shell, run unmodified.

T114. Design §2: desktop must not change what already worked. Mobile, Print Bridge, the printing packages, the backend and the PWA all keep their behaviour, and this is the record that they do — not an assertion that they should.

Run of 2026-09-06

Suite	Files	Tests	Result
packages/print-orchestrator	1	10	pass
packages/printer-transport	3	50	pass
packages/receipt-escpos	6	46	pass
packages/receipt-layout	9	157	pass
apps/mobile	42	423	pass
apps/print-bridge	18	187	pass
apps/backend	461	4,243 (+2 skipped)	pass
apps/frontend-pwa	564	3,164	pass
Total	1,104	8,280	pass

No suite was modified for this feature. No test was skipped, disabled or relaxed to make it pass.

The two skipped backend tests

Tests: 2 skipped is reported by the backend suite and is pre-existing and unrelated to this feature:

• communications/application/adapters/__tests__/email-adapter.service.spec.ts:68
• communications/application/__tests__/communications.service.comprehensive.spec.ts:713

Both are unit tests skipped for a mocking limitation, documented in place. Neither is an integration test skipping because a precondition was missing, which is the failure CLAUDE.md forbids — that rule exists because a skipped integration test reports its cases as passing while none of them ran. These two report as skipped, visibly, and count separately.

Recorded here rather than left in the output, because "2 skipped" in a preservation run is exactly the kind of line that gets read as noise once and never looked at again.

What this run does not cover

• The desktop suites themselves. They are new, not preserved; they run in .github/workflows/desktop.yml on both platforms.
• Anything needing real hardware or certificates. The clean-machine install verification (SC-022) is a separate, currently unmet criterion — see install-verification.md.
• The mobile app on a device. These are the unit and integration suites, not a device run.

Re-running it

pnpm --filter @flowpos-workspace/print-orchestrator test
pnpm --filter @flowpos-workspace/printer-transport test
pnpm --filter @flowpos-workspace/receipt-escpos test
pnpm --filter @flowpos-workspace/receipt-layout test
pnpm --filter @flowpos-workspace/mobile test
pnpm --filter @flowpos-workspace/print-bridge test
pnpm --filter @flowpos-workspace/backend test
pnpm --filter @flowpos-workspace/frontend-pwa test

The backend suite needs a database. It fails rather than skips when one is missing — requireTestDatabase() — so a green backend run means the assertions actually executed.