Yes.

Cutoff Condition Satisfied

Rollback closed after the normal root startup paths were updated so that:

• dev
• dev:core
• dev:one

all now provision svc-vacancies as part of the expected primary startup path.

Why This Condition Matters

Current live Vacancy routing already points the API seam at:

• http://localhost:4023

But current root startup still launches:

• svc-auth
• services/api
• svc-tenders
• other shared services

and does not launch:

• svc-vacancies

So the old Vacancy host still acts as practical safety coverage for the normal developer/operator startup path.

Rollback Implications

Implications:

• the old svc-tenders Vacancy route host no longer needs to remain live
• the prepared legacy Vacancy deletion package could be executed immediately
• Vacancy route-host rollback is no longer an env flip

Notes

• public Vacancy list/detail remain compatibility-backed in current behavior
• that compatibility truth did not block route-host retirement
• gateway route shape remains unchanged
• auth behavior remains unchanged