@owlmeans/socket 0.1.18-rc.29 → 0.1.18-rc.30

package/README.md

@@ -12,7 +12,7 @@ Shared WebSocket connection types and message protocol for OwlMeans real-time co
 ## Installation
 
 ```bash
-bun add @owlmeans/socket@^0.1.18-rc.28
+bun add @owlmeans/socket@^0.1.18-rc.30
 ```
 
 ## Usage
@@ -91,7 +91,7 @@ This package ships embedded agent skills under `agent-meta/`. After installing y
 your project's skill store (`.agents/skills/`):
 
 ```sh
-npx @owlmeans/agent-skills@^0.1.18-rc.33
+npx @owlmeans/agent-skills@^0.1.18-rc.34
 ```
 
 The embedded files are version-matched to this package release. Do not edit them

package/agent-meta/manifest.json

@@ -1,8 +1,8 @@
 {
   "schemaVersion": 2,
   "package": "@owlmeans/socket",
-  "version": "0.1.18-rc.29",
-  "generatedAt": "2026-09-22T17:39:02.523Z",
+  "version": "0.1.18-rc.30",
+  "generatedAt": "2026-09-22T20:45:24.053Z",
   "canonicalRepo": "https://github.com/owlmeans/common",
   "entries": [
     {

package/agent-meta/skills/socket/SKILL.md

@@ -8,7 +8,7 @@ user-invocable: false
 # @owlmeans/socket
 
 **Layer:** Core
-**Install:** `"@owlmeans/socket": "^0.1.18-rc.29"` in `dependencies`
+**Install:** `"@owlmeans/socket": "^0.1.18-rc.30"` in `dependencies`
 
 Contracts and one implementation-free connection model. It knows nothing about WebSockets: the
 browser side is `@owlmeans/client-socket`, the Fastify side `@owlmeans/server-socket`, and each
@@ -91,12 +91,12 @@ subscription a handler opened is released there.
 | `disconnected` | The socket dropped and a retry IS scheduled (client-socket only) — `{ code }` |
 | `reconnecting` | Before each retry attempt (client-socket only) — `{ attempt, delay }` |
 | `reconnected` | A retry succeeded, same `Connection` model (client-socket only) — `{ attempts }` |
-| `lost` | The retry budget elapsed with no success, immediately followed by `close` (client-socket only) |
+| `lost` | The retry budget elapsed with no success (client-socket only). NOT followed by `close`: the connection stays revivable until its owner closes it |
 
 `close` is the only one of the five a plain carrier with no retry logic (like `server-socket`, or
-`client-socket` itself with `reconnect: false`) will ever emit — a listener written against `close`
-alone, before reconnect support existed, still sees exactly the frame it always did once a
-reconnecting carrier's retries give up.
+`client-socket` itself with `reconnect: false`) will ever emit. A listener that must react to a
+reconnecting carrier giving up listens for `lost` — a `close` there comes only from its owner's
+own `close()` or a terminal server code.
 
 ## What the model expects of a carrier
 

package/build/consts.d.ts

@@ -13,10 +13,9 @@ export declare const CALL_TIMEOUT = 60000;
 /**
  * System frames a carrier synthesises around the lifecycle of the underlying transport.
  *
- * `Close` keeps its original meaning: the connection is gone for good — a client-initiated
- * close, a terminal server code, or a reconnect budget exhausted. A drop the carrier intends to
- * retry is reported as `Disconnected` instead, so a listener that only knew about `close` before
- * this carried reconnect support still sees exactly the frame it always did once retries give up.
+ * `Close` means the connection is gone for good — a client-initiated close, or a terminal server
+ * code. A drop the carrier intends to retry is reported as `Disconnected`, and an exhausted retry
+ * budget as `Lost` alone: a lost connection can still be revived, so it is not closed.
  */
 export declare enum SocketSystemEvent {
     Close = "close",

package/build/consts.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"consts.d.ts","sourceRoot":"","sources":["../src/consts.ts"],"names":[],"mappings":"AACA,oBAAY,WAAW;IACrB,IAAI,SAAS;IACb,MAAM,WAAW;IACjB,KAAK,UAAU;IACf,OAAO,YAAY;IACnB,QAAQ,aAAa;IACrB,KAAK,UAAU;IACf,OAAO,YAAY;IACnB,IAAI,SAAS;IACb,MAAM,WAAW;CAClB;AAED,eAAO,MAAM,YAAY,QAAQ,CAAA;AAEjC;;;;;;;GAOG;AACH,oBAAY,iBAAiB;IAC3B,KAAK,UAAU;IACf,YAAY,iBAAiB;IAC7B,YAAY,iBAAiB;IAC7B,WAAW,gBAAgB;IAC3B,IAAI,SAAS;CACd;AAED;;;;;GAKG;AACH,eAAO,MAAM,6BAA6B,OAAO,CAAA"}
+{"version":3,"file":"consts.d.ts","sourceRoot":"","sources":["../src/consts.ts"],"names":[],"mappings":"AACA,oBAAY,WAAW;IACrB,IAAI,SAAS;IACb,MAAM,WAAW;IACjB,KAAK,UAAU;IACf,OAAO,YAAY;IACnB,QAAQ,aAAa;IACrB,KAAK,UAAU;IACf,OAAO,YAAY;IACnB,IAAI,SAAS;IACb,MAAM,WAAW;CAClB;AAED,eAAO,MAAM,YAAY,QAAQ,CAAA;AAEjC;;;;;;GAMG;AACH,oBAAY,iBAAiB;IAC3B,KAAK,UAAU;IACf,YAAY,iBAAiB;IAC7B,YAAY,iBAAiB;IAC7B,WAAW,gBAAgB;IAC3B,IAAI,SAAS;CACd;AAED;;;;;GAKG;AACH,eAAO,MAAM,6BAA6B,OAAO,CAAA"}

package/build/consts.js

@@ -14,10 +14,9 @@ export const CALL_TIMEOUT = 60000;
 /**
  * System frames a carrier synthesises around the lifecycle of the underlying transport.
  *
- * `Close` keeps its original meaning: the connection is gone for good — a client-initiated
- * close, a terminal server code, or a reconnect budget exhausted. A drop the carrier intends to
- * retry is reported as `Disconnected` instead, so a listener that only knew about `close` before
- * this carried reconnect support still sees exactly the frame it always did once retries give up.
+ * `Close` means the connection is gone for good — a client-initiated close, or a terminal server
+ * code. A drop the carrier intends to retry is reported as `Disconnected`, and an exhausted retry
+ * budget as `Lost` alone: a lost connection can still be revived, so it is not closed.
  */
 export var SocketSystemEvent;
 (function (SocketSystemEvent) {

package/build/consts.js.map

@@ -1 +1 @@
-{"version":3,"file":"consts.js","sourceRoot":"","sources":["../src/consts.ts"],"names":[],"mappings":"AACA,MAAM,CAAN,IAAY,WAUX;AAVD,WAAY,WAAW;IACrB,4BAAa,CAAA;IACb,gCAAiB,CAAA;IACjB,8BAAe,CAAA;IACf,kCAAmB,CAAA;IACnB,oCAAqB,CAAA;IACrB,8BAAe,CAAA;IACf,kCAAmB,CAAA;IACnB,4BAAa,CAAA;IACb,gCAAiB,CAAA;AACnB,CAAC,EAVW,WAAW,KAAX,WAAW,QAUtB;AAED,MAAM,CAAC,MAAM,YAAY,GAAG,KAAK,CAAA;AAEjC;;;;;;;GAOG;AACH,MAAM,CAAN,IAAY,iBAMX;AAND,WAAY,iBAAiB;IAC3B,oCAAe,CAAA;IACf,kDAA6B,CAAA;IAC7B,kDAA6B,CAAA;IAC7B,gDAA2B,CAAA;IAC3B,kCAAa,CAAA;AACf,CAAC,EANW,iBAAiB,KAAjB,iBAAiB,QAM5B;AAED;;;;;GAKG;AACH,MAAM,CAAC,MAAM,6BAA6B,GAAG,IAAI,CAAA"}
+{"version":3,"file":"consts.js","sourceRoot":"","sources":["../src/consts.ts"],"names":[],"mappings":"AACA,MAAM,CAAN,IAAY,WAUX;AAVD,WAAY,WAAW;IACrB,4BAAa,CAAA;IACb,gCAAiB,CAAA;IACjB,8BAAe,CAAA;IACf,kCAAmB,CAAA;IACnB,oCAAqB,CAAA;IACrB,8BAAe,CAAA;IACf,kCAAmB,CAAA;IACnB,4BAAa,CAAA;IACb,gCAAiB,CAAA;AACnB,CAAC,EAVW,WAAW,KAAX,WAAW,QAUtB;AAED,MAAM,CAAC,MAAM,YAAY,GAAG,KAAK,CAAA;AAEjC;;;;;;GAMG;AACH,MAAM,CAAN,IAAY,iBAMX;AAND,WAAY,iBAAiB;IAC3B,oCAAe,CAAA;IACf,kDAA6B,CAAA;IAC7B,kDAA6B,CAAA;IAC7B,gDAA2B,CAAA;IAC3B,kCAAa,CAAA;AACf,CAAC,EANW,iBAAiB,KAAjB,iBAAiB,QAM5B;AAED;;;;;GAKG;AACH,MAAM,CAAC,MAAM,6BAA6B,GAAG,IAAI,CAAA"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@owlmeans/socket",
-  "version": "0.1.18-rc.29",
+  "version": "0.1.18-rc.30",
   "license": "MIT",
   "type": "module",
   "scripts": {
@@ -21,9 +21,9 @@
     }
   },
   "dependencies": {
-    "@owlmeans/auth": "^0.1.18-rc.31",
-    "@owlmeans/basic-ids": "^0.1.18-rc.30",
-    "@owlmeans/error": "^0.1.18-rc.31"
+    "@owlmeans/auth": "^0.1.18-rc.32",
+    "@owlmeans/basic-ids": "^0.1.18-rc.31",
+    "@owlmeans/error": "^0.1.18-rc.32"
   },
   "devDependencies": {
     "@owlmeans/dep-config": "workspace:*",

package/src/consts.ts

@@ -16,10 +16,9 @@ export const CALL_TIMEOUT = 60000
 /**
  * System frames a carrier synthesises around the lifecycle of the underlying transport.
  *
- * `Close` keeps its original meaning: the connection is gone for good — a client-initiated
- * close, a terminal server code, or a reconnect budget exhausted. A drop the carrier intends to
- * retry is reported as `Disconnected` instead, so a listener that only knew about `close` before
- * this carried reconnect support still sees exactly the frame it always did once retries give up.
+ * `Close` means the connection is gone for good — a client-initiated close, or a terminal server
+ * code. A drop the carrier intends to retry is reported as `Disconnected`, and an exhausted retry
+ * budget as `Lost` alone: a lost connection can still be revived, so it is not closed.
  */
 export enum SocketSystemEvent {
   Close = 'close',