#180 cli: add redaction-safe JSON Lines output to doberman log

[Anonymous]

Originally created by: fu351

Context

doberman log already reads newest-first decision rows from the redacted local decision log and prints them for humans. An opt-in JSON Lines mode would let local scripts consume the same safe rows one record at a time.

Suggested starting points

• src/doberman/cli/main.py — the log command
• src/doberman/storage/log.py — redacted decision-row reads
• tests/integration/test_cli_views.py
• tests/integration/test_decision_log.py

Acceptance criteria

• [ ] Add a --jsonl option to doberman log.
• [ ] Emit exactly one valid JSON object per decision row, with no heading or separator on stdout.
• [ ] Use only fields from the already-redacted stored decision representation.
• [ ] Decode structured fields such as reason codes into JSON values rather than embedding JSON-in-a-string.
• [ ] Preserve newest-first ordering plus the existing --last and --path behavior.
• [ ] Produce empty stdout for an empty result set in JSONL mode.
• [ ] Preserve the current human-readable output when --jsonl is absent.
• [ ] Preserve existing exit and fail-safe read behavior.
• [ ] Add tests for line-by-line parsing, one-record-per-line output, ordering, --last, empty results, default-output compatibility, and redaction.

Suggested validation

Seed a temporary decision database with known redacted rows, invoke the command with CliRunner, and parse each nonempty stdout line independently with Python's standard json module.

Include a synthetic secret in the pre-redaction input and assert that it never appears in JSONL output.

Out of scope

• Changing the decision-log schema or storage format.
• Adding raw targets, arguments, prompts, file contents, or payloads.
• Adding remote log shipping or enterprise audit features.
• Replacing the default human-readable view or the TUI.

Security and compatibility

This feature must not weaken write-time redaction or reconstruct raw values. Serialization failures must not reveal the source row or secret-bearing inputs in diagnostics. Logging remains observational and must not affect a security decision.

See CONTRIBUTING.md (github.com) before opening a pull request.

[Anonymous]

Ticket changed by: fu351

• status: open --> closed