CHA-RL5f1-3: remove as copies of CHA-RL1e

textile/chat-features.textile

@@ -131,10 +131,7 @@ h4(#rooms-lifecycle-operations). Room Lifecycle Operations
 ** @(CHA-RL5c)@ @[Testable]@ If the operation above fails (i.e. the call to the @CHA-RL2f@ detach procedure fails), such that the room enters the @FAILED@ state, then the retry loop must stop.
 ** @(CHA-RL5d)@ Once all channels (except the channel that entered @SUSPENDED@, per @CHA-RL5a@) have been detached, the room waits until the original channel that caused the retry loop naturally enters the @ATTACHED@ state. This is handled by the underlying Realtime SDK.
 ** @(CHA-RL5e)@ @[Testable]@ If, during the @CHA-RL5d wait, the channel state becomes @FAILED@, then the room status is transitioned to @FAILED@ and the retry loop stops. The error associated with the transition is the error from the Realtime @ChannelStateChange@.
-** @(CHA-RL5f)@ @[Testable]@ If, during the @CHA-RL5d wait, the channel state becomes @ATTACHED@, then the room status is transitioned to @ATTACHING@ to begin a new @CHA-RL1e@ attachment cycle.
-*** @(CHA-RL5f1)@ @[Testable]@ If the attachment cycle succeeds, then the room is transitioned to @ATTACHED@ and any discontinuity errors are broadcast to contributors. These are then cleared to prevent double-notification. The retry loop now terminates.
-*** @(CHA-RL5f2)@ @[Testable]@ If the attachment cycle fails because a channel entered @FAILED@, then the room is transitioned to @FAILED@ and the retry loop terminates. The error associated with the transition is the error from the Realtime @ChannelStateChange@. A @CHA-RL1h5@ detachment of non-failed channels is performed.
-*** @(CHA-RL5f3)@ @[Testable]@ If the attachment cycle fails because a channel entered @SUSPENDED@, then the room is transitioned to @SUSPENDED@ and the retry loop restarted using the @SUSPENDED@ channel as the subject. The error associated with the transition is the error from the Realtime @ChannelStateChange@.
+** @(CHA-RL5f)@ @[Testable]@ If, during the @CHA-RL5d wait, the channel state becomes @ATTACHED@, then the room status is transitioned to @ATTACHING@ to begin a new @CHA-RL1e@ attachment cycle. On successful completion, or terminal condition (room status is @FAILED@) the @RETRY@ loop terminates.
 * @(CHA-RL6)@ @[Testable]@ A room begins its lifetime in the @INTIIALIZING@ state.
 * @(CHA-RL6a)@ @[Testable]@ It enters @INITIALIZED@ when any @RELEASE@ operations for a previous instance of a room are completed.
 * @(CHA-RL7)@ Room lifecycle operations are atomic and exclusive operations: one operation must complete (whether that's failure or success) before the next one may begin.