Rollback window is closed in Sprint 65.

Whether retirement is approved now

Retirement of the old svc-tenders accommodation host is approved and executed.

Why retirement is approved

The Sprint 64 cutoff condition was satisfied:

• the normal root dev entrypoints now provision svc-accommodations as part of the primary stack

Verified examples:

• package.json dev
• package.json dev:core
• scripts/dev-bootstrap.js, which still shells into npm run dev:clean:start and therefore now inherits the updated dev stack

Current consequence:

• the gateway and docs treat svc-accommodations as the primary runtime
• the ordinary repo startup flow now provisions that primary runtime automatically
• the old svc-tenders accommodation host no longer needs to remain mounted for normal startup or rollback

Cutoff condition that was satisfied

• root primary dev entrypoints now start svc-accommodations as part of the normal stack, so dev, dev:core, and dev:one no longer rely on the legacy svc-tenders accommodation host being present

Exact deletion package once the cutoff condition is met

Deleted from the legacy host slice:

1. accommodation mount and related wiring from services/svc-tenders/src/server.ts
2. services/svc-tenders/src/routes/registerAccommodationRoutes.ts
3. services/svc-tenders/src/routes/support/accommodationRouteSupport.ts
4. no-longer-needed copied active accommodation runtime files in services/svc-tenders/src/accommodation:
   • commandHandlers.ts
   • readModel.ts
   • quote.ts
   • validation.ts
   • domain.ts
   • projections.ts
5. matching compiled .js residue for the removed files in the same cut

Kept for the follow-up residue pass:

• services/svc-tenders/src/accommodation/contracts.ts
• services/svc-tenders/src/accommodation/ownerReadRepository.ts
• services/svc-tenders/src/accommodation/compatibilityReadRepository.ts
• root compatibility methods in services/svc-tenders/src/repository.ts
• mixed accommodation-related migrations in services/svc-tenders/migrations

Remaining blockers

No blocker remains for legacy accommodation host retirement itself.

What remains unresolved is not a rollback blocker:

• accommodation compatibility residue in svc-tenders
• mixed migration ownership

Notes

• Migration ownership remains mixed, but it did not block retiring the legacy route host.
• The next sprint can focus on migration ownership cleanup or the next extracted domain rather than preserving accommodation fallback drift.