Integration-branch tag with the record contract: EZI-2a and EZI-2b #489

Summary

Integration-branch tag with the record contract: EZI-2a and EZI-2b.

Behavior

EdgeZero keeps a protected integration branch for this work (DEC-5), and each integration point is a tag on it that Trusted Server main pins until EdgeZero releases the work. R1 creates the branch and tags #275 through #439, so Axum production serving does not wait for the record contract. R1b adds EZI-2a and EZI-2b. R2 adds the Fastly and Axum parts of EZI-1. R2b adds EZI-3, #90, #92, the JA4 accessor (#283) and Axum's geo binding (EZI-4a), so providers never wait on JA4. Together R1, R1b, R2 and R2b cover Fastly and Axum. R3 adds the Cloudflare parts of EZI-1 to EZI-4, and R4 the Spin parts. EZI-2p and EZI-5 follow the MVP (DEC-15).

Acceptance criteria

• Each tag exists on the protected integration branch and Trusted Server main pins it
• R1, R1b, R2 and R2b contain no Cloudflare or Spin part

Dependencies

Blocked by:

• KvStore record contract with listing strong within a partition #472 KvStore record contract with listing strong within a partition (new in this plan)
• DynamoDB and celld providers on Axum meet the record contract #473 DynamoDB and celld providers on Axum meet the record contract (new in this plan)

Blocks:

• One record backend over EdgeZero KvStore; delete the Fastly ec_kv.rs trusted-server#1587 One record backend over EdgeZero KvStore; delete the Fastly ec_kv.rs (new in this plan)

Related

• Needed by Server-side identity on every adapter trusted-server#1558, server-side identity on every adapter. Planned in wave 5 (MVP: Fastly and Axum); priority P1, size S.
• Requirement EZI-6 in the design.