feat(cli): JUnit + JSON reporters for run-all (CI integration)

[GamalAnwar]

Summary

Adds CI-friendly reporters to forge run-all, so teams running collections in pipelines get the same machine-readable outputs they get today from bru run --reporter-junit/--reporter-json — removing a switching cost for Bruno/Newman users.

forge run-all ./collection \
  --reporter-junit report.xml \
  --reporter-json  report.json

• JUnit XML: each .http file becomes a <testsuite> and each request a <testcase>. Transport errors map to <error>; failed assertions and post-response test()s map to <failure> with the subject op expected (got actual) detail. Names/values are XML-escaped. Consumable by GitHub Actions, GitLab, Jenkins, etc.
• JSON: a { summary: { total, passed, failed }, suites: [...] } document carrying the full, already-serde-serializable run results.

Design

Report generation is a pure, unit-tested forge_engine::report module (junit_xml / json_report over ReportSuite groups) — the CLI just accumulates runs per file and writes the requested formats. This keeps the logic in the well-tested engine layer rather than the binary.

Testing

• Unit tests for both formats (counts, <failure>/<error> shapes, XML escaping, empty input).
• CLI integration tests asserting the written report.xml/report.json contents and that nothing is written when no reporter flag is passed.
• report.rs at ~99% line coverage; workspace stays above the 95% gate.

🤖 Generated with Claude Code

---

Generated by Claude Code