MSM Access Perumahan v1.4 - ACB Vendor SDK Cross-check

The supplied ACB-001/002/004 SDK source was used to confirm application semantics:

Vendor SDK concept                         MSM v1.4 equivalent
--------------------------------------------------------------------------
wgMjController.SearchControlers           Native UDP controller discovery
wgMjController.GetMjControllerRunInformationIP
                                           Native live status/event 0x20
wgWatchingService / EventHandler           MSM live monitor + event catch-up
wgMjControllerPrivilege.AddPrivilegeOfOneCardIP
                                           Upload/update one card + read-back verify
wgMjControllerPrivilege.DelPrivilegeOfOneCardIP
                                           Master-only deactivate/delete + verify
wgMjControllerPrivilege.DownloadIP         Full card download / board backup
MjRegisterCard.CardID                      Card ID / UHF credential
MjRegisterCard.Password                    PIN
MjRegisterCard.ymdStart / ymdEnd           Active from / active until
ControlSegIndexSet(1..4)                   Door access values 1..4
wgMjController.RemoteOpenDoorIP            Reserved for a later verified gate-control module

Runtime design:
- The production EXE does NOT require N3000.
- The production EXE does NOT require the vendor .NET DLL at runtime.
- The proven native UDP protocol driver is kept as the runtime engine so the package remains portable and standalone.
- Vendor SDK semantics are used to cross-check CRUD, privilege fields and live monitoring behavior.

Safety:
- Mass clear privilege is intentionally not exposed.
- Restore checks controller serial number and makes a pre-restore board backup.
- Single-card delete creates a card backup and verifies the card is no longer readable.
- Upload/update requires read-back verification.
