Accommodation Cutover Parity Checklist

Purpose

This checklist defines the minimum parity verification needed before any env-only accommodation cutover.

It assumes:

• old accommodation hosting in svc-tenders still exists
• new copy-first runtime exists in svc-accommodations
• gateway seam remains ACCOMMODATIONS_SERVICE_URL ?? TENDERS_SERVICE_URL

1. Read-route checks

• GET /accommodations
• GET /accommodations/:id
• POST /accommodations/:id/quote

Verify:

• status code parity
• response-shape parity
• quote response parity
• compatibility-read behavior remains explicit where relevant

2. Booking / reservation checks

• POST /accommodation-bookings
• POST /accommodation-bookings/:id/confirm
• POST /accommodation-bookings/:id/reject
• POST /accommodation-bookings/:id/cancel
• GET /my-accommodation-bookings

Verify:

• authenticated happy-path mutation parity
• denial-path auth parity
• persisted read-back parity where practical

3. Owner listing / reservation checks

• GET /owner/accommodation-listings
• GET /owner/accommodation-listings/:id
• GET /owner/accommodation-reservations
• GET /owner/accommodation-reservations/:id

Verify:

• owner-only visibility parity
• not-found parity
• reservation filter behavior parity

4. Auth-protected mutation checks

• POST /accommodation-listings
• PATCH /accommodation-listings/:id
• POST /accommodation-listings/:id/publish
• POST /accommodation-listings/:id/unpublish

Verify:

• missing-token denial parity
• principal-resolution parity
• active-principal requirement parity
• happy-path mutation response parity

5. Env cutover checks

Pre-cutover:

• svc-tenders accommodation host reachable
• svc-accommodations reachable
• gateway fallback mode works

Cutover rehearsal:

• set ACCOMMODATIONS_SERVICE_URL=http://localhost:4022
• keep gateway route shape unchanged
• rerun read, owner, booking, and mutation smoke checks through API gateway

6. Rollback checks

Rollback path:

1. unset or change ACCOMMODATIONS_SERVICE_URL
2. restart gateway if needed for env pickup
3. verify gateway fallback path returns to svc-tenders

Verify after rollback:

• at least one public read route
• at least one owner/auth-protected route
• at least one booking or listing mutation denial/smoke route

7. Known truth to keep explicit

• legacy compatibility catalog reads still live in the old host path
• root repository compatibility hosting still exists
• migration ownership is not yet fully transferred to svc-accommodations

Parity should not hide those facts.