4_11 needs more clarification

test 4_11 that is testing the update-update ordered feature variant (ii)

"The predecessor or successor of an inserted value is concurrently deleted"

**Example:**

User 2 inserts a new value B after A; this value, however, A has been concurrently deleted by user 1. Thus, a conflict is reported

This should be tightly coupled to successor, predecessor

**Problem:**

Since we using Json Pointer its not out of the box to get successor, predecessor, this has to a part comes from semantic information (?) or we have to split path from json pointer get the last elem if its index, compare added and deleted but with index+1 /-1 ... ... and all that kind of messy stuff

Start with test 4_11 for the update-update ordered feature variant (ii), then read the existing successor and predecessor handling. Clarify how JSON Pointer paths should identify adjacent values and define the expected conflict when the predecessor or successor is concurrently deleted; done means the test captures that decision and passes.

Written by the indexing model from the issue text.