It started as a coexistence runtime, became the active primary host after the Sprint 62 env-only cutover, and now remains the sole accommodation route host after the Sprint 65 legacy-host retirement cut.

New runtime location

New runtime:

• services/svc-accommodations

Primary bootstrap entry:

• services/svc-accommodations/src/server.ts

Runtime shell files:

• services/svc-accommodations/src/config.ts
• services/svc-accommodations/src/db.ts
• services/svc-accommodations/src/auth.ts
• services/svc-accommodations/src/http/authTypes.ts
• services/svc-accommodations/package.json
• services/svc-accommodations/tsconfig.json

What files were copied

Copied accommodation-owned runtime files:

• services/svc-accommodations/src/accommodation/contracts.ts
• services/svc-accommodations/src/accommodation/validation.ts
• services/svc-accommodations/src/accommodation/domain.ts
• services/svc-accommodations/src/accommodation/projections.ts
• services/svc-accommodations/src/accommodation/commandHandlers.ts
• services/svc-accommodations/src/accommodation/readModel.ts
• services/svc-accommodations/src/accommodation/ownerReadRepository.ts
• services/svc-accommodations/src/accommodation/quote.ts
• services/svc-accommodations/src/routes/registerAccommodationRoutes.ts
• services/svc-accommodations/src/routes/support/accommodationRouteSupport.ts
• services/svc-accommodations/src/routes/support/detailExtractionSupport.ts

Small additional runtime files added because the copied accommodation slice needed them:

• local config loader
• local DB pool bootstrap
• local auth ingress adapter
• local auth request types

What remains shared

Shared on purpose:

• gateway proxy routes in services/api
• services/api/src/routes/accommodationsServiceTarget.ts
• shared /auth/me principal resolution contract
• shared bearer/JWT ingress semantics

These stayed shared so gateway route shape and auth behavior remain unchanged.

What still remains old-host-only

Old-host-only residue that still remains outside svc-accommodations:

• services/svc-tenders/src/accommodation/compatibilityReadRepository.ts
• root accommodation compatibility hosting in services/svc-tenders/src/repository.ts
• mixed/legacy accommodation migrations still hosted only in services/svc-tenders/migrations

Reason:

• they are compatibility residue or unresolved migration ownership rather than clean move-first runtime truth

Env handling

Runtime env contract:

• PORT
• AUTH_SERVICE_URL
• DATABASE_URL
• JWT_SECRET

Dev loading behavior:

• load local/runtime .env files if present
• otherwise reuse the existing dev DATABASE_URL and JWT_SECRET from svc-tenders / svc-auth env files without inheriting sibling service PORT

Coexistence / rollback notes

Current coexistence model:

• svc-accommodations is the active primary runtime
• gateway seam stays ACCOMMODATIONS_SERVICE_URL ?? TENDERS_SERVICE_URL
• old svc-tenders accommodation route hosting is retired

Rollback to the old route host is no longer available.

Dev entry points added

Added root scripts:

• npm run dev:accommodations

Port-cleanup awareness updated:

• root dev:ports:free now includes 4022
• scripts/dev-bootstrap.js dev-port cleanup now includes 4022