Routing preference (draft reminder)

Same rule as v1 who calls what. Drafts must not weaken it.

1. Only Core Backend has the operation → frontend calls Core Backend.
2. Middleware Backend later adds the same capability → frontend calls Middleware Backend. Core Backend is an implementation note.
3. One winner. Old URL goes to “Do not call (superseded)” with a date.

Greenfield drafts: overview. Proposed lodging mount is already live on the explorer:

https://middleware-dev.bookdirect.live/api/v1/bookdirect/properties

Core

POST https://backend-dev.bookdirect.live/public/api/v1/nellalink/smart-meta-manager/entity/property

stays “Called by Middleware Backend, not by frontend.”

Scraper workers (AI Rate Match) and Resend are Middleware-side. They are not Frontend jobs. Amenity pickers stay a local slug catalog.