docs: audit RPC server-control stubs

REDESIGN.md

@@ -922,9 +922,13 @@ ordering and error handling harder.
 
 Simple management and information calls should not become their own process.
 Examples include login-status queries, server description strings, server time,
-console-privilege checks, and small broadcast/control helpers.  These can be
-represented as a `servermgmt` provider for dispatch clarity, but they should stay
-in-process unless a specific call requires an existing backend service.
+console-privilege checks, and small broadcast/control helpers.  NetWare-4.x RPC
+server-control calls such as load/unload NLM, mount/dismount volume, SET command
+changes, and NCF execution also belong to this provider boundary, but they are
+not simple information calls and must remain disabled until there is a real
+privilege model and backend behavior.  These can be represented as a
+`servermgmt` provider for dispatch clarity, but they should stay in-process
+unless a specific call requires an existing backend service.
 
 ### Suggested provider map
 
@@ -937,7 +941,7 @@ queue          queue objects, jobs, queue servers, print queues, direct-spool br
 filesystem     file, directory, volume, namespace, trustee, salvage helpers
 semaphore      semaphore state and old 0x2222/32 calls
 message        station messaging and broadcast helpers
-servermgmt     small server-management and information calls
+servermgmt     server-management, information, and guarded RPC/control calls
 accounting     account status, charges, holds, notes
 AFP            AFP namespace and metadata helpers
 unknown        documented but not yet mapped