Niro v0.1.71

Summary

When a customer penetration-test report is requested (the default), a run that does not produce one now fails visibly mid-run, instead of only at the very end — so a skipped report is caught and retried in place.

Changes

• A niro find or niro fix run that requested a report now surfaces a missing report mid-run and retries it, rather than discovering the absence only at the end. A run whose report genuinely cannot be produced still fails, and publishes its findings summary. To run without a report, pass --generate-report=false.

Security

None.

Compatibility and upgrade

• No action required. No configuration, CLI flag, or MCP tool changed.

Known issues

• checksums.txt covers platform archives but not niro.mcpb.
• Release artifacts have no detached signatures, provenance attestation, or SBOM.
• niro upgrade follows stable, not dev or RC; Windows users rerun the installer to change versions.