From 064fba5c0cb8ec756e24c28d870379ef47f34d82 Mon Sep 17 00:00:00 2001 From: Maurice Date: Sat, 10 Oct 2026 14:32:15 +0200 Subject: [PATCH] test(server): the provider-orchestrator boundary case gets an id of its own Both boundary rules arrived as BOUND-012; the provider rule's case is now BOUND-014. --- server/tests/unit/scripts/import-boundaries.test.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/server/tests/unit/scripts/import-boundaries.test.ts b/server/tests/unit/scripts/import-boundaries.test.ts index 4889f16a1..6c0d2890d 100644 --- a/server/tests/unit/scripts/import-boundaries.test.ts +++ b/server/tests/unit/scripts/import-boundaries.test.ts @@ -178,7 +178,7 @@ describe('import-boundaries.mjs', () => { expect(out).toContain('FAIL dbImportsNest: db/orm.ts -> nest/database/request-context.ts'); }); - it('BOUND-012: a provider may not import the orchestrator above it, type-only included', () => { + it('BOUND-014: a provider may not import the orchestrator above it, type-only included', () => { const dir = serverRoot({ 'nest/maps/maps.service.ts': "import { Osm } from './providers/osm.client';\nexport class MapsService { o = Osm; }\n",