Regenerate API-INTERNAL.md for new write helpers

`npm run build:docs` output for the three new file-private helpers
introduced in the previous commit: persistMultiSetWrite,
persistCollectionWrite, persistMergedCollectionWrite.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: elirangoshen

API-INTERNAL.md

@@ -125,17 +125,33 @@ It will also mark deep nested objects that need to be entirely replaced during t
 Serves as core implementation for <code>Onyx.set()</code> public function, the difference being
 that this internal function allows passing an additional <code>retryAttempt</code> parameter to retry on failure.</p>
 </dd>
+<dt><a href="#persistMultiSetWrite">persistMultiSetWrite()</a></dt>
+<dd><p>Storage-write tail of multiSetWithRetry, isolated so that retryOperation re-enters only the
+storage step. Cache and subscriber notifications already happened in the orchestrator, so
+retries no longer re-fire <code>waitForCollectionCallback</code> subscribers with the same payload.</p>
+</dd>
 <dt><a href="#multiSetWithRetry">multiSetWithRetry(data, retryAttempt)</a></dt>
 <dd><p>Sets multiple keys and values.
 Serves as core implementation for <code>Onyx.multiSet()</code> public function, the difference being
 that this internal function allows passing an additional <code>retryAttempt</code> parameter to retry on failure.</p>
 </dd>
+<dt><a href="#persistCollectionWrite">persistCollectionWrite()</a></dt>
+<dd><p>Storage-write tail of setCollectionWithRetry, isolated so that retryOperation re-enters only the
+storage step. Cache and subscriber notifications already happened in the orchestrator, so
+retries no longer re-fire <code>waitForCollectionCallback</code> subscribers with the same payload.</p>
+</dd>
 <dt><a href="#setCollectionWithRetry">setCollectionWithRetry(params, retryAttempt)</a></dt>
 <dd><p>Sets a collection by replacing all existing collection members with new values.
 Any existing collection members not included in the new data will be removed.
 Serves as core implementation for <code>Onyx.setCollection()</code> public function, the difference being
 that this internal function allows passing an additional <code>retryAttempt</code> parameter to retry on failure.</p>
 </dd>
+<dt><a href="#persistMergedCollectionWrite">persistMergedCollectionWrite()</a></dt>
+<dd><p>Storage-write tail of mergeCollectionWithPatches, isolated so that retryOperation re-enters only
+the storage step. Cache and subscriber notifications already happened in the orchestrator, and
+the existing/new key split is captured in <code>params</code> — so retries don&#39;t re-fire subscribers and
+don&#39;t reclassify keys against a cache that was already mutated on the first attempt.</p>
+</dd>
 <dt><a href="#mergeCollectionWithPatches">mergeCollectionWithPatches(params, retryAttempt)</a></dt>
 <dd><p>Merges a collection based on their keys.
 Serves as core implementation for <code>Onyx.mergeCollection()</code> public function, the difference being
@@ -435,6 +451,14 @@ that this internal function allows passing an additional `retryAttempt` paramete
 | params.options | optional configuration object |
 | retryAttempt | retry attempt |
 
+<a name="persistMultiSetWrite"></a>
+
+## persistMultiSetWrite()
+Storage-write tail of multiSetWithRetry, isolated so that retryOperation re-enters only the
+storage step. Cache and subscriber notifications already happened in the orchestrator, so
+retries no longer re-fire `waitForCollectionCallback` subscribers with the same payload.
+
+**Kind**: global function  
 <a name="multiSetWithRetry"></a>
 
 ## multiSetWithRetry(data, retryAttempt)
@@ -449,6 +473,14 @@ that this internal function allows passing an additional `retryAttempt` paramete
 | data | object keyed by ONYXKEYS and the values to set |
 | retryAttempt | retry attempt |
 
+<a name="persistCollectionWrite"></a>
+
+## persistCollectionWrite()
+Storage-write tail of setCollectionWithRetry, isolated so that retryOperation re-enters only the
+storage step. Cache and subscriber notifications already happened in the orchestrator, so
+retries no longer re-fire `waitForCollectionCallback` subscribers with the same payload.
+
+**Kind**: global function  
 <a name="setCollectionWithRetry"></a>
 
 ## setCollectionWithRetry(params, retryAttempt)
@@ -466,6 +498,15 @@ that this internal function allows passing an additional `retryAttempt` paramete
 | params.collection | Object collection keyed by individual collection member keys and values |
 | retryAttempt | retry attempt |
 
+<a name="persistMergedCollectionWrite"></a>
+
+## persistMergedCollectionWrite()
+Storage-write tail of mergeCollectionWithPatches, isolated so that retryOperation re-enters only
+the storage step. Cache and subscriber notifications already happened in the orchestrator, and
+the existing/new key split is captured in `params` — so retries don't re-fire subscribers and
+don't reclassify keys against a cache that was already mutated on the first attempt.
+
+**Kind**: global function  
 <a name="mergeCollectionWithPatches"></a>
 
 ## mergeCollectionWithPatches(params, retryAttempt)