# Reuse Shared Management Services For Starter

Imported Starter/Essential v1 OpenAPI traffic in the merged Premium runtime must reuse the same `tidb-mgmt-portal` and `tidb-mgmt-service` instances as Premium-family traffic. This matches real staging, where the management services are shared rather than split into separate Premium and Starter copies.

The shared public gateway may add Starter-specific routes, but those routes target the shared management service instances. The implementation must not introduce Starter-specific `tidb-mgmt-portal` or `tidb-mgmt-service` service names as the product boundary; Starter separation lives in route ownership, config/backend enablement, skill guidance, train artifacts, and proof labeling.

Enabling Starter on the shared management services must be additive. The merged Premium runtime preserves existing Premium and Dedicated wiring, then adds the Starter/Essential v1 backend dependencies needed for `/v1beta1` Starter routes. It must not swap the shared management service configuration to the retired `starter-full` config shape because that would make the merged Premium proof behave like the old standalone Starter persona and could regress existing Premium trains.