Vacancy Migration Workflow Decision

Canonical migration owner

svc-vacancies is now the canonical migration owner for vacancy-specific schema changes.

Whether migrate:all includes Vacancy

Yes, migrate:all now includes npm --prefix services/svc-vacancies run migrate.

Canonical operator path

Operators should run npm run migrate:all to apply all migrations, including vacancy schema changes.

Individual vacancy migrations can be run with npm --prefix services/svc-vacancies run migrate.

Mixed/shared migration notes

The following vacancy-related migrations remain in svc-tenders/migrations because they are mixed with accommodation concerns:

• 0005_vacancies_accommodations.sql (legacy shared vacancy/accommodation)
• 0042_vacancy_accommodation_context.sql (adds accommodation_mode to vacancies, accommodation_need to vacancy_applications, listing_context to accommodations)
• 0043_vacancy_accommodation_declaration_details.sql (adds details_json to both vacancy_postings and accommodation_listings)
• 0044_add_details_json_to_views.sql (adds details_json to vacancy and accommodation views)

These are not transferred because they affect both vacancy and accommodation schemas, requiring coordinated migration ownership.

Explicit public-read compatibility note

Public vacancy discovery (GET /vacancies, GET /vacancies/:id) remains compatibility-backed, falling back to legacy vacancies table when projection-backed vacancy_postings are not available. This migration ownership cleanup does not change public-read behavior.

What changed

• Transferred pure vacancy migration (0032) from svc-tenders to svc-vacancies as (0001)
• Added migrate script to svc-vacancies
• Updated root migrate:all to include svc-vacancies
• Removed transferred migration from svc-tenders/migrations
• Updated topology and residue documentation