feat(protocol): add relaunch operation response

openapi/control-v1.yaml

@@ -308,6 +308,20 @@ paths:
             application/json:
               schema:
                 $ref: ../schemas/control-v1.schema.json#/$defs/ConnectionManifest
+        '202':
+          description: >-
+            Confirmed over-cap reconnect creates or returns a durable `session.display_relaunch` termination operation.
+            Under the session and unique Stop lock, the Server MUST create at most one display-relaunch operation per session;
+            a same-owner/device lost-response retry MUST return that same operation. It reuses the existing one-way non-reissued
+            Stop work/ack path. An existing user Stop in any state MUST win and yield a stable non-202 result; it MUST NOT be reinterpreted as display-relaunch authority. This response is not a manifest,
+            does not assert termination completion, and does not authorize a replacement session before `applied`.
+            After `applied`, the client submits a fresh `SessionRequest` with a new idempotency key.
+            Failed or `termination_unconfirmed` outcomes never auto-relaunch. Local Stop or teardown MUST suppress the fresh launch.
+            Maximum JSON body: 16384 bytes.
+          content:
+            application/json:
+              schema:
+                $ref: ../schemas/control-v1.schema.json#/$defs/StopOperation
         '400': {$ref: '#/components/responses/InvalidRequest'}
         '401': {$ref: '#/components/responses/Unauthorized'}
         '404': {$ref: '#/components/responses/NotFound'}