优化结构

internal/service/README.md

@@ -2,7 +2,7 @@
 
 `service` adapts HTTP-facing DTOs to business usecases and owns application
 orchestration. Request/response/filter contracts live in `dto/`; the root
-package is a compatibility facade and module provider aggregator.
+package aggregates module provider sets for Wire.
 
 Implementations are grouped by the same business modules as `biz` and `data`:
 
@@ -18,9 +18,8 @@ The stateless router-prefix helper lives in `internal/utils/routepath` because
 both service modules and HTTP middleware use it; it does not depend on a
 business usecase or DTO.
 
-Each module owns its Wire `ProviderSet`. The root `service` package re-exports
-the existing service types and constructors through aliases and thin wrappers, so handlers, middleware
-and generated Wire code can migrate independently without a flag day.
+Each module owns its Wire `ProviderSet`; the root package only composes those
+sets and does not re-export service types or constructors.
 
 Within `system/`, larger cross-cutting resources stay in the same package while
 being split by concern (`audit.go` and its error/log companions, `media.go` and