Add log aggregator redaction summary report

[h1065153539-create]

Summary

Adds an audit-friendly redaction summary report for log aggregation runs, covering processed lines, malformed records, redacted-field counts, and per-source-file totals without exposing raw secret-looking values.

Fixes #2.

Changes

• Tracks processed, parsed, malformed, and redacted counts while preserving the existing default log aggregation outputs.
• Adds --redaction-summary and --redaction-summary-format json|text CLI options.
• Redacts secret-looking field names and inline token/password/authorization values before entries or summaries are exported.
• Documents the operations command for JSON and text redaction summaries.
• Adds focused unittest coverage for valid, malformed, and secret-like fixture inputs plus text/JSON summary export.

Testing

• python -m unittest discover -s tests -v passed 3 tests.
• python -m py_compile tools/log_aggregator.py tests/test_log_aggregator_redaction_summary.py build.py tools/ai_migrator.py passed.
• Manual CLI smoke with --redaction-summary-format text produced processed/malformed/redacted counts and preserved the normal report output.
• python build.py was attempted. It timed out while the bundled ools/encryptly/windows-x64/encryptly.exe preflight was running; the resulting diagnostic/build-00000000.json is included to show the blocker. No new .logd was produced in this Windows validation environment.

Checklist

• Relevant modules affected by these changes build locally
• Tests pass locally
• Diagnostic build log is committed in this PR
• Documentation has been updated, if applicable
• Configuration or schema changes are documented, if applicable
• No generated build artifacts are committed, except the required diagnostic build log
• Changes are scoped to the PR purpose and avoid unrelated cleanup
• Security, privacy, and error-handling implications have been considered

---

• I would like to request that my diagnostic build log is removed before merging

[Soengkit]

Thanks for the PR. I am closing this because Soengkit/zeroeye is only my working fork of the upstream repository, not an official bounty intake or payment queue. The fork parent/source is NemoMi/zeroeye: https://github.com/NemoMi/zeroeye. Please use the upstream owner current process for any submission or claim, and do not post payment details here.