feat: bmalph report — post-run summary command

[LarsCowe]

Summary

After Ralph runs, there's no structured summary of what happened. .response_analysis is overwritten each loop, so history is lost.

Proposed Solution

A bmalph report command that:

1. Parses logs/ralph.log for loop count, duration, and outcome history
2. Reads final status.json and @fix_plan.md state
3. Aggregates per-loop analysis into a coherent summary
4. Outputs a formatted report to stdout

Prerequisites

• Accumulate per-loop analysis in logs/analysis_history.jsonl instead of overwriting .response_analysis
• This requires a Ralph-side change to append rather than overwrite

Options

• --json — Machine-readable output for CI integration
• --loops <n> — Show only the last N loops (default: all)

Alternatives Considered

• Manual inspection of logs/ralph.log (verbose, unstructured)
• External log aggregation (overkill for local dev)

Additional Context

Useful for understanding Ralph's behavior across multiple loops, especially when debugging stuck loops or validating circuit breaker triggers.