VACANCY PUBLIC READ STATUS

Vacancy public-read status

Route status

• GET /vacancies: still compatibility-backed
• GET /vacancies/:id: still compatibility-backed

Cleanup level chosen

• EXPLICIT COMPATIBILITY WRAP

This was the highest safe cleanup level for Sprint 74 because it reduced ambiguity without pretending the public vacancy surface had already converged onto projection-only truth.

What that means

• preferred public-read truth exists through projection-backed vacancy posting views
• compatibility fallback to legacy vacancies still remains active
• the extracted Vacancy runtime now names those branches more explicitly
• current route shape, gateway behavior, and auth behavior remain unchanged

What remains for later

• true projection-only convergence for GET /vacancies
• true projection-only convergence for GET /vacancies/:id
• cleanup of old compatibility residue still present in svc-tenders
• possible future reduction of web-side fallback dependence on richer static catalog truth

Notes

Sprint 74 should be read as public-read clarification plus boundary hardening, not as proof that Vacancy public discovery is fully cleaned up.