Add full monorepo: virtual-banker, backend, frontend, docs, scripts, deployment

Co-authored-by: Cursor <cursoragent@cursor.com>

IP_CONFLICT_RESOLVED.md

@@ -0,0 +1,51 @@
+# IP Conflict Resolution - Complete
+
+**Date**: 2026-01-21  
+**Status**: ✅ **IP CONFLICT RESOLVED**
+
+---
+
+## Resolution Summary
+
+### Before Fix
+- **VMID 10233** (npmplus) on r630-01: 192.168.11.167
+- **VMID 10234** (npmplus-secondary) on r630-02: 192.168.11.167 ⚠️ **CONFLICT**
+
+### After Fix
+- **VMID 10233** (npmplus) on r630-01: 192.168.11.167 ✅
+- **VMID 10234** (npmplus-secondary) on r630-02: 192.168.11.168 ✅
+
+---
+
+## Verification
+
+### IP Address Verification
+- ✅ 192.168.11.168 confirmed unused before reassignment
+- ✅ VMID 10234 successfully reassigned to 192.168.11.168
+- ✅ No remaining conflicts for 192.168.11.167
+
+### Expected Results
+- UDM Pro should now see correct MAC (BC:24:11:A8:C1:5D) for 192.168.11.167
+- Traffic should route correctly to VMID 10233 (npmplus)
+- No more ARP conflicts
+
+---
+
+## Next Steps
+
+1. **Verify UDM Pro Client List**
+   - Check that 192.168.11.167 shows correct MAC (BC:24:11:A8:C1:5D)
+   - Verify 192.168.11.168 appears as new client
+
+2. **Test NPMplus Connectivity**
+   - Test access to 192.168.11.167:80
+   - Verify NPMplus dashboard works
+   - Test external access to explorer.d-bis.org
+
+3. **Update UDM Pro Firewall Rules** (if needed)
+   - Ensure firewall rules target correct IP/MAC
+   - Verify outbound access works
+
+---
+
+**Status**: ✅ **CONFLICT RESOLVED - VERIFICATION IN PROGRESS**