Repair a branch address and DHCP plan

Edit branch-address-plan.json. The branch owns 10.44.8.0/23. Preserve the existing management block 10.44.8.224/27; it is a read-only allocation and should not appear as a new segment. Plan exactly staff for 100 DHCP clients, voice for 45 DHCP clients, and cameras for 25 DHCP clients. These are ordinary multi-access IPv4 LANs: reserve network and broadcast addresses, and reserve one usable address for each gateway. Give each LAN the smallest CIDR block that fits all its clients plus the gateway. Choose canonical network addresses and keep all new blocks inside the branch delegation, disjoint from each other and management. A gateway may be any usable address in its LAN. Set one contiguous DHCP range per LAN with enough addresses for every required client, excluding the gateway, network and broadcast addresses. Advertise one summaryRoute covering all three new LANs and the retained management LAN without claiming space outside 10.44.8.0/23. Unallocated space inside the delegation may be covered by the summary. Use segments as an array of records with id, cidr, gateway, dhcpStart and dhcpEnd, plus summaryRoute as an IPv4 CIDR string. Different valid block placements and gateway positions are acceptable. Run the independent checks after each edit and repair failures without Reset.