ContextLattice v3.20.1: Receipts Bound to the Release

The Utility Ledger was ready. Its paid installer authorization was not: the first v3.20.0-public-paid release correctly stopped before building or publishing assets because a legacy Frontier provenance record still identified the previous release train. ContextLattice v3.20.1 repairs that proof chain without weakening the gate or changing runtime behavior.

The CLI remains the primary interface. HTTP remains the integration fallback.

What changed

• Current paid release provenance now binds the active T3 Utility Ledger evidence, exact tested source, and proof commit.
• Historical T2 activation evidence remains independently verifiable from immutable hashes instead of depending on the mutable current-release provenance record.
• The commercial-truth audit now rejects a current T3 activation or provenance record that drifts from the canonical stable tag before a release is cut.
• The failed v3.20.0-public-paid release remains asset-free and is superseded by v3.20.1-public-paid.

What did not change

• Utility Ledger recording, verification, exact token accounting, analytics, advisory gates, durability, or rollback behavior.
• Public v3.20.0, which passed its release workflow; v3.20.1 carries the same runtime behavior plus the shared release-safety repair.
• Agent Packet deltas, proof timelines, session lifecycle, entitlement boundaries, quickstart requirements, or third-party agent installation policy.

Verification

The repair is proof and release tooling only. Focused commercial-truth regressions verify stale current provenance is rejected while historical T2 evidence remains valid. The exact paid candidate is re-audited against the private proof root, and the paid release workflow must pass before any installer asset is published.

Rollback

Use public v3.20.1 or paid v3.20.1-public-paid. The earlier paid tag intentionally has no installer assets.