dsh-remote-bridge 2.2.2 → 2.2.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/docs/api/asyncapi.yaml +38 -3
- package/docs/api/openapi.yaml +1 -1
- package/lib/index.d.ts +973 -859
- package/lib/index.js +332 -28
- package/package.json +1 -1
package/docs/api/asyncapi.yaml
CHANGED
|
@@ -1,8 +1,15 @@
|
|
|
1
1
|
asyncapi: 3.0.0
|
|
2
2
|
info:
|
|
3
3
|
title: DeepSeek Harness Mobile Events
|
|
4
|
-
version: 2.2.
|
|
5
|
-
description:
|
|
4
|
+
version: 2.2.4
|
|
5
|
+
description: |
|
|
6
|
+
Live file and authorized DSH chat events. Reconnect clients must refresh
|
|
7
|
+
REST state; unbounded replay is not provided.
|
|
8
|
+
|
|
9
|
+
`chat.turn.failed` carries the terminal failure of a model turn (rate
|
|
10
|
+
limit, quota exhausted, invalid API key, signed-out stop). Without it a
|
|
11
|
+
remote client sees an ordinary `chat.turn.end` and keeps waiting on a run
|
|
12
|
+
that already failed.
|
|
6
13
|
servers:
|
|
7
14
|
local:
|
|
8
15
|
host: 127.0.0.1:3090
|
|
@@ -32,7 +39,7 @@ components:
|
|
|
32
39
|
id: { type: string }
|
|
33
40
|
type:
|
|
34
41
|
type: string
|
|
35
|
-
examples: [file.changed, file.trashed, chat.message.delta, chat.message.committed, chat.session.status, chat.approval.requested, chat.approval.resolved, connection.ready]
|
|
42
|
+
examples: [file.changed, file.trashed, chat.message.delta, chat.message.committed, chat.session.status, chat.approval.requested, chat.approval.resolved, chat.turn.failed, connection.ready]
|
|
36
43
|
time: { type: integer }
|
|
37
44
|
data:
|
|
38
45
|
oneOf:
|
|
@@ -40,6 +47,7 @@ components:
|
|
|
40
47
|
- $ref: '#/components/schemas/ChatMessageCommitted'
|
|
41
48
|
- $ref: '#/components/schemas/ChatApprovalRequested'
|
|
42
49
|
- $ref: '#/components/schemas/ChatApprovalResolved'
|
|
50
|
+
- $ref: '#/components/schemas/ChatTurnFailed'
|
|
43
51
|
- type: object
|
|
44
52
|
additionalProperties: true
|
|
45
53
|
schemas:
|
|
@@ -84,3 +92,30 @@ components:
|
|
|
84
92
|
sessionId: { type: string }
|
|
85
93
|
approvalId: { type: string }
|
|
86
94
|
outcome: { type: string, enum: [allowed-once, rejected, cancelled, unavailable] }
|
|
95
|
+
ChatTurnFailed:
|
|
96
|
+
type: object
|
|
97
|
+
description: |
|
|
98
|
+
Terminal failure of a model turn. Emitted instead of a plain
|
|
99
|
+
`chat.turn.end` when the host reports `reason.kind === 'error'` (rate
|
|
100
|
+
limit, quota exhausted, invalid key) or an abort caused by signing out
|
|
101
|
+
of the DeepSeek account. Clients must stop their running indicator and
|
|
102
|
+
show the message; otherwise a failed run keeps looking like it is in
|
|
103
|
+
flight.
|
|
104
|
+
required: [sessionId, eventType, failure]
|
|
105
|
+
properties:
|
|
106
|
+
sessionId: { type: string }
|
|
107
|
+
eventType: { type: string, const: turn/end }
|
|
108
|
+
seq: { type: integer }
|
|
109
|
+
failure:
|
|
110
|
+
type: object
|
|
111
|
+
description: |
|
|
112
|
+
`message` is the host's own wording, forwarded verbatim so clients
|
|
113
|
+
can decide localization. `code` is present only when the host
|
|
114
|
+
supplies one; an empty string is meaningful and must not be
|
|
115
|
+
treated as absent. `stopped` marks an account-sign-out stop, which
|
|
116
|
+
is not a model fault.
|
|
117
|
+
required: [message]
|
|
118
|
+
properties:
|
|
119
|
+
message: { type: string }
|
|
120
|
+
code: { type: string }
|
|
121
|
+
stopped: { type: boolean, const: true }
|
package/docs/api/openapi.yaml
CHANGED