The live Vacancy cutover changed one API gateway seam only:

• file: services/api/.env
• before: VACANCIES_SERVICE_URL=http://localhost:4020
• after: VACANCIES_SERVICE_URL=http://localhost:4023

No gateway route paths changed. No auth middleware changed. No old Vacancy hosting was removed.

Canonical extracted Vacancy runtime target:

• http://localhost:4023

Legacy fallback Vacancy host kept available during the window:

• http://localhost:4020

Cutover Start Steps

1. Verified svc-auth was available on http://localhost:4100
2. Verified legacy svc-tenders Vacancy hosting was available on http://localhost:4020
3. Verified extracted svc-vacancies was available on http://localhost:4023
4. Verified the live API gateway on http://localhost:4001 worked in fallback mode
5. Updated services/api/.env to set VACANCIES_SERVICE_URL=http://localhost:4023
6. Restarted only the API gateway on http://localhost:4001

Smoke Checks Run

Pre-cutover fallback baseline:

• GET /api/v1/vacancies?page=1&pageSize=5
• GET /api/v1/vacancies/VAC-GE-2026-00001
• GET /api/v1/vacancies/11e35ec4-4818-4741-868b-bb3c64cdd9f2
• GET /api/v1/owner/vacancy-postings
• GET /api/v1/vacancy-applications/me
• POST /api/v1/vacancy-postings without bearer token

Post-cutover live checks:

• GET /api/v1/vacancies?page=1&pageSize=5
• GET /api/v1/vacancies/VAC-GE-2026-00001
• GET /api/v1/vacancies/11e35ec4-4818-4741-868b-bb3c64cdd9f2
• GET /api/v1/owner/vacancy-postings
• GET /api/v1/owner/vacancy-postings/11e35ec4-4818-4741-868b-bb3c64cdd9f2
• GET /api/v1/vacancy-applications/me
• GET /api/v1/owner/vacancy-applications
• GET /api/v1/vacancy-postings/11e35ec4-4818-4741-868b-bb3c64cdd9f2/applications
• POST /api/v1/vacancy-postings without bearer token

Observations

• the live gateway matched extracted svc-vacancies on the checked route set
• status codes matched expected parity
• auth behavior matched expected parity
• owner/internal and applicant read routes behaved as before
• the legacy Vacancy host remained healthy as rollback target during the window

Important compatibility note:

• this cutover confirms extracted-runtime parity for the current Vacancy behavior
• it does not claim that GET /vacancies or GET /vacancies/:id are already projection-only truth
• those public routes remain compatibility-backed where current runtime logic still falls back to legacy vacancies

Whether The Cutover Stayed In Place

Yes.

The cutover remained in place after the live checks.

Current live Vacancy routing intent after this sprint:

• API gateway Vacancy traffic targets http://localhost:4023
• legacy svc-tenders Vacancy hosting on http://localhost:4020 remains available only as fallback during this phase

Rollback Notes

Rollback was not needed in this window.

Rollback remains simple:

1. change services/api/.env
2. set VACANCIES_SERVICE_URL=http://localhost:4020
3. restart only services/api
4. re-run Vacancy smoke checks