Right. Most of the time you would simply retry the transaction - that's what FoundationDB's automatic transaction retry loop does. The first two tests I ran do that, but the third (foundationdb-append-noretry) does not.
That makes perfect sense. If it is the case, I think it's worth mentioning that the acknowledge write happened when the partition happened. I assumed that it happened when everything was going well, which is odd.
You don't want the database to report that a transaction was successful before the data is actually committed, or else you lose consistency. But if you wait until after the commit happens, there's a chance that the client might no longer be reachable. There's no way around this aside from waiting an indefinite period of time for the partition to be resolved.