Important interpretation note:

• /vacancies and /vacancies/:id still carry an explicit compatibility seam
• parity should be judged against the current mixed truth, not against an imagined projection-only future state

Public Vacancy Read Checks

• GET /vacancies?page=1&pageSize=1
• compare old svc-tenders host vs new svc-vacancies host
• confirm list payload shape matches
• confirm meta.projectionHealthy matches
• confirm mixed projection + legacy fallback behavior matches current host

Vacancy Detail Checks

• GET /vacancies/:id for a projection-backed vacancy posting id
• GET /vacancies/:id for a legacy vacancies-only id if one exists in the environment
• confirm 404 behavior still matches
• confirm summary shape matches current API expectations

Vacancy Application Checks

• GET /vacancy-applications/me
• POST /vacancy-applications
• POST /vacancy-applications/:id/withdraw
• POST /vacancy-applications/:id/shortlist
• POST /vacancy-applications/:id/reject
• POST /vacancy-applications/:id/accept

Check:

• auth success/denial parity
• response shape parity
• status code parity

Owner / Internal Read Checks

• GET /owner/vacancy-postings
• GET /owner/vacancy-postings/:id
• GET /owner/vacancy-applications
• GET /owner/vacancy-applications/:id
• GET /vacancy-postings/:id/applications

Check:

• auth parity
• owner scoping parity
• not-found parity
• application list parity

Auth-Protected Mutation Checks

• POST /vacancy-postings
• PATCH /vacancy-postings/:id
• POST /vacancy-postings/:id/publish
• POST /vacancy-postings/:id/close
• POST /vacancy-postings/:id/reopen

Check both:

• missing-token denial path
• authenticated happy-path if a stable fixture exists

Env-Cutover Checks

• API in fallback mode without VACANCIES_SERVICE_URL
• API in extracted mode with VACANCIES_SERVICE_URL=http://localhost:4023
• route shape unchanged through gateway
• upstream service target only changes by env

Rollback Checks

• unset VACANCIES_SERVICE_URL or point it back to TENDERS_SERVICE_URL
• restart only the API gateway
• confirm vacancy route family returns to old host behavior

Public-Read Compatibility Interpretation

Do not flag the following as cutover drift by itself:

• public vacancy list/detail still drawing from legacy vacancies when no projection-backed posting exists

Do flag as drift:

• different fallback behavior between old and new hosts
• different response shape for the same mixed-truth route
• different auth/status behavior