Repository navigation
v0.1.14
KRY v0.1.14 fixes ledger recovery and settlement retry failures, and includes the fixes from the unpublished v0.1.13 tag.
Accounting and recovery
- Unknown debit outcomes keep the settlement grant consumed. Partial-debit adjustment preserves that protection throughout its update.
- Interrupted public operations and cache refreshes cannot leave replayable changes behind. Capacity checks read durable state without flushing pending changes.
- Recovery acknowledgement refuses negative restored balances, preserves debit history and reports success only when accounting is available.
- Included v0.1.13 changes protect concurrent accounting, uncertain writes, missing or corrupt ledger history, precision boundaries and retained holdout history.
Other included fixes
- Explicit model and dated-snapshot pricing replaces substring matching. Unknown or unsupported models earn no new credit; historical receipt verdicts remain unchanged.
- Optional SNP minting requires supported AMD identity and explicit image/TCB policy. Custom-root inspection cannot authorize minting. Optional SNP/PQC inputs are bounded, and dry-run results distinguish inspection from hardware policy.
- Request-ID reconciliation and TEE/TLSN identifiers preserve their evidence and duplicate-credit boundaries.
Upgrade guidance
Back up data and upgrade all writers sharing a directory together. Legacy or interrupted accounting may require explicit recovery using independently established debit records. Do not reconstruct missing spending as zero. Read the recovery guide before resuming a blocked ledger.
The signed v0.1.13 tag remains in history; no v0.1.13 GitHub assets or PyPI distributions were published.
Verification
The signed-tag release gate passed all 12 checks. Its initial suite and each of ten reproduction rounds recorded 2,901 passed / 18 optional skips; all ten lab, zero-loss concurrency and lease demonstrations passed.
- PR and main checks passed across Python 3.11–3.14; Windows recorded 2,877 passed / 42 platform or optional skips.
- Dedicated native cryptography jobs on Python 3.11 and 3.13 each recorded 238 passed with zero skips. LiteLLM integration recorded 8 passed with one existing upstream Pydantic warning.
- The JavaScript corpus passed all 402 cases. Vector regeneration preserved every corpus file byte for byte.
- This follow-up adds 100 regression cases without changing existing tests or historical vector verdicts. Package content and provenance are checked separately from the test results.
The three distribution/source archives carry GitHub build-provenance attestations. The separate release-verifier report records the workflow gate; it is not itself an attested archive. These tests establish the exercised implementation behavior, not provider payment settlement, savings veracity or independent adoption.