v0.1.56

Niro v0.1.56

Summary

This release makes telemetry status reporting match the selected project's
niro.yaml instead of claiming a process-wide state before a project has been
selected. It also improves release visibility in the public README.

Changes

• Removed the telemetry-enabled notice and telemetry_state activity record
  from niro serve startup, where no project configuration is available yet.
• Removed the generic telemetry notice printed after niro upgrade, because
  telemetry policy is configured per project rather than per installation.
• Added a telemetry_disabled activity record, including the selected
  niro.yaml path, when start_pentest resolves telemetry: false.
• Documented when and where the project-scoped telemetry status is recorded.
• Added a latest-stable-release badge to the public README.

Security

This release does not expand telemetry collection or change its payload,
endpoint, default, or per-project opt-out behavior. It removes misleading
status claims made before project policy is known and records the resolved
disabled state after the project configuration is selected. No developer
agent, attacker agent, attack-tool sandbox, CLI permission, or target-access
behavior changed.

Compatibility and upgrade

There are no CLI, MCP, configuration, or runtime compatibility changes. Existing
telemetry: false settings continue to suppress telemetry without modification.
Upgrade to v0.1.56 when validating telemetry status through CLI output or
niro-cli.jsonl.

Known issues

• checksums.txt covers the platform archives but does not yet include
  niro.mcpb.
• Release artifacts do not yet include detached signatures, a public binary
  provenance attestation, or an SBOM.
• niro upgrade follows stable rather than dev or RC, and Windows users must
  rerun the installer to change versions.