[M0nsxx]

Summary

Adds nirium report summary and nirium report export anchors|payments|payroll, thin clients for the Reporting node's GET /api/reporting/summary and GET /api/reporting/export:

nirium report summary --from 2026-10-01 --json
nirium report export anchors --from 2026-10-01 | xargs -n1 nirium verify

• export anchors prints exactly one CID per line on stdout, nothing else - pipeable straight into nirium verify. The row count and the "not certified regulatory reporting" disclaimer go to stderr so neither ends up in that pipe.
• --csv <file> writes the server's CSV export to that file instead of printing rows.
• --json prints the full response (type, period, rowCount, rows, disclaimer); mutually exclusive with --csv.
• Both subcommands keep and reprint the server's own "not certified regulatory reporting" disclaimer.

Test plan

• New test/report.test.js (15 cases) against a local HTTP server standing in for the Reporting node: summary JSON/human output, query param forwarding, server-error surfacing; export's CID-only stdout for anchors, the stdout/stderr split, --json, --csv (file write + mutual exclusivity with --json), input validation (bad type, non-positive --limit) before any network call, and query param forwarding.
• Full suite green: npm test.
• node --check bin/nirium.js clean.

Closes #136

[Eras256]

Approving — clean thin client for the Reporting node's summary/export, export anchors pipes one CID per row straight into verify as intended, keeps the "not certified regulatory reporting" disclaimer. CI green (4/4).

[Eras256]

Approving - conflict resolution looks correct (interleaved anchor/report blocks in bin/nirium.js, plus package.json/CHANGELOG entries), 91/91 tests pass locally including anchor+report together. CI at 3/4, last check still running, nothing failed - merging once it finishes.

[Eras256]

Approving — conflict resolved cleanly (anchor + verify --gateway + report all registered together in bin/nirium.js), 99/99 tests pass locally, CI green (4/4). Merging.