Two related LAN follow-ups deferred from Epic A2 (fn-144):
(a) auths pair --recover over LAN. Online recovery (auths pair --recover <did> --registry <url>) is implemented (SDK recover_device: pair replacement → revoke old, with safe ordering). The LAN path currently redirects to online recovery. Native LAN recovery needs the LAN initiator flow (lan.rs / common.rs::handle_pairing_response) to revoke-after-anchor.
(b) LAN-joiner delegation persistence. The LAN initiator anchors a joiner's dip (anchor_pairing_response), but relaying the anchoring ixn back to an external LAN joiner app (e.g. a phone) for its own local persistence needs the phone-app side plus an initiator→joiner confirmation channel in the daemon (today auths-pairing-daemon's confirmation flows joiner→initiator as an SAS ack).
Roadmap: docs/architecture/keri-only-roadmap.md. Delegation pairing landed in commit a5c85a5; recovery in fa26168.
Two related LAN follow-ups deferred from Epic A2 (fn-144):
(a)
auths pair --recoverover LAN. Online recovery (auths pair --recover <did> --registry <url>) is implemented (SDKrecover_device: pair replacement → revoke old, with safe ordering). The LAN path currently redirects to online recovery. Native LAN recovery needs the LAN initiator flow (lan.rs/common.rs::handle_pairing_response) to revoke-after-anchor.(b) LAN-joiner delegation persistence. The LAN initiator anchors a joiner's
dip(anchor_pairing_response), but relaying the anchoringixnback to an external LAN joiner app (e.g. a phone) for its own local persistence needs the phone-app side plus an initiator→joiner confirmation channel in the daemon (todayauths-pairing-daemon's confirmation flows joiner→initiator as an SAS ack).Roadmap:
docs/architecture/keri-only-roadmap.md. Delegation pairing landed in commit a5c85a5; recovery in fa26168.