VACANCY PARITY VERIFICATION

This sprint verified parity between:

• legacy Vacancy hosting in svc-tenders on http://localhost:4120
• extracted svc-vacancies on http://localhost:4023
• API gateway fallback mode on http://localhost:4002 without VACANCIES_SERVICE_URL
• API gateway cutover mode on http://localhost:4002 with VACANCIES_SERVICE_URL=http://localhost:4023

Canonical Vacancy runtime target for extraction cutover remains:

• http://localhost:4023

Temporary isolated rehearsal ports used in this sprint:

• auth: http://localhost:4101
• old Vacancy host: http://localhost:4120
• API rehearsal: http://localhost:4002

Authenticated fixture used:

• POST /api/v1/auth/dev/impersonate
• email: kvaratskhelia.ge@gmail.com
• result: stable bearer token suitable for authenticated Vacancy read-path checks

Sample IDs used:

• compatibility-backed public Vacancy detail: VAC-GE-2026-00001
• projection-backed Vacancy detail / owner posting: 11e35ec4-4818-4741-868b-bb3c64cdd9f2

Routes Checked

Direct old-host vs new-host parity:

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

Gateway fallback parity:

• 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

Gateway cutover parity:

• 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

Rollback verification:

• 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

Results

Direct old-host vs new-host parity verdict:

• parity confirmed

Gateway fallback verdict:

• parity confirmed against legacy svc-tenders Vacancy hosting

Gateway cutover verdict:

• parity confirmed against extracted svc-vacancies

Rollback verdict:

• parity confirmed after removing the Vacancy-specific service target override

Observed status parity:

• public list: 200
• public detail by compatibility-backed ID: 200
• public detail by projection-backed ID: 200
• owner posting list: 200
• owner posting detail: 200
• my applications: 200
• owner applications: 200
• posting applications: 200
• unauthenticated posting create denial: 401

Interpretation

Public read parity is confirmed including compatibility-backed public read behavior.

This is intentionally not a claim that public Vacancy discovery is already projection-only or fully cleaned up. It confirms that:

• the extracted runtime preserved the current mixed public-read truth
• the gateway preserved that behavior in both fallback and cutover modes

Authenticated happy-path coverage in this sprint:

• confirmed for owner/internal and applicant read paths using a stable impersonated bearer token

Authenticated mutation happy-path coverage in this sprint:

• not exercised

That leaves a small residual confidence gap for successful write parity, but not a gateway or auth-shape mismatch.

Mismatches

No parity drift was found in the checked route set.

No mismatch was classified as:

• real drift
• compatibility-backed difference
• env/config issue
• auth issue

Current public-read compatibility residue remains intentional and unchanged:

• GET /vacancies
• GET /vacancies/:id

That residue affects architectural cleanliness, not the parity result for this sprint.