Repair route failover across the branch and backup routers

Edit route-plan.json using exactly routes, a list of at most 64 static route records. Each record has id, router, destination, nextHop and distance. Ids must be unique, trimmed strings of 1..80 characters. Router is branch, core or backup. Destination is a canonical IPv4 CIDR; use /32 for a host. NextHop is an adjacent peer's complete dotted-decimal address, or null for a local discard. Distance is an integer from 1 to 254. A route through an adjacent peer is eligible only while that local link is up; it does not detect a remote failure. For the same exact destination prefix, the lowest eligible distance is installed. Equal winning distances with different actions or peers fail the unique-choice requirement. Connected routes participate at distance 0. Different prefixes can coexist, and forwarding uses the longest matching installed prefix regardless of distance on less-specific routes. Repair complete forward and return LAN prefix coverage in all three phases, preserve the required normal direct paths, remove every forwarding loop and keep unowned guarded addresses local. Checks prove complete CIDR match ranges, including interior host routes and both prefix endpoints; they do not assert that network or broadcast addresses are usable hosts. You may float matching prefixes or use safe aggregates with more-specific critical routes. An aggregate must not forward unowned space; a more-specific route overrides a broader discard. Run tests, follow the destination range and router path in the failure evidence, and repair the saved plan without Reset.