Couch has always been good at this use case where systems on both ends may have changed in the disconnect time.
We use transactions under the hood actually writing data to indexeddb
I fully admit I'm not very well-versed on databases or distributed computing, happy to have things clarified.
1. Additional (p2p) use cases, honestly I dont use CouchDB much these days, I use express-pouchdb-server so I can embed pouchdb into my server easier than any other database, there is also pouchdb-server and p2p projects like Thali (http://thaliproject.org/)
2. CouchDB existed, sync is super hard, writing an edge client would have meant designing it myself, writing a couchdb clone meant I needed to make a lot less decisions about how it worked while being very confident it would work, The test suite runs the same tests against pouchdb/couchdb to ensure compatibility (and replication via each configuration)