v0.2.0

Security-hardening release from a line-wide code review. Highlights: secure-by-default approver gate for high/critical operations (init seeds a starter rules.yaml), percent-encoded URL path segments, single-sourced version, governance persistence + CLI write-path tests. See CHANGELOG.md for the full list. BREAKING: fresh installs with no rules.yaml now deny high/critical writes until an approver is recorded.

Compliance-AIops v0.1.1

Patch: config.yaml now honors the *_AIOPS_HOME env var; CLI writes are now audited + undo-recorded through the governance path (previously MCP-only). See CHANGELOG.

compliance-aiops v0.1.0

Governed compliance-evidence tooling — 15 MCP tools that read the sibling AIops tools' governance audit trails (~/.-aiops/audit.db, read-only) and produce framework-mapped (HIPAA / PCI-DSS / SOC 2 / GDPR), hash-chain-sealed, tamper-evident evidence bundles with honest evidence-strength labelling. Zero network, no platform credentials. Deterministic, fully-offline self-tests. Preview — evidence, not certification. (PyPI publish following shortly.)