HydraCache 0.52.0

HydraCache 0.52.0

0.52.0 adds the IMap plus Fenced Lock Java surface. It promotes the existing
single-key conditional/fenced-lock engine into a supported migration surface:
lease-bound ownership, reentrancy, lock wire operations, Java facade contracts,
IMap compare-and-set ergonomics, entry listeners, and simulator safety checks.

The release surfaces what the engine can prove. It does not add a general CP
subsystem, cross-region locks, remote code execution, or distributed
transactions.

Highlights

• Added lock lease semantics, session-bound ownership, logical-time expiry, and
  auto-release behavior.
• Added reentrant lock ownership and owner identity checks in the single-key
  lock model.
• Added lock operations to the versioned external client protocol, including
  acquire, unlock, renew, force-unlock, ownership, CAS, and listener operations.
• Added server endpoint coverage for the lock protocol path.
• Added Java migration contracts for Hazelcast-shaped FencedLock and
  IMap.lock behavior, including the supported subset and unsupported
  boundaries.
• Added IMap CAS ergonomics: replace-if-value and remove-if-value.
• Added IMap entry-listener projection over the invalidation bus, explicitly as
  cache signals rather than a business event log.
• Added deterministic simulator checks for lock safety under partition, expiry,
  contention, fence monotonicity, and stale-holder rejection.

Verification

Focused gates:

cargo test -p hydracache --locked lock_lease
cargo test -p hydracache --locked lock_reentrancy
cargo test -p hydracache-client-protocol --locked lock_wire
cargo test -p hydracache-server --locked lock_endpoint
cargo test -p hydracache-client-protocol --locked java_migration_contract
cargo test -p hydracache-client-protocol --locked java_lock_mapping
cargo test -p hydracache-client-protocol --locked imap_cas
cargo test -p hydracache-client-protocol --locked imap_entry_listener
cargo test -p hydracache-sim --locked lock_safety_sim

Full gate:

cargo xtask verify

Scope Boundary

Locks are single-key, fenced, leased, and session-bound. Weak consistency levels
do not serve lock/CAS operations. Entry listeners remain cache-event
projections, not durable business-event logs.

Release Status

Published as 0.52.0 after the lock, wire-protocol, Java contract, and DST
safety gates.