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.

Example draft (not published): if POST /api/v1/bookdirect/properties is approved, rewrite Owner property setup step 1 on /next to that Middleware Backend URL. Core Backend

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

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