[ChristianPavilonis]

Summary

Extract the existing demo's conditional/physical celld record operations as a separate review unit. This is a mechanical replay of 5ab90e68a08580ee34ae143f59cb02eaff4b0974, not new storage design.

Base: #422, feat/native-celld-stores at 0d17257fd7c8991f78a28cadbca309160521601c.

Head: b18a44d0a63790e8a16fe14737afa0a2053a5f5b. Refs #461; integration checkpoint #462.

Retained changes

Ten existing paths add explicit record capability/settings, conditional Add/CAS, generation and physical-record reads, expiry/deletion behavior, tests and documentation. Ordinary KV does not become CAS or an identity-allocation guarantee. These operations are separate from the native config/KV provider installation in #422.

Checks and limits

The entire edgezero-store-celld source tree is byte-identical to the previously tested extraction. Reusable proof: 56 all-feature unit/TCP cases, strict scoped Clippy and formatting, and one explicitly executed real conditional-record interop case against the matching celld service. No service or cloud check was rerun merely to change ancestry.

The retained real interop was a disposable loopback check with a verified reused service binary, not an independent rebuild or fleet durability qualification. The expiry fixture's no-sweep setting was only for held physical-expiry proof. No cloud, production identity-allocation, multi-node consistency or deployment acceptance is claimed.

Keep draft. Combined integration checks and fresh hosted checks are reported by #462; a historical passing receipt is not a claim that every new-head check passed.

[aram356]

CREATOR: From the server-side identity plan (IABTechLab/trusted-server#1559, c7dc9de77): Rebase as Part A's table says.

Part of #473

[ChristianPavilonis]

Superseded by #422, which now includes these conditional and physical record operations.