insights-correlations (#22)

Reviewed-on: #22

crates/application/src/users/deps.rs

@@ -7,9 +7,6 @@ use domain::ports::{
 };
 use domain::value_objects::InstanceIdentity;
 
-/// The local half of the former `GetProfileDeps` split (ADR-0004). `user` and
-/// `instance` build the always-populated `ProfileIdentity`; `stats`/`diary`/
-/// `social_query` are unchanged from before the split.
 pub struct GetLocalProfileDeps {
     pub stats: Arc<dyn StatsRepository>,
     pub diary: Arc<dyn DiaryQuery>,
@@ -18,18 +15,12 @@ pub struct GetLocalProfileDeps {
     pub instance: InstanceIdentity,
 }
 
-/// The federated half of the former `GetProfileDeps` split. No `user`/`instance` —
-/// the federated handler builds identity from the resolved remote actor and never
-/// reads a local user row for this path.
 pub struct GetFederatedProfileStatsDeps {
     pub stats: Arc<dyn StatsRepository>,
     pub diary: Arc<dyn DiaryQuery>,
     pub social_query: Arc<dyn FollowGraphQuery>,
 }
 
-/// Backs page-chrome data (email/role badge, pending-follow badge). See the error
-/// policy note on `get_page_viewer::execute`: this deliberately propagates errors
-/// rather than degrading internally — the caller decides chrome degrades.
 pub struct GetPageViewerDeps {
     pub user: Arc<dyn UserRepository>,
     pub follow_graph: Arc<dyn FollowGraphQuery>,
@@ -82,9 +73,6 @@ pub struct AuthorizeAdminDeps {
     pub user: Arc<dyn UserRepository>,
 }
 
-/// `Option` mirrors `Repositories::federated_profile` — genuine optional
-/// configuration (federation on/off), not a container-shape workaround. Same
-/// exemption as `Services::person_enrichment`.
 pub struct GetFederatedProfileDeps {
     pub federated_profile: Option<Arc<dyn FederatedProfileQuery>>,
 }