keep-web: hardening & test-coverage backlog (1 items)

[kwsantiago]

Backlog of hardening / test-coverage findings in keep-web, verified still-open against current code by an automated triage pass. Each is an independent, pickup-able task — pick one and open a PR.

Findings

• wall-clock created_at can freeze keep-state replication (clock regression / future-dating) — The permanent-freeze core is mitigated by consumer future-bound keep-state: bound consumer-side created_at so a future-dated event cannot permanently poison a record's rollback mark #708/keep-state: bound consumer created_at to prevent permanent mark-poisoning (#708) #709 and floor-seeding keep-web state replication: handle relay created_at rejection and bound future-dated timestamps #704/keep-state: surface relay created_at rejection instead of silent replication loss (#704) #706, but the tracked residual (a persistent-divergence alert/escalation when applied==false repeats) remains unimplemented in keep-web/src/state_replication.rs.

Grouped from individual tracked items; close each checkbox as its PR merges.