luigidemasi opened a new pull request, #27656: URL: https://github.com/apache/camel/pull/27656
Semantic audit history now shows the selected expert input when capture is explicitly enabled for that expert. Capture remains disabled by default, uses a bounded immutable snapshot, supports a registry-provided redactor, and omits input on redaction failure. Stored input reaches the configured audit sinks and the CLI/TUI/MCP reader surfaces; it never reaches telemetry observers. This follows #27649 on current `main`. The Audit TUI gains the agreed decision/evidence inspector, readable status and filters, coloured actions, linked-record navigation and pausable live refresh. Semantic CLI commands print labelled text and tables by default, reserving JSON for `--json`; listing experts reports an unset default without an error. The documentation includes real showcase screenshots and input-capture examples for YAML, XML and Java. Validation: - Semantic module: 356 tests passed; YAML semantic integration: 33 passed; semantic CLI: 91 passed. - Full TUI suite: 1,870 passed, 1 skipped. - Source checks passed for all four changed modules; YAML schemas and catalog mirrors regenerated. - Real Wolf-Defender showcase verified by the operator, with input capture enabled for `security`, auditing disabled for `decisions`, and OpenTelemetry disabled. - Live CLI and MCP event lookup returned the stored input; TUI rendering and unchanged screen selection after MCP queries verified. - Full reactor passed: `mvnd -B -ntp -Dmaven.build.cache.enabled=false clean install -DskipTests`. Input retention uses the selected audit backend, including the log sink when configured. The built-in memory backend remains bounded and non-durable. The screenshots show the UI with input capture disabled; the inspector also shows input when explicitly enabled. _AI-generated by OpenAI Codex on behalf of @luigidemasi._ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
