Cleanud up

docs/USER-GUIDE.md

@@ -1,6 +1,10 @@
 # atMb usage and behavior
 
-This guide describes the supplied working export, including its renamed `ClientTCP`. The documented export changes comments only and retains the embedded C Implemented Library object. Import with replacement of matching objects into your existing library project. No C rebuild is needed for these documentation changes.
+This guide describes the last supplied working IEC export, including `ClientTCP`.
+The current repository stores the working file at `library/CmpAtomModbus.library`.
+Use that file in CODESYS. No IEC or C implementation is changed by repository cleanup.
+The binary library format was not decoded to reverify its member declarations;
+when changing IEC code, update this guide against a fresh CODESYS export.
 
 ## Choosing the block
 
@@ -211,6 +215,6 @@ States: 0 disabled, 1 retry wait, 2 connecting, 3 ready, 4 sending, 5 receiving.
 
 ## Maintenance and scope
 
-The documented export preserves the working implementations, metadata and embedded payloads. Internal native fields are sometimes exposed as VAR_INPUT for compatibility; leave them under library control. Several legacy BOOL methods do not assign a return value; the API reference identifies them so callers rely on their side effects.
+The cleanup preserves the supplied working library and standalone native binary. Internal native fields are sometimes exposed as VAR_INPUT for compatibility; leave them under library control. Several legacy BOOL methods do not assign a return value; the API reference identifies them so callers rely on their side effects.
 
 Lifecycle hooks exist, but reliable online-change ownership and pointer relocation remain future work. Documentation adds no behavior changes or online-change guarantee. Use the API reference for every method/property, including internal accessors.