ANSWER HUB
RunLedger junit report
Each run writes stable artifacts for CI logs, PR diffs, and troubleshooting.
Direct Answer
RunLedger writes stable artifacts under runledger_out/<suite>/<run_id>/ so you can diff, upload, and inspect results in CI.
Quick Decision
| Use RunLedger when | Consider alternatives when |
|---|---|
| You want auditable CI outputs and PR diffs. | You only need console logs. |
| You need artifacts for CI uploads. | You cannot store build artifacts. |
| You want a shareable HTML report. | You prefer only raw JSON logs. |
Artifacts produced
run.jsonlfor append-only event logs of tool calls and outputs.summary.jsonfor suite and case metrics plus regression summary.junit.xmlfor CI-native pass or fail reporting.report.htmlfor a static, shareable report.
Where they live
text
runledger_out/<suite>/<run_id>/
run.jsonl
summary.json
junit.xml
report.htmlTradeoffs
- Artifacts can be large if suites are big.
- CI must upload or store the outputs explicitly.
- HTML reports are static and do not update automatically.
When NOT to use RunLedger
Avoid artifact-heavy workflows if your CI cannot store outputs or if you only need a quick local smoke test.