STEP_034O_CHECKPOINT_PERSISTED_CANARY PASS_PERSISTED_CANARY_CHECKPOINT
timestamp: 20260708-123152

Snapshot:
- name: S034O_WGPAY_PERSISTED_CANARY_OK
- VM100 snapshot rc/visible: 0 / 0
- VM101 snapshot rc/visible: 0 / 0

Persisted canary:
- tunnel_ip: 10.253.1.10
- VM100 service/rule rc: 0 / 0
- VM100 persisted packets: 4
- VM101 service/pre/post/route rc: 0 / 0 / 0 / 0
- VM101 mark persisted packets: 4

VM121:
- peer_count: 21
- job_count: 37
- pending_job_count: 0
- canary_peer_enabled: True
- canary_tunnel_ip_matches: True
- canary_job_status: completed
- pg_dump_rc: 0
- endpoint_final_lines: 1
- backend_health_ok_lines: 2

Changes:
- snapshots VM100/VM101
- VM121 pg_dump backup only
- no policy switch
- no peer disable
- no WG/network/firewall reload
- no backend restart

Next:
- safe options:
  1. keep persisted canary active for this one WGPay peer and start planning production selector model;
  2. rollback persisted canary if you want a completely clean runtime before broader policy work.