API Tender Legacy Bridge Modularization Status

Date: 2026-03-19 Sprint: Platform Cleanup Sprint 105

What Bridge Logic Was Moved

The gateway-side tender legacy bridge logic was moved out of:

• legacyRoutes.ts

and into:

• legacyBridge.ts

Moved bridge logic now includes:

• enqueueLegacyTenderBridgeEvent(...)
• LEGACY_TENDERS_OUTBOX_ENABLED
• LEGACY_TENDERS_OUTBOX_PATH
• bridge event type definition
• intentId derivation
• dedupeKey derivation
• bridge-specific request body parsing for intentId
• POST to TENDERS_SERVICE_URL + LEGACY_TENDERS_OUTBOX_PATH
• bridge failure mapping contract via legacy_outbox_enqueue_failed

Where It Lives Now

Dedicated bridge module:

• services/api/src/tenders/legacyBridge.ts

That file now owns the gateway-side compatibility bridge boundary.

What Still Remains In Route-Shell Code

Route-shell behavior remains in:

• services/api/src/tenders/legacyRoutes.ts

It still owns:

• /api/v1/tenders/legacy/* route mounting
• feature-flag gating through ensureLegacyTenderLocalEngineEnabled(...)
• gateway-local viewer resolution
• request input parsing for route actions
• local-engine action execution through engine.ts
• route-level success/error response shaping

Dependency Notes

Who calls the bridge helper now

• only legacyRoutes.ts

What the bridge depends on

• Request metadata for x-intent-id / request body inspection
• TENDERS_SERVICE_URL
• LEGACY_TENDERS_OUTBOX_PATH
• LEGACY_TENDERS_OUTBOX_ENABLED
• fetch

What remains local to services/api

• the route shell
• the bridge module
• the API-local legacy tender engine

What still blocks removal planning later

• the bridge is still operationally real because it appends to the documented legacy tender outbox flow
• no canonical upstream replacement for these legacy actions has been established here yet

What Later Cleanup This Enables

This modularization enables a cleaner next step:

• evaluate route-shell removal planning separately from bridge retirement planning
• reason about bridge dependencies without rereading route-handler logic
• isolate or retire the bridge later without treating the whole route file as one mixed ownership blob

Notes

• Behavior was intentionally kept unchanged.
• This is a modularization step, not a removal step.