docs: audit async synchronization stubs

AI.md

@@ -1220,4 +1220,23 @@ Next patch number should be `0253`.
 - This is synchronization/lock-provider state, not server-management or
   directory state.
 
-Next patch number should be `0258`.
+## 2026-06-02 - Patch 0258 async synchronization direct stubs 105/107/108/109
+
+- Continued NDK-first after Clear Lock Wait Node with the missing direct
+  asynchronous synchronization endpoints in `src/nwconn.c`:
+  - `105` / wire `0x69` Log File (old)
+  - `107` / wire `0x6b` Log Logical Record
+  - `108` / wire `0x6c` Lock Logical Record Set
+  - `109` / wire `0x6d` Log Physical Record
+- These are NetWare-3.x/4.x-relevant endpoints.  The NDK also lists 5.x, but
+  this audit keeps only the 3.x/4.x contract.
+- Patch `0258` adds disabled source stubs only.  Runtime behavior is unchanged.
+- Do not map these direct async-capable calls onto the existing old
+  synchronous handlers (`03`, `09`, `10`, `26`) or namespace handlers
+  (`87/36`, `87/67`) without a real provider design.  The request encodings and
+  async wait-node semantics differ.
+- These calls share state requirements with `112` Clear Lock Wait Node: pending
+  lock allocation, async wait-node lifetime, and correct completion-code
+  mapping.
+
+Next patch number should be `0259`.