fix: CP13-5 doc — remove stale CatchingUp transition claim

Replace "observable CatchingUp state transition" with the actual 3
signals the test asserts: seeded hasFlushedProgress, receivedLSN
advance, non-zero replicaFlushedLSN.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
pingqiu
2026-04-02 22:59:44 -07:00
co-authored by Claude Opus 4.6
parent 4681df6b56
commit 20a1a4995c
@@ -52,7 +52,7 @@ SyncCache → groupCommit.Submit → Barrier(lsnMax)
| Test | Was | Now | Why |
|------|-----|-----|-----|
| `TestAdversarial_ReconnectUsesHandshakeNotBootstrap` | FAIL | PASS | Seeded hasFlushedProgress + observable CatchingUp state transition proves handshake path used |
| `TestAdversarial_ReconnectUsesHandshakeNotBootstrap` | FAIL | PASS | 3 observable signals: seeded hasFlushedProgress, receivedLSN advance, non-zero replicaFlushedLSN |
| `TestAdversarial_CatchupMultipleDisconnects` | FAIL | PASS | Repeated SetReplicaAddrs preserves progress seed |
| `TestAdversarial_CatchupDoesNotOverwriteNewerData` | FAIL | PASS | Catch-up now completes, safety invariant exercised |