audit: review get_audit_log, trace_ui_path, list_reports, download_report, and get_view for data density and effectiveness

[matty-drexler]

Objective

Perform a comprehensive code audit and UAT review of the remaining discovery, UX, and reporting tools to ensure they adhere to our high-fidelity v1.5.0 standards (standardizing outputs into clean envelopes, pruning redundant Odoo-internal keys, and ensuring low-token, agent-friendly results).

Target Tools to Review:

1. get_audit_log: Audit the returned JSON structures. Check if log lines are cleanly formatted and compact, or if they contain duplicate/redundant payloads.
2. trace_ui_path: Verify if breadcrumb tracing is intuitive, correctly maps compositional hierarchies, and supports clean nested paths.
3. list_reports: Standardize the output into our unified metadata envelope, and verify if the reports catalog can be paginated.
4. download_report: Ensure that PDF/binary generation does not bloat or crash the stdio/text transport, and verify proper buffer/stream handling.
5. get_view: Review the raw XML/HTML views returned. Ensure we minify or compress layout files aggressively to prevent large view files from causing prompt context inflation.