docs: document TimeSync host time adapter policy

AI.md

@@ -685,4 +685,15 @@ Latest endpoint audit checkpoint from patch 0229:
   `nwnds` or `nwdirectory`.  Do not emulate the NDK remark that Set Server List
   returns success in all cases until a real TimeSync compatibility policy exists.
 
-Next patch number should be `0230`.
+Latest redesign checkpoint from patch 0230:
+
+- `REDESIGN.md` now records that the NetWare-4.x `0x2222/114` TimeSync provider
+  should be a host-time adapter, not a full NTP implementation.  mars-nwe should
+  rely on the host's configured time discipline such as ntpd, chrony, or
+  systemd-timesyncd and only translate local time/status into NetWare-compatible
+  NCP replies.
+- Do not make a new TimeSync process.  Keep it in the `servermgmt`/time-provider
+  boundary.  Do not let `114/06` Set Server List rewrite host NTP configuration
+  or return fake success without an explicit safe admin policy.
+
+Next patch number should be `0231`.

REDESIGN.md

@@ -931,6 +931,35 @@ 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.
 
+##### TimeSync should adapt host time discipline, not implement NTP
+
+The NetWare-4.x `0x2222/114` Time Synchronization compatibility provider should
+not grow into a full NTP implementation.  That would duplicate operating-system
+infrastructure and create a new time-discipline service inside mars-nwe.
+
+The preferred design is an adapter:
+
+```text
+NCP 114 TimeSync request
+  -> servermgmt/time provider
+  -> host system clock and configured time service
+     (ntpd, chrony, systemd-timesyncd, or local administrator policy)
+  -> NetWare-compatible TimeSync reply
+```
+
+For early compatibility, `114/01` Get Time can be backed by the local system
+clock.  Future `114/02` Exchange Time and server-list queries may report the
+configured local policy or host time-service status, but mars-nwe should not try
+to manage or reconfigure `ntpd`, chrony, or systemd-timesyncd at runtime.  In
+particular, `114/06` Set Server List should not be wired to fake success or to
+blindly rewrite host NTP configuration until there is an explicit, safe admin
+policy for that behavior.
+
+This keeps TimeSync in the `servermgmt` provider boundary and avoids adding a
+new process.  It also keeps the security model simple: the host remains
+responsible for disciplining time; mars-nwe only translates that state into the
+NetWare-compatible NCP surface.
+
 ### Suggested provider map
 
 The endpoint audit table should be able to use provider names like these: