Host import routes alongside their collection owners

Context

Migration spans collections with different owners and write authorities.

Decision

Serve each collection’s data-job routes from its owning HTTP function while sharing job dispatch and execution.

Alternatives Considered

Serve all data-job collections through one HTTP function. The current route layout assigns collection paths to their owning HTTP function.

Place each collection import with its record-owning module. Collection-specific import ownership remains a product question even though routes already follow owners.

Consequences

Collection authority remains distinct from import ownership. Product must decide which module owns collection-specific migration design.