v0.2.5

What's Changed

• fix(viewer): contain claim filters in a panel by @PeterGrace in #30
• build(deps): bump rmcp from 3.7.0 to 3.8.0 in the cargo group across 1 directory by @dependabot[bot] in #24
• claims-audit: pull request mode and a per-call ledger helper by @PeterGrace in #33
• feat: let a tool call choose its ledger (catalog path per call) by @PeterGrace in #34
• feat: claims-mcp rebase, so parallel branches that write claims.json can merge by @PeterGrace in #35
• chore: prepare 0.2.5 release by @PeterGrace in #36

Full Changelog: v0.2.4...v0.2.5

v0.2.4

What's Changed

• Documentation site on GitHub Pages; slim README by @PeterGrace in #25
• Claims viewer on the docs site by @PeterGrace in #27
• feat: formally specify claims.json with generated JSON Schema by @PeterGrace in #28
• chore: prepare 0.2.4 release by @PeterGrace in #29

Full Changelog: v0.2.3...v0.2.4

v0.2.3

What's Changed

• Add commit-pinned anchors, absence refutations, and recheck by @PeterGrace in #22
• chore: release 0.2.3 by @PeterGrace in #23

Full Changelog: v0.2.2...v0.2.3

v0.2.2

What's Changed

• docs: mark the implementation plan as historical (CLM-0034) by @PeterGrace in #14
• feat: ship the PDF report template and notes guidance with the binary by @PeterGrace in #19
• chore: release 0.2.2 by @PeterGrace in #20

Full Changelog: v0.2.1...v0.2.2

v0.2.1

What's Changed

• chore(deps): Bump thiserror from 2.0.6 to 2.0.21 in the cargo group across 1 directory by @dependabot[bot] in #8
• audit: re-audit claims catalog against 0.2.0 and cover issues #2, #4, #9 by @PeterGrace in #13
• Add next_steps TL;DR: ranked next steps from a claims catalog by @PeterGrace in #15
• PDF report: summary and full detail modes by @PeterGrace in #16
• Release 0.2.1 by @PeterGrace in #17

New Contributors

• @dependabot[bot] made their first contribution in #8

Full Changelog: v0.2.0...v0.2.1

v0.2.0

Upgrading from 0.1.0

0.2.0 seals every record in the claims catalog and refuses writes to any catalog that fails verification. Catalogs written by 0.1.0 (schema_version 1) have no seals yet, so the server treats them as read-only until they are migrated. Reads and audit_report still work.

A maintainer (not an agent) should migrate each catalog once, then commit the result:

claims-mcp --catalog claims.json seal --adopt
claims-mcp --catalog claims.json verify   # expect: integrity verified
git commit -am "chore: migrate claims catalog to sealed schema v2"

Migrated records are labeled adopt in verify and audit_report, which separates them from records the server writes. After the migration, edit the catalog only through the MCP tools. A hand edit blocks every write until you restore the file from git. See Integrity seals in the README.

What's Changed

• chore: license under Apache 2.0, copyright Hypotheosis by @PeterGrace in #6
• chore: Dependabot config and security policy for public release by @PeterGrace in #7
• feat: detect direct edits to the claims catalog with HMAC seals keyed by a built-in key by @PeterGrace in #10
• chore: release 0.2.0 by @PeterGrace in #11

Full Changelog: v0.1.0...v0.2.0

v0.1.0

What's Changed

• feat: generate PDF audit reports from claims.json with Typst by @PeterGrace in #3
• feat: CI for PRs with audit-report artifact, and tagged multi-platform release pipeline by @PeterGrace in #5

New Contributors

• @PeterGrace made their first contribution in #3

Full Changelog: https://github.com/hypotheosis/claims-mcp/commits/v0.1.0