It used the canonical extracted accommodation runtime target:

• http://localhost:4022

It kept the old colocated accommodation host available on:

• http://localhost:4020

Exact env change used

Changed:

• services/api/.env

From:

• ACCOMMODATIONS_SERVICE_URL=http://localhost:4020

To:

• ACCOMMODATIONS_SERVICE_URL=http://localhost:4022

No gateway route definitions changed.

No auth behavior changed.

Cutover steps

1. verify old host remained available on 4020
2. start svc-accommodations on 4022
3. confirm live API gateway on 4001 still matched old host before the seam flip
4. change only ACCOMMODATIONS_SERVICE_URL in services/api/.env
5. restart the live API process on 4001
6. run immediate smoke checks through the live API gateway
7. compare the live API responses to direct svc-accommodations responses

Smoke checks run

• GET /api/v1/accommodations?page=1&pageSize=1
• GET /api/v1/accommodations/ACC-GE-2026-0102
• POST /api/v1/accommodations/ACC-GE-2026-0102/quote
• GET /api/v1/my-accommodation-bookings
• GET /api/v1/owner/accommodation-listings
• GET /api/v1/owner/accommodation-reservations
• POST /api/v1/accommodation-listings without a bearer token

Authenticated checks used the existing dev impersonation flow through /auth/dev/impersonate.

Observations

• post-cutover gateway responses matched direct svc-accommodations responses for the checked set
• status codes matched expected parity
• auth behavior stayed unchanged
• old svc-tenders accommodation hosting remained available on 4020
• quote responses stayed correct; the only request-time variance was computedAt

Cutover outcome

• live env-only cutover was executed successfully
• cutover remained in place
• rollback was not needed

Rollback notes

Rollback remained available throughout the window:

1. change ACCOMMODATIONS_SERVICE_URL back to http://localhost:4020
2. restart services/api
3. verify fallback against old svc-tenders accommodation hosting

That rollback path was not used because no serious mismatch occurred.