Bootstrap / Server Entry

Primary runtime bootstrap files:

• services/svc-vacancies/package.json
• services/svc-vacancies/tsconfig.json
• services/svc-vacancies/src/server.ts
• services/svc-vacancies/src/config.ts
• services/svc-vacancies/src/db.ts
• services/svc-vacancies/src/auth.ts
• services/svc-vacancies/src/http/authTypes.ts

The runtime follows the same extracted-service pattern already used by:

• services/svc-icpi
• services/svc-accommodations

Canonical intended dev runtime port:

• http://localhost:4023

Copied Vacancy Files

Copied into svc-vacancies:

• src/routes/registerVacancyRoutes.ts
• src/routes/support/vacancyRouteSupport.ts
• src/routes/support/detailExtractionSupport.ts
• src/vacancy/contracts.ts
• src/vacancy/validation.ts
• src/vacancy/domain.ts
• src/vacancy/commandHandlers.ts
• src/vacancy/projections.ts
• src/vacancy/readModel.ts
• src/vacancy/readRepository.ts

These are the move-first vacancy-owned runtime files.

What Remains Shared

Still shared on purpose:

• Vacancy gateway route family in services/api
• VACANCIES_SERVICE_URL ?? TENDERS_SERVICE_URL
• shared bearer-token auth ingress behavior
• shared auth/identity principal resolution behind /auth/me

What Stayed Old-Host-Only

Still only in svc-tenders:

• services/svc-tenders/src/vacancy/compatibilityReadRepository.ts
• services/svc-tenders/src/vacancy/compatibilityApplicationRepository.ts
• vacancy compatibility methods on services/svc-tenders/src/repository.ts
• vacancy shell composition in services/svc-tenders/src/server.ts
• current vacancy migration ownership and mixed migration residue in services/svc-tenders/migrations

Coexistence / Rollback Notes

This sprint did not remove old vacancy hosting.

Current coexistence truth:

• svc-vacancies now exists as a real extracted runtime bootstrap
• old vacancy hosting in svc-tenders still remains for rollback and parity
• gateway behavior is unchanged
• auth behavior is unchanged

Opt-in dev helpers added:

• npm run dev:vacancies
• npm run dev:api:vacancies-extracted

Root port cleanup now also knows about:

• 4023

Public-Read Compatibility Notes

Public vacancy compatibility residue remains explicit in the copied runtime:

• GET /vacancies
• GET /vacancies/:id

still use the copied VacancyReadRepository, which still:

• prefers vacancy projection-backed reads first
• falls back to legacy vacancies when needed

This sprint did not attempt to pretend public vacancy discovery is already fully converged.