ICPI Root Compatibility Layer Status

Current Root Compatibility Hosting

The root repository.ts still contains ICPI runtime delegation methods on TendersRepository:

• upsertIcpiPricePoints(...)
• countIcpiPricePoints(...)
• listIcpiPricePoints(...)
• suggestIcpiItems(...)
• findLatestIcpiPricePoint(...)

These methods still forward to the dedicated ICPI child repository and therefore remain a temporary runtime compatibility layer.

What Was Removed In Sprint 46

The root repository no longer re-exports ICPI contract types from src/icpi/contracts. That means root hosting has been narrowed from:

• compatibility type host
• compatibility runtime delegation

to:

• compatibility runtime delegation only

What Remains And Why

• Delegation methods remain because TendersRepository still truthfully hosts multiple legacy domain slices in one runtime
• They were not removed in this sprint because Sprint 46 was about safe dependency reduction, not about forcing a monolith-wide import migration

Extraction Meaning

This is a better extraction posture than Sprint 45 because the root repository no longer presents itself as the authoritative home of ICPI types. The remaining root edge is operational compatibility only.

Remaining Root Blockers

• ICPI methods still exist on TendersRepository
• monolith runtime construction still instantiates TendersRepository alongside the dedicated IcpiRepository
• any future caller still using root ICPI delegation will need to be removed before final extraction