protocol: remove "testing phase" disclaimers

We don't break window managers.

 README.md                               | 12 +++---------
 protocol/river-input-management-v1.xml  |  5 -----
 protocol/river-layer-shell-v1.xml       |  5 -----
 protocol/river-libinput-config-v1.xml   |  5 -----
 protocol/river-window-management-v1.xml |  5 -----
 protocol/river-xkb-bindings-v1.xml      |  5 -----
 protocol/river-xkb-config-v1.xml        |  5 -----
 7 files changed, 3 insertions(+), 39 deletions(-)

diff --git a/README.md b/README.md
index b46fd2d..5645a81 100644
--- a/README.md
+++ b/README.md
@@ -65,15 +65,9 @@ with writing Wayland clients should need, I'd like to add some more
 beginner-friendly documentation including a well-commented example window
 manager before the 0.4.0 release.
 
-I would also like to get more feedback on the
-[river-window-management-v1](protocol/river-window-management-v1.xml) protocol
-before the 0.4.0 release. If you are working on a window manager and have
-questions/feedback I'd love to hear from you!
-
-With regards to protocol stability, my goal is to never make a backwards
-incompatible change and stay at `v1` forever. I've been iterating on this
-protocol since April 2023 and am quite confident in the design and extensibility
-of the current protocol.
+The [river-window-management-v1](protocol/river-window-management-v1.xml)
+protocol and other river protocol extensions are stable.
+We don't break window managers.
 
 If everything goes well with the 0.4.0 release, I expect the following
 non-bugfix release to be river 1.0.0. After river 1.0.0, all backwards
diff --git a/protocol/river-input-management-v1.xml b/protocol/river-input-management-v1.xml
index 05bcd34..e7cc777 100644
--- a/protocol/river-input-management-v1.xml
+++ b/protocol/river-input-management-v1.xml
@@ -30,11 +30,6 @@
     The key words "must", "must not", "required", "shall", "shall not",
     "should", "should not", "recommended", "may", and "optional" in this
     document are to be interpreted as described in IETF RFC 2119.
-
-    Warning! The protocol described in this file is currently in the testing
-    phase. Backward compatible changes may be added together with the
-    corresponding interface version bump. Backward incompatible changes can only
-    be done by creating a new major version of the extension.
   </description>
 
   <interface name="river_input_manager_v1" version="1">
diff --git a/protocol/river-layer-shell-v1.xml b/protocol/river-layer-shell-v1.xml
index 0a9a437..b6cf41b 100644
--- a/protocol/river-layer-shell-v1.xml
+++ b/protocol/river-layer-shell-v1.xml
@@ -30,11 +30,6 @@
     The key words "must", "must not", "required", "shall", "shall not",
     "should", "should not", "recommended", "may", and "optional" in this
     document are to be interpreted as described in IETF RFC 2119.
-
-    Warning! The protocol described in this file is currently in the testing
-    phase. Backward compatible changes may be added together with the
-    corresponding interface version bump. Backward incompatible changes can only
-    be done by creating a new major version of the extension.
   </description>
 
   <interface name="river_layer_shell_v1" version="1">
diff --git a/protocol/river-libinput-config-v1.xml b/protocol/river-libinput-config-v1.xml
index fc7b75d..69e23c0 100644
--- a/protocol/river-libinput-config-v1.xml
+++ b/protocol/river-libinput-config-v1.xml
@@ -41,11 +41,6 @@
     The key words "must", "must not", "required", "shall", "shall not",
     "should", "should not", "recommended", "may", and "optional" in this
     document are to be interpreted as described in IETF RFC 2119.
-
-    Warning! The protocol described in this file is currently in the testing
-    phase. Backward compatible changes may be added together with the
-    corresponding interface version bump. Backward incompatible changes can only
-    be done by creating a new major version of the extension.
   </description>
 
   <interface name="river_libinput_config_v1" version="1">
diff --git a/protocol/river-window-management-v1.xml b/protocol/river-window-management-v1.xml
index db170d4..a39ab79 100644
--- a/protocol/river-window-management-v1.xml
+++ b/protocol/river-window-management-v1.xml
@@ -32,11 +32,6 @@
     The key words "must", "must not", "required", "shall", "shall not",
     "should", "should not", "recommended", "may", and "optional" in this
     document are to be interpreted as described in IETF RFC 2119.
-
-    Warning! The protocol described in this file is currently in the testing
-    phase. Backward compatible changes may be added together with the
-    corresponding interface version bump. Backward incompatible changes can only
-    be done by creating a new major version of the extension.
   </description>
 
   <interface name="river_window_manager_v1" version="3">
diff --git a/protocol/river-xkb-bindings-v1.xml b/protocol/river-xkb-bindings-v1.xml
index 041b1bd..a83c5f5 100644
--- a/protocol/river-xkb-bindings-v1.xml
+++ b/protocol/river-xkb-bindings-v1.xml
@@ -31,11 +31,6 @@
     The key words "must", "must not", "required", "shall", "shall not",
     "should", "should not", "recommended", "may", and "optional" in this
     document are to be interpreted as described in IETF RFC 2119.
-
-    Warning! The protocol described in this file is currently in the testing
-    phase. Backward compatible changes may be added together with the
-    corresponding interface version bump. Backward incompatible changes can only
-    be done by creating a new major version of the extension.
   </description>
 
   <interface name="river_xkb_bindings_v1" version="2">
diff --git a/protocol/river-xkb-config-v1.xml b/protocol/river-xkb-config-v1.xml
index 4b8ae16..d44d141 100644
--- a/protocol/river-xkb-config-v1.xml
+++ b/protocol/river-xkb-config-v1.xml
@@ -31,11 +31,6 @@
     The key words "must", "must not", "required", "shall", "shall not",
     "should", "should not", "recommended", "may", and "optional" in this
     document are to be interpreted as described in IETF RFC 2119.
-
-    Warning! The protocol described in this file is currently in the testing
-    phase. Backward compatible changes may be added together with the
-    corresponding interface version bump. Backward incompatible changes can only
-    be done by creating a new major version of the extension.
   </description>
 
   <interface name="river_xkb_config_v1" version="1">