What Stayed Shared

Still shared on purpose:

• API gateway Vacancy route family
• VACANCIES_SERVICE_URL ?? TENDERS_SERVICE_URL
• shared auth ingress behavior
• shared auth/identity resolution behind /auth/me
• root startup orchestration that now launches svc-vacancies normally

What Compatibility Residue Still Remains

Still intentionally present in svc-tenders:

• services/svc-tenders/src/vacancy/contracts.ts
• services/svc-tenders/src/vacancy/domain.ts
• services/svc-tenders/src/vacancy/readModel.ts
• services/svc-tenders/src/vacancy/readRepository.ts
• services/svc-tenders/src/vacancy/compatibilityReadRepository.ts
• services/svc-tenders/src/vacancy/compatibilityApplicationRepository.ts
• root Vacancy compatibility methods in services/svc-tenders/src/repository.ts

Why they remain:

• older callers and compatibility cleanup still depend on them
• they no longer represent an active Vacancy route host

Compatibility-Truth Notes

Public Vacancy read behavior still remains mixed:

• GET /vacancies
• GET /vacancies/:id

That compatibility-backed truth remains explicit in the extracted runtime and in the smaller svc-tenders compatibility residue.

Host retirement does not equal public-read cleanup.

Notes

• the rollback cutoff condition is now satisfied
• the old svc-tenders Vacancy route host is retired
• some older JS residue still exists in services/svc-tenders/src/; that is outside the active TS runtime and was not expanded into a broader cleanup sprint