@optimystic/db-p2p 1.0.0 → 1.2.0

package/src/repo/coordinator-repo.ts

@@ -337,6 +337,8 @@ interface LocalClusterWithExecutionTracking extends ICluster {
 	getExecutedPendResult?(messageHash: string): PendResult | undefined;
 	/** Local storage's verdict for a commit applied during consensus; see ClusterMember.getExecutedCommitResult. */
 	getExecutedCommitResult?(messageHash: string): CommitResult | undefined;
+	/** One more reconcile for a behind-refused commit, once remote members hold it; see ClusterMember.reconcileRefusedCommit. */
+	reconcileRefusedCommit?(record: ClusterRecord): Promise<void>;
 	/** Self-sign a one-peer commit proof for the solo-cohort commit path; see ClusterMember.mintSoloCommitProof.
 	 *  Optional like its siblings: absent on a bare ICluster double, and then the solo path simply
 	 *  commits proof-less — exactly the pre-mint behavior. */
@@ -600,7 +602,8 @@ export class CoordinatorRepo implements IRepo {
 			peerId: localPeerId,
 			wasTransactionExecuted: localCluster.wasTransactionExecuted?.bind(localCluster),
 			getExecutedPendResult: localCluster.getExecutedPendResult?.bind(localCluster),
-			getExecutedCommitResult: localCluster.getExecutedCommitResult?.bind(localCluster)
+			getExecutedCommitResult: localCluster.getExecutedCommitResult?.bind(localCluster),
+			reconcileRefusedCommit: localCluster.reconcileRefusedCommit?.bind(localCluster)
 		} : undefined;
 		this.coordinator = new ClusterCoordinator(keyNetwork, createClusterClient, policy, localClusterRef, fretService, reputation, stateStore);
 	}
@@ -2508,10 +2511,11 @@ export class CoordinatorRepo implements IRepo {
 			// fresh revision, which is what the `conflict: true` shape makes `Collection.syncAttempts`
 			// and the multi-collection `pendPhase` do. But a member reached only by
 			// `scheduleCommitRetry` can still land the refused revision later, and this node's own
-			// member (or its fallback commit) may hold it already. When the refused block is the
-			// action's LOG TAIL, that matters beyond this block: `NetworkTransactor.commit` stops at a
-			// refused tail and never sweeps the action's other blocks, so the writer can then read
-			// its own log entry back while none of the data it describes was committed anywhere.
+			// member (or its fallback commit) may hold it already. When the refused commit carries the
+			// action's LOG TAIL, that matters beyond this block: the writer can then read its own log
+			// entry back while the data it describes is on a minority at best — when the tail travelled
+			// with the other blocks, the members holding it may hold them too; when it travelled alone,
+			// `NetworkTransactor.commit` stops at the refused tail and never sweeps the rest.
 			// The writer's retry with the SAME action id is what converges that, and only because it
 			// does two things: `isOwnRevision` in `StorageRepo.pend` and `commit` treats an
 			// already-landed own revision as satisfied, and `Collection.completeOwnEntry` — on