@fougere/transport-http 0.4.0-alpha.0 → 0.5.0-alpha.0

package/dist/policy.d.ts

@@ -1,8 +1,9 @@
 /**
  * What every receiver of the envelope decides the same way, and what it does not.
  *
- * The cap and the answers are POLICY — `1024 * 1024` was spelled in four packages and
- * omitted by the receiver written by hand. Reading the body is PLUMBING, and it belongs to
+ * The answers are POLICY. The CAP is core's (`wire/call.ts`) — it was spelled in four packages
+ * and omitted by the receiver written by hand, and this file claimed to have consolidated it
+ * while three doors kept their own literal. Reading the body is PLUMBING, and it belongs to
  * the transport: a `node:http` stream and a `Request` body are read differently, and putting
  * Node through the Web reader HALVED the door that took it (measured, 2026-08-22: the JSON-RPC
  * door fell from 0.677 to 0.341 of its hand-written baseline, while the REST door, which never
@@ -11,8 +12,8 @@
  * So this file holds the decisions. Each receiver keeps its own reader.
  */
 import { type RpcResponse } from './jsonrpc.js';
-/** What a receiver accepts before it stops reading. */
-export declare const MAX_BODY_BYTES: number;
+/** What a receiver accepts before it stops reading — declared by core, re-exported here. */
+export { MAX_BODY_BYTES } from '@fougere/core';
 /** The path the envelope answers on. A host mounting it elsewhere passes its own. */
 export declare const CALL_PATH = "/_fougere/call";
 /** The answer to a payload that was not JSON. */

package/dist/policy.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"policy.d.ts","sourceRoot":"","sources":["../src/policy.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AACH,OAAO,EAAe,KAAK,WAAW,EAAE,MAAM,cAAc,CAAC;AAE7D,uDAAuD;AACvD,eAAO,MAAM,cAAc,QAAc,CAAC;AAE1C,qFAAqF;AACrF,eAAO,MAAM,SAAS,mBAAmB,CAAC;AAE1C,iDAAiD;AACjD,eAAO,MAAM,UAAU,QAAO,WAI5B,CAAC;AAEH,yCAAyC;AACzC,eAAO,MAAM,QAAQ;IAAY,KAAK;CAAwB,CAAC"}
+{"version":3,"file":"policy.d.ts","sourceRoot":"","sources":["../src/policy.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AACH,OAAO,EAAe,KAAK,WAAW,EAAE,MAAM,cAAc,CAAC;AAE7D,4FAA4F;AAC5F,OAAO,EAAE,cAAc,EAAE,MAAM,eAAe,CAAC;AAE/C,qFAAqF;AACrF,eAAO,MAAM,SAAS,mBAAmB,CAAC;AAE1C,iDAAiD;AACjD,eAAO,MAAM,UAAU,QAAO,WAI5B,CAAC;AAEH,yCAAyC;AACzC,eAAO,MAAM,QAAQ;IAAY,KAAK;CAAwB,CAAC"}

package/dist/policy.js

@@ -1,8 +1,9 @@
 /**
  * What every receiver of the envelope decides the same way, and what it does not.
  *
- * The cap and the answers are POLICY — `1024 * 1024` was spelled in four packages and
- * omitted by the receiver written by hand. Reading the body is PLUMBING, and it belongs to
+ * The answers are POLICY. The CAP is core's (`wire/call.ts`) — it was spelled in four packages
+ * and omitted by the receiver written by hand, and this file claimed to have consolidated it
+ * while three doors kept their own literal. Reading the body is PLUMBING, and it belongs to
  * the transport: a `node:http` stream and a `Request` body are read differently, and putting
  * Node through the Web reader HALVED the door that took it (measured, 2026-08-22: the JSON-RPC
  * door fell from 0.677 to 0.341 of its hand-written baseline, while the REST door, which never
@@ -11,8 +12,8 @@
  * So this file holds the decisions. Each receiver keeps its own reader.
  */
 import { PARSE_ERROR } from './jsonrpc.js';
-/** What a receiver accepts before it stops reading. */
-export const MAX_BODY_BYTES = 1024 * 1024;
+/** What a receiver accepts before it stops reading — declared by core, re-exported here. */
+export { MAX_BODY_BYTES } from '@fougere/core';
 /** The path the envelope answers on. A host mounting it elsewhere passes its own. */
 export const CALL_PATH = '/_fougere/call';
 /** The answer to a payload that was not JSON. */

package/dist/policy.js.map

@@ -1 +1 @@
-{"version":3,"file":"policy.js","sourceRoot":"","sources":["../src/policy.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AACH,OAAO,EAAE,WAAW,EAAoB,MAAM,cAAc,CAAC;AAE7D,uDAAuD;AACvD,MAAM,CAAC,MAAM,cAAc,GAAG,IAAI,GAAG,IAAI,CAAC;AAE1C,qFAAqF;AACrF,MAAM,CAAC,MAAM,SAAS,GAAG,gBAAgB,CAAC;AAE1C,iDAAiD;AACjD,MAAM,CAAC,MAAM,UAAU,GAAG,GAAgB,EAAE,CAAC,CAAC;IAC5C,OAAO,EAAE,KAAK;IACd,EAAE,EAAE,IAAI;IACR,KAAK,EAAE,EAAE,IAAI,EAAE,WAAW,EAAE,OAAO,EAAE,aAAa,EAAE;CACrD,CAAC,CAAC;AAEH,yCAAyC;AACzC,MAAM,CAAC,MAAM,QAAQ,GAAG,GAAG,EAAE,CAAC,CAAC,EAAE,KAAK,EAAE,mBAAmB,EAAE,CAAC,CAAC"}
+{"version":3,"file":"policy.js","sourceRoot":"","sources":["../src/policy.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AACH,OAAO,EAAE,WAAW,EAAoB,MAAM,cAAc,CAAC;AAE7D,4FAA4F;AAC5F,OAAO,EAAE,cAAc,EAAE,MAAM,eAAe,CAAC;AAE/C,qFAAqF;AACrF,MAAM,CAAC,MAAM,SAAS,GAAG,gBAAgB,CAAC;AAE1C,iDAAiD;AACjD,MAAM,CAAC,MAAM,UAAU,GAAG,GAAgB,EAAE,CAAC,CAAC;IAC5C,OAAO,EAAE,KAAK;IACd,EAAE,EAAE,IAAI;IACR,KAAK,EAAE,EAAE,IAAI,EAAE,WAAW,EAAE,OAAO,EAAE,aAAa,EAAE;CACrD,CAAC,CAAC;AAEH,yCAAyC;AACzC,MAAM,CAAC,MAAM,QAAQ,GAAG,GAAG,EAAE,CAAC,CAAC,EAAE,KAAK,EAAE,mBAAmB,EAAE,CAAC,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fougere/transport-http",
-  "version": "0.4.0-alpha.0",
+  "version": "0.5.0-alpha.0",
   "description": "The call contract on the wire, in JSON-RPC 2.0 (server + client).",
   "keywords": [
     "fougere",
@@ -38,12 +38,12 @@
     "src"
   ],
   "dependencies": {
-    "@fougere/core": "0.4.0-alpha.0"
+    "@fougere/core": "0.5.0-alpha.0"
   },
   "devDependencies": {
     "jiti": "^2.6.1",
-    "@fougere/schema": "0.4.0-alpha.0",
-    "@fougere/container": "0.4.0-alpha.0"
+    "@fougere/container": "0.5.0-alpha.0",
+    "@fougere/schema": "0.5.0-alpha.0"
   },
   "publishConfig": {
     "access": "public"

package/src/policy.ts

@@ -1,8 +1,9 @@
 /**
  * What every receiver of the envelope decides the same way, and what it does not.
  *
- * The cap and the answers are POLICY — `1024 * 1024` was spelled in four packages and
- * omitted by the receiver written by hand. Reading the body is PLUMBING, and it belongs to
+ * The answers are POLICY. The CAP is core's (`wire/call.ts`) — it was spelled in four packages
+ * and omitted by the receiver written by hand, and this file claimed to have consolidated it
+ * while three doors kept their own literal. Reading the body is PLUMBING, and it belongs to
  * the transport: a `node:http` stream and a `Request` body are read differently, and putting
  * Node through the Web reader HALVED the door that took it (measured, 2026-08-22: the JSON-RPC
  * door fell from 0.677 to 0.341 of its hand-written baseline, while the REST door, which never
@@ -12,8 +13,8 @@
  */
 import { PARSE_ERROR, type RpcResponse } from './jsonrpc.js';
 
-/** What a receiver accepts before it stops reading. */
-export const MAX_BODY_BYTES = 1024 * 1024;
+/** What a receiver accepts before it stops reading — declared by core, re-exported here. */
+export { MAX_BODY_BYTES } from '@fougere/core';
 
 /** The path the envelope answers on. A host mounting it elsewhere passes its own. */
 export const CALL_PATH = '/_fougere/call';