ROCMAI-84: Modularize crates/rocm-dash-tui/src/app/mod.rs

apps/rocm/src/main.rs

@@ -29730,7 +29730,7 @@ install therock";
 
         // The claim itself (onboarding only opens via an explicit `n` on the
         // Observe tab, never automatically) is proven by
-        // `crates/rocm-dash-tui/src/app/mod.rs`'s
+        // `crates/rocm-dash-tui/src/app/event_loop.rs`'s
         // `startup_focus_gate_only_opens_onboarding_for_explicit_setup_focus`
         // test and the `onboarding.rs` module doc — this assertion only
         // guards the string, not the behavior.

crates/rocm-dash-tui/src/agent/mod.rs

@@ -22,10 +22,10 @@
 //! `slash.rs`/`summary.rs` mechanical-relocation convention: this file holds
 //! the shared `AgentClient` seam; `snapshot` holds the pure JSON telemetry
 //! helpers; `tools` holds the rig `Tool` wrappers and dispatch; `clients`
-//! holds the four backend implementations. Unlike `app/mod.rs`'s private
-//! siblings, this file re-exports the submodules' public items — this module
-//! (and its pre-split `crate::agent::*` surface) has in-crate and cross-crate
-//! consumers, so the existing paths must keep resolving.
+//! holds the four backend implementations. Like `app/mod.rs`, this file
+//! re-exports the submodules' public items — this module (and its pre-split
+//! `crate::agent::*` surface) has in-crate and cross-crate consumers, so the
+//! existing paths must keep resolving.
 
 use async_trait::async_trait;