This cleanup pass does not treat shared backbone code as if it had already moved into KES.

What KES Residue Still Remains In svc-tenders

Shared Backbone Code

• kesOutboxRelay.ts
• kesDomainEventConsumer.ts
• kesEventConsumer.ts
• kesDlqReplay.ts
• kesOutboxPoisonReplay.ts
• idempotencyStore.ts

These remain shared backbone or shared operational infrastructure, not dead KES host residue.

Shared Shell / Ingress Glue

• auth ingress and /auth/me contract behavior remain shared through the gateway and service shells
• KYC/signature semantics remain shared and are not represented as dead residue just because the old KES HTTP host is gone

What Was Removed In Sprint 98

• the former validation.ts path Notes: after retirement of the old svc-tenders KES HTTP host, this file was no longer imported by any live TypeScript path.

• stale ownership wording in:

  • the former contracts.ts path
  • the former repository.ts path
  • repository.ts

What Stayed And Why

• shared Kafka/backbone files stayed because they still truthfully serve shared event/backbone responsibilities and are not part of the retired HTTP host slice.

Root Repository Truth

The KES-related compatibility portion of repository.ts has now been removed:

• there are no remaining live TypeScript callers of KES methods through TendersRepository
• TendersRepository no longer instantiates or delegates to a KES repository
• services/svc-tenders/src/kes/* no longer remains as a compatibility package

What still remains in svc-tenders is shared backbone/runtime only, not KES compatibility delegation.

What Was Removed In Sprint 99

• KES compatibility delegation methods from repository.ts
• the old compatibility type surface at the former services/svc-tenders/src/kes/contracts.ts path
• the old compatibility persistence copy at the former services/svc-tenders/src/kes/repository.ts path
• the dead TendersRepository construction from server.ts

Notes

• residue cleanup is not the same thing as full backbone transfer
• post-retirement KES cleanup should keep separating:
  • shared backbone code in svc-tenders
  • canonical KES runtime ownership in svc-kes