Transactions hit DurabilityImpossibleException on a single node cluster with OOTB settings

As seen on https://forums.couchbase.com/t/receiving-a-transaction-operation-failed-exception-when-attempting-an-insert/30063, this remains a common sticking point, though we have tried to document it e.g. near the top of https://docs.couchbase.com/dotnet-sdk/current/howtos/distributed-acid-transactions-from-the-sdk.html.

I think we need to document the requirement for a rebalance if it's being changed on an existing bucket, for one.

After that, any thoughts on how we can make this more obvious?  It is negatively affecting the initial experience of so many developers using transactions.

Nb. there are plans to solve this on the server-side in the longer run, but better documentation would smooth the path until that point.