Update README.md

[Cubewise-Ronan]

Summary

Linked record

• Issue / change / incident:
• Target release (if any):

Risk classification

• Standard
• High-risk — threat model and two independent approvals required
• Emergency — incident/change approval and retrospective controls required

Security and privacy

• Affected assets, trust boundaries, identities, and data classes:
• Authentication / authorization / secrets / cryptography impact:
• Abuse cases and controls:
• Privacy, retention, transfer, or customer impact:
• Residual risk or approved exception:

Scope

• Components and interfaces changed:
• Deliberately out of scope:
• Compatibility or breaking-change impact:
• Dependencies, packages, CI actions, images, or licenses changed:

Validation evidence

Check	Command / CI job	Result
Formatting / pre-commit
Lint / static / type checks
Targeted tests
Full tests
Security / secret / dependency scans
Build / package / migration
Manual / integration / gateway validation

Known failures, skipped checks, or environment limitations:

Release and operations

• Configuration or migration steps:
• Deployment order and post-deployment checks:
• Monitoring and rollback trigger:
• Rollback or forward-fix procedure:
• Documentation and release notes updated:

Author checklist

• The change is minimal, issue-scoped, and contains no unrelated refactor or formatting.
• I reviewed the final diff, including generated and binary files.
• No secrets, production/customer data, personal data, or sensitive security evidence are included.
• Server-side authorization, input validation, safe errors, and safe logging were considered.
• Changed behavior has positive, negative, boundary, and regression tests as applicable.
• Repository-defined checks completed on this commit; failures and skips are disclosed above.
• Dependency and supply-chain changes were verified and pinned through the repository mechanism.
• Migration, deployment, monitoring, compatibility, and rollback impacts are documented.
• Documentation reflects the implemented behavior and does not overstate a control.
• Exceptions and residual risks have a named approver, compensating control, and expiry/follow-up.

Reviewer checklist

• The requirement, implementation, tests, and evidence agree.
• Security, privacy, data, dependency, and operational impacts were reviewed.
• The diff is focused and preserves existing contracts unless intentionally changed.
• Required checks are current and successful on the reviewed commit.
• Release and rollback steps are proportionate to the risk.