0.5.213: adopt edge v25.2.0 / persist v44.7.0 — attribution self-refusal (#623) and the same-key rebind door (#864)

[emooreatx]

Adopts CIRISEdge v25.2.0 / CIRISPersist v44.7.0 (verify v15.2.0 unchanged) — the #602 update. Pins only; no server behaviour changes in this cut.

What the substrate brings

• CIRISEdge#623 — inbound attribution never resolves to this node's own key, and no responder is built for ourselves. The defence-in-depth half of RCA: the canonical serves ZERO anti-entropy rounds — prime_canonical_bootstrap_peers roots the canonical's OWN key, Branch-B attribution resolves every inbound link to self, the responder replies to itself (no route) — every agent times out #607; with 0.5.212's self-prime removal, both ends of that defect are now closed.
• CIRISPersist v44.7.0 (#864) — Engine::rebind_key_record / rebind_self_federation_key: a same-key rebind is an admission, so the holder of a pre-#659 {key_id}-only registration record can re-sign it bound; edge admits the replicated Rebound. This cut makes the door available. The server half — heal an unbound owner record at claim/boot from the owner's own seed — is Heal an unbound owner registration record at claim/boot through persist's same-key rebind door; name the peer on #425 refusal warns #606, next.

What this does NOT fix

The 0.5.212 canonical serves zero rounds with zero reply-to-self failures: a first-contact peer is dropped because edge's #402 bootstrap carve-out keys on the attribution result, which is None exactly when a fresh peer needs it (#609 / CIRISEdge#624). That is an edge fix; this pin does not include it. The traceflow ladder's served stage (0.5.212) is the in-repo probe; it passes in the harness because the harness canonical admits the agent's announce before the agent dials.

Verification

• cargo tree -i: one copy each of persist v44.7.0, edge v25.2.0, verify v15.2.0.
• Substrate contract gate, replication policy gate, anchor-block gate: green (no ratified hash moved in v44.7.0).
• 127-binary sweep green; lib 531; clippy --all-targets; localization guard.
• Ladders: see the checklist comment.

🤖 Generated with Claude Code

https://claude.ai/code/session_01SZcY9yx3JZ8YqkqtFq1TQw

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[emooreatx]

Local verification on the v25.2.0 / v44.7.0 wheel

• 127-binary sweep green, lib 531, clippy --all-targets, localization guard; substrate contract / replication policy / anchor-block gates green (no hash moved).
• Traceflow: SUCCESS incl. the served stage (harness canonical logs not priming itself, serves the agent's rounds).
• Chat: first local run BROKEN AT sent (the joiner's KeyPackage took ~60 s to reach the creator while this box was compiling); rerun SUCCESS, cross-node chat proven. CI's chat ladder on this PR is green on an idle runner. Reading it as a load flake, not a v25.2.0 regression; noting the propagation time in case it recurs.