docs: credit @rine77 and @Wojak129 for the WIT atomicity fix (#331)

The v1.6.2 notes credited seven reporters and not @rine77, whose account of
what drove him to write an external proxy - 'locks and timeouts and no usable
shared connection' - is what located the defect. #331 was filed as a feature
request for behaviour that already existed; without that sentence it would have
been answered 'already supported' and closed.

He pointed it out himself, which is worse than noticing it. Fixed here and on
the published release.

Co-Authored-By: Claude <noreply@anthropic.com>

Author: 0xAHA

RELEASENOTES.md

@@ -70,7 +70,8 @@ Issues: #331, #375, #380
   six to eight registers, and a poll could previously land between them — leaving the
   inverter with control authority granted but no power setpoint, or a schedule with no
   period count. The sequence now holds the connection from first write to last, so it
-  either applies completely or fails without starting. (#331)
+  either applies completely or fails without starting. Reported by @Wojak129, and
+  diagnosed from @rine77's description of the symptom. (#331)
 - **Peak-shaving limits stay unavailable until they are configured.** On MOD and MID
   TL3-XH, Import Limit, Export Limit and AC Charge Max Power previously showed 3000 kW or
   6553.5 kW on systems where peak shaving had never been set up in the portal. An