Milestone 6 - Step 0

codetracer-python-recorder/src/monitoring/callbacks.rs: 
codetracer-python-recorder/src/monitoring/mod.rs: 
codetracer-python-recorder/src/runtime/tracer/mod.rs: 
design-docs/codetracer-architecture-refactor-implementation-plan.status.md: 

Signed-off-by: Tzanko Matev <[email protected]>

Author: tzanko-matev

codetracer-python-recorder/src/monitoring/callbacks.rs

@@ -16,7 +16,7 @@ use recorder_errors::ErrorCode;
 use super::api::Tracer;
 use super::{register_callback, EventId, EventSet, MonitoringEvents, ToolId};
 
-pub use super::{events_union, CallbackFn, CallbackOutcome, CallbackResult};
+pub use super::{CallbackFn, CallbackOutcome, CallbackResult};
 
 /// Global tracer state shared between callback invocations and installer.
 pub(super) struct Global {
@@ -486,6 +486,7 @@ type CallbackFactory = for<'py> fn(&Bound<'py, PyModule>) -> PyResult<CallbackFn
 /// Metadata describing how to register a sys.monitoring callback.
 pub struct CallbackSpec {
     /// Debug label (mirrors the PyO3 function name).
+    #[allow(dead_code)]
     pub name: &'static str,
     event: fn(&MonitoringEvents) -> EventId,
     factory: CallbackFactory,

codetracer-python-recorder/src/monitoring/mod.rs

@@ -4,9 +4,9 @@ use pyo3::prelude::*;
 use pyo3::types::PyCFunction;
 use std::sync::OnceLock;
 
-pub mod api;
-pub mod callbacks;
-pub mod install;
+pub(crate) mod api;
+pub(crate) mod callbacks;
+pub(crate) mod install;
 pub mod tracer;
 
 pub use api::Tracer;

codetracer-python-recorder/src/runtime/tracer/mod.rs

@@ -1,11 +1,12 @@
 //! Collaborators for the runtime tracer lifecycle, IO coordination, filtering, and event handling.
 //!
-//! Re-exports [`RuntimeTracer`] so downstream callers continue using `crate::runtime::RuntimeTracer`.
+//! Re-exports [`RuntimeTracer`] so downstream callers continue using `crate::runtime::RuntimeTracer`
+//! without exposing the implementation modules outside the crate.
 
-pub mod events;
-pub mod filtering;
-pub mod io;
-pub mod lifecycle;
+pub(crate) mod events;
+pub(crate) mod filtering;
+pub(crate) mod io;
+pub(crate) mod lifecycle;
 
 mod runtime_tracer;
 

design-docs/codetracer-architecture-refactor-implementation-plan.status.md

@@ -85,6 +85,7 @@
 - ✅ Milestone 5 Step 4: carved lifecycle orchestration into `runtime::tracer::lifecycle::LifecycleController`, covering activation gating, writer initialisation/finalisation, policy enforcement, failure cleanup, and trace id scoping. Added focused unit tests for the controller and re-ran `just test` (nextest + pytest) to verify no behavioural drift.
 - ✅ Milestone 5 Step 5: shifted event handling into `runtime::tracer::events`, relocating the `Tracer` trait implementation alongside failure-injection helpers and telemetry wiring. `RuntimeTracer` now exposes a slim collaborator API (`mark_event`, `flush_io_before_step`, `ensure_function_id`), while tests import the trait explicitly. `just test` (nextest + pytest) confirms the callbacks behave identically after the split.
 - ✅ Milestone 5 Step 6: harmonised the tracer module facade by tightening `IoCoordinator` visibility, pruning unused re-exports, documenting the `runtime::tracer` layout, and updating design docs that referenced the legacy `runtime_tracer.rs` path. `just test` (Rust nextest + Python pytest) verified the cleanup.
+- 🔄 Milestone 6 Kickoff: audited crate exports to keep the new module tree internal by default (runtime tracer collaborators + monitoring submodules now `pub(crate)`), and confirmed packaging metadata/docs already reference the updated paths so no additional adjustments are required yet. Pending follow-up: sweep for dead imports and finalise documentation/CI updates before ADR 0011 sign-off.
 
 
 ### Planned Extraction Order (Milestone 4)