Add run report export

[melonattacker]

Motivation

Users need a shareable local summary of what happened during an AI agent run.

logira view and logira explain are useful for local inspection, but a report command would make it easier to:

• save evidence
• share a run with another person
• attach results to a GitHub issue or PR
• keep a local audit record
• prepare for future local UI or hosted UI workflows

This is useful for individuals today and can later become the foundation for team reporting.

Goal

Add a logira report command.

Proposed CLI

logira report last
logira report last --format markdown
logira report last --format json
logira report last --output report.md
logira report last --redact
logira report last --no-redact

Initial formats

Required:

• markdown
• json

HTML can be deferred.

Report contents

The report should include:

• run ID
• command
• tool
• start/end time
• duration
• event counts
• detection counts by severity
• risk level
• top detections
• top commands
• top file paths
• top destinations
• inspection hints

Redaction

Reports should support basic best-effort redaction.

Initial redaction should cover:

• home directory normalization
• common token/password argv patterns
• obvious environment-like secret values

Examples:

/home/alice/project

becomes:

$HOME/project

--token abc123

becomes:

--token [REDACTED]

Default behavior:

redact by default

Users can explicitly disable redaction:

logira report last --no-redact

Non-goals

This issue should not implement:

• hosted report sharing
• cloud upload
• PDF export
• SARIF export
• compliance-grade DLP
• perfect secret detection
• team dashboard

Acceptance criteria

• logira report last --format markdown works.
• logira report last --format json works.
• report output can be written to stdout.
• report output can be written to a file.
• report includes summary, risk, detections, and top activity.
• report supports basic redaction.
• --no-redact disables redaction.
• tests cover markdown/json output and basic redaction.

Notes

This is a should-have for v0.2.0.

If it does not fit into v0.2.0, it can move to v0.2.1 without blocking the release.