@pulse-compute/s3 1.0.0-beta.3 → 1.0.0-beta.5

package/README.md

@@ -7,9 +7,9 @@
 > **Supported entry points:** `@pulse-compute/s3`<br>
 > **Stability:** The package root supports head, getText and putText on Node Native, Node JavaScript and Fastly Native. Fastly JavaScript is ineligible. Provider and lowering subpaths are toolchain-only; live origin acceptance is separate.<br>
 > **npm:** [`@pulse-compute/s3`](https://www.npmjs.com/package/@pulse-compute/s3)<br>
-> **Canonical documentation:** [Package guide](https://pulsecompute.io/v1.0.0-beta.3/packages/s3/)
+> **Canonical documentation:** [Package guide](https://pulsecompute.io/v1.0.0-beta.5/packages/s3/)
 >
-> This release-status block is generated from the synchronized `Pulse 1.0.0-beta.3` package policy.
+> This release-status block is generated from the synchronized `Pulse 1.0.0-beta.5` package policy.
 <!-- pulse-package-status:end -->
 
 This package provides bounded, exact-key `head`, `getText` and `putText` effects for
@@ -31,7 +31,7 @@ Put mappings under `<profile>.node.bindings.s3` or
 | `bucket`, `region` | Explicit bucket and signing region |
 | `accessKeyIdSecret`, `secretAccessKeySecret` | Named provider secret references |
 | `sessionTokenSecret` | Optional named session-token reference |
-| `maxTextBytes` | 1–32768; default 32768 |
+| `maxTextBytes` | 1–2097152; default 32768 |
 | `timeoutMs` | 1–30000; default 10000 |
 | `backend` | Fastly-only named static backend |
 
@@ -65,19 +65,23 @@ Native targets compose Crypto's AssemblyScript primitives. Fastly JavaScript S3
 is ineligible because its SDK projects raw headers and loses required metadata
 information. This target exclusion does not gate supported targets.
 
-For a JSON request carrying the maximum text consisting of escaped control
-characters, configure the existing `schemas.maxBytes` request envelope to
-262144; the object itself remains bounded to 32768 UTF-8 bytes. The acceptance
+Select `maxTextBytes: 2097152` per binding for 2 MiB objects; the default remains
+32768. Request/schema limits are independent. Use `schemas.maxBytes: 2097152`
+for a 2 MiB encoded object, and explicitly size larger transport envelopes when
+JSON escaping requires it. The S3/text effect envelope is 12,648,448 bytes.
+Local HTTP ingress also uses `dev.maxBodyBytes`, default 65536. Primary-memory
+Native digest/S3 modules enforce a 256 MiB Wasm maximum; fixed-memory linked
+guests retain their separate ABI. KV values, HMAC and JWT do not grow with S3. The acceptance
 consumer uses generic JSON responses (`strict: false`) to compare the complete
 result unions. Applications using strict JSON must declare response schemas.
 
 The package root is the supported application API in the synchronized
-`1.0.0-beta.3` release candidate. Provider, manifest, compiler and Native
+`1.0.0-beta.5` release candidate. Provider, manifest, compiler and Native
 subpaths are trusted toolchain integration, not application imports. Install
 S3 with the exact compatible Pulse, CLI and provider candidate set; candidate
 preparation does not imply npm publication.
 
-See the [S3 guide](https://pulsecompute.io/v1.0.0-beta.3/packages/s3/) for the
+See the [S3 guide](https://pulsecompute.io/v1.0.0-beta.5/packages/s3/) for the
 lowering contract, support matrix and acceptance boundaries. Local acceptance
 executes Node Native, Node JavaScript and compiled Fastly Native Wasm against
 controlled origins. Live Object Storage evidence follows infrastructure setup.

package/conformance/README.md

@@ -10,4 +10,4 @@ metadata limits, truncation, deadlines, write uncertainty and secret redaction.
 Fastly Native executes compiled Wasm against host ABI fixtures. These checks
 do not establish live origin behavior; that evidence follows infrastructure
 setup. Fastly JavaScript is ineligible for S3 because its SDK loses raw header
-metadata. See the [S3 guide](https://pulsecompute.io/v1.0.0-beta.3/packages/s3/).
+metadata. See the [S3 guide](https://pulsecompute.io/v1.0.0-beta.5/packages/s3/).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pulse-compute/s3",
-  "version": "1.0.0-beta.3",
+  "version": "1.0.0-beta.5",
   "license": "Apache-2.0",
   "engines": {
     "node": "^22.14.0 || ^24.0.0"
@@ -39,8 +39,8 @@
     "manifest": "./pulsewasm.manifest.cjs"
   },
   "dependencies": {
-    "@pulse-compute/runtime": "1.0.0-beta.3",
-    "@pulse-compute/wasm-contracts": "1.0.0-beta.3"
+    "@pulse-compute/runtime": "1.0.0-beta.5",
+    "@pulse-compute/wasm-contracts": "1.0.0-beta.5"
   },
   "publishConfig": {
     "access": "public"
@@ -50,7 +50,7 @@
     "url": "git+https://github.com/pulse-compute/pulse.git",
     "directory": "packages/s3"
   },
-  "homepage": "https://pulsecompute.io/v1.0.0-beta.3/packages/s3/",
+  "homepage": "https://pulsecompute.io/v1.0.0-beta.5/packages/s3/",
   "bugs": {
     "url": "https://github.com/pulse-compute/pulse/issues"
   }

package/src/index.js

@@ -1,10 +1,15 @@
 'use strict';
 const { createPackageRuntime } = require('@pulse-compute/runtime/package');
-const { S3_PACKAGE, S3_CONTRACT_ID, S3_OPERATIONS } = require('@pulse-compute/wasm-contracts/s3/contracts');
+const { S3_PACKAGE, S3_CONTRACT_ID, S3_OPERATIONS, S3_LIMITS } = require('@pulse-compute/wasm-contracts/s3/contracts');
 const { normalizeResult, normalizePutOptions } = require('./provider.js');
 const runtime = createPackageRuntime({ package: S3_PACKAGE, contractId: S3_CONTRACT_ID, providerKind: 's3', operations: S3_OPERATIONS });
 exports.s3 = Object.freeze({
   head(ctx, binding, key) { return runtime.effect(ctx, 'head', { binding, key }, (result) => normalizeResult('head', result)); },
   getText(ctx, binding, key) { return runtime.effect(ctx, 'getText', { binding, key }, (result) => normalizeResult('getText', result)); },
-  putText(ctx, binding, key, text, options) { return runtime.effect(ctx, 'putText', { binding, key, text, ...normalizePutOptions(options) }, (result) => normalizeResult('putText', result)); }
+  putText(ctx, binding, key, text, options) {
+    // Retain an over-limit sentinel without copying an unbounded string into
+    // the effect envelope. Providers reject it before encoding or dispatch.
+    const boundedText = typeof text === 'string' ? text.slice(0, S3_LIMITS.textBytes + 1) : null;
+    return runtime.effect(ctx, 'putText', { binding, key, text: boundedText, ...normalizePutOptions(options) }, (result) => normalizeResult('putText', result));
+  }
 });

package/src/provider.js

@@ -26,7 +26,7 @@ function normalizeBinding(value) {
     if (field === 'sessionTokenSecret' && input[field] === undefined) continue;
     if (typeof input[field] !== 'string' || !namePattern.test(input[field])) throw new TypeError('S3 credentials must be valid named secret references.');
   }
-  const maxTextBytes = input.maxTextBytes === undefined ? S3_LIMITS.textBytes : input.maxTextBytes;
+  const maxTextBytes = input.maxTextBytes === undefined ? S3_LIMITS.defaultTextBytes : input.maxTextBytes;
   const timeoutMs = input.timeoutMs === undefined ? 10000 : input.timeoutMs;
   if (!Number.isInteger(maxTextBytes) || maxTextBytes < 1 || maxTextBytes > S3_LIMITS.textBytes || !Number.isInteger(timeoutMs) || timeoutMs < 1 || timeoutMs > 30000) throw new TypeError('S3 limits are outside the bounded subset.');
   return Object.freeze({ ...input, endpoint: url.origin, maxTextBytes, timeoutMs });