Autoadoption logs

[j-chmielewski]

• add scoped log buffering to auto-adoption attempts
• merge persisted failure logs from Core and component streams
• use existing wizard.auto_adoption_state.adoption_result[component].logs persistence
• enable debug-level tracing for defguard_setup::auto_adoption
• cleanup previous logs on successful adoption

[Copilot]

Pull request overview

Adds scoped tracing log buffering to auto-adoption attempts so that actionable Core + component-stream logs can be persisted into the existing wizard.auto_adoption_state.adoption_result[component].logs on failures, and enables debug-level tracing for the auto-adoption module.

Changes:

• Scoped Core tracing capture via scope_setup_logs, and merged Core + component stream logs on failures.
• Persist failure logs per component while avoiding persisting logs for successful adoptions.
• Added integration tests asserting per-component failure logs are persisted and include Core debug lines; enabled defguard_setup::auto_adoption=debug in the main binary log filter.

Reviewed changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
crates/defguard_setup/src/auto_adoption.rs	Introduces scoped Core log buffering and merges Core + component logs into persisted failure results.
crates/defguard_setup/tests/auto_adoption_wizard.rs	Adds tests validating that per-component failure logs are persisted and include Core debug output.
crates/defguard_setup/Cargo.toml	Adds tracing-subscriber as a dev-dependency for the new tests’ tracing initialization.
crates/defguard/src/main.rs	Extends the runtime log filter to enable debug logs for defguard_setup::auto_adoption.
Cargo.lock	Locks the additional dev dependency.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.