@plumbus/ai-bedrock 0.3.0-beta.1 → 0.3.0

package/CHANGELOG.md

@@ -1,23 +1,13 @@
 # @plumbus/ai-bedrock
 
-## 0.3.0-beta.1 — 2026-10-12
+## 0.3.0 — Stabilization compatibility family
 
-### Added
-
-- Carry Converse/ConverseStream prompt caching from stable 0.2.2 into the beta family, preserving native structured-output schemas and per-call deadlines. Use with core 0.8.0-beta.10.
-
-### Fixed
+- Upgrade the framework test toolchain to **Vitest 5.0.4** and require Node 22.12+ on the 22.x line, Node 24.x, or Node 26+.
 
-- **A request its timeout ends is reported as a timeout.** When `requestTimeout`, or the request's own `timeout` (a prompt's `model.timeoutMs` or a call's `timeoutMs` in core), ended a Converse call, it failed with the AWS SDK's bare `AbortError: Request aborted`, the same as a caller's cancellation. It now fails with core's `ProviderAPIError` shape (`name: 'ProviderAPIError'`, `providerName: 'bedrock'`, `retryable: false`, `timeoutMs`), message `Bedrock request timed out after <ms> ms`, which core's `isProviderAPIError` recognises; a stream ends with an `error` event carrying that message, also when the timeout cuts it off after some deltas — whether the SDK's event stream then breaks or just ends, which could otherwise be reported as some other error or as a finished answer. A caller's abort is still rethrown as raised.
-- **Embeddings honour a per-call timeout.** `embed()` gave every InvokeModel call the adapter's `requestTimeout`, ignoring the request, and a call it ended failed with a bare `AbortError`. `EmbeddingRequest.timeout` (core's RAG `ingest`/`retrieve` and `ctx.ai.retrieve` `timeoutMs`) now sets it, per InvokeModel call, and a call the timeout ends fails with the same `ProviderAPIError` shape as Converse (`Bedrock request timed out after <ms> ms`, `timeoutMs`), which core's `isProviderTimeoutError` recognises.
-- **An unusable timeout is refused before anything is sent.** A `requestTimeout` or request `timeout` that was not a whole number of milliseconds from 1 to 2 147 483 647 went straight to `AbortSignal.timeout`, which threw a bare `RangeError` for `-1`, `1.5` or `NaN` (an `AI_BEDROCK_REQUEST_TIMEOUT` that is not a number), ended the request at once for `0`, and fired after 1 ms above the maximum. `complete()`, `stream()` and `embed()` now fail with core's `AIInvalidRequestError` (`reason: 'timeout_invalid'`) before loading pricing or calling Bedrock, as core's OpenAI and Anthropic adapters do.
-- **Embeddings stop when the caller cancels.** `embed()` ignored the request's signal (core had none on `EmbeddingRequest`), so a cancelled `ctx.ai.retrieve` or RAG `ingest` kept every InvokeModel call running and sent the remaining texts. `embed()` now honours `EmbeddingRequest.signal` (core's new field): the calls in flight are aborted and fail as `complete()` does on a caller abort (the AWS SDK's `AbortError`, the caller's reason as its `cause`), no further text is sent once it fires between texts (rejecting with the caller's reason as raised), and an already-aborted signal rejects with its reason before pricing is loaded or Bedrock is called. Needs the `@plumbus/core` release that adds `EmbeddingRequest.signal`.
-
-## 0.3.0-beta.0 — 2026-09-11 — core 0.8 beta family
-
-### Upgrade boundary
+Requires the coordinated core 0.8 family. Follow the [stabilization upgrade guide](../../docs/upgrading-stabilization.md) and the installed `node_modules/@plumbus/core/instructions/stabilization.md`; update installed Plumbus packages together.
 
-- Beta prerelease of the coordinated core 0.8 family (core 0.8.x, UI 0.9.x, MCP 0.7.x, voice 0.6.x, other add-ons 0.3.x), published under the branch-named npm dist-tag `plumbus-next` (`latest` stays on the 0.7 family). Previous caret ranges exclude it; install the whole family together and follow the [0.8 upgrade notes](../../docs/upgrading-core-0.8.md). Internal peers use prerelease-inclusive ranges (for example `>=0.8.0-beta.0 <0.9.0`) until the family goes stable.
+- Update Plumbus peers to `@plumbus/core` `0.8.x`. This minor line makes the compatibility change an explicit upgrade.
+- Refresh package instructions and compatibility guidance for core 0.8 and agent wiring v21. Runtime APIs in this add-on are unchanged.
 
 ## 0.2.2 — 2026-10-08
 

package/README.md

@@ -1,5 +1,7 @@
 # @plumbus/ai-bedrock
 
+Release **0.3.0** belongs to the core 0.8 stabilization family. See the [changelog](./CHANGELOG.md) and [upgrade guide](../../docs/upgrading-stabilization.md) before updating an existing app.
+
 > **Amazon Bedrock for [Plumbus](https://github.com/plumbus-framework/plumbus) AI.** Optional AWS SDK adapter for Converse chat, ConverseStream, Titan embeddings, and **package-owned USD cost** from the AWS Price List (or a mounted pricing file).
 
 [![npm](https://img.shields.io/npm/v/@plumbus/ai-bedrock.svg)](https://www.npmjs.com/package/@plumbus/ai-bedrock)
@@ -46,7 +48,7 @@ An opt-in peer keeps core lean while giving AWS shops a first-class `provider: '
 
 ## Status
 
-Optional peer of `@plumbus/core` (beta family version **`0.3.0-beta.1`**, npm dist-tag `plumbus-next`; required peer `@plumbus/core` **`>=0.8.0-beta.0 <0.9.0`**). The beta includes prompt caching through `ctx.ai`; on the stable 0.7 line caching needs core **≥ 0.7.9** and Bedrock **≥ 0.2.2**. Install alone is not enough until the adapter is registered (env discovery or `createBedrockAdapter`).
+Optional peer of `@plumbus/core` (version-locked **`0.3.x`**; required peer `@plumbus/core` **`0.8.x`**). **Runtime floor:** `@plumbus/core` **≥ 0.7.0**; prompt caching through `ctx.ai` needs **≥ 0.7.9**. Install alone is not enough until the adapter is registered (env discovery or `createBedrockAdapter`).
 
 ## Install
 
@@ -134,7 +136,7 @@ Full curl, normalize script, ConfigMap sketch: **[instructions/pricing.md](./ins
 - **Missing pricing file** — file mode throws on first call; auto-download failure warns, leaves cost unknown, and backs off 5 minutes before retrying.
 - **Unmapped / unkeyed models** — inference works; **no `cost` field** is set until the pricing file has an explicit family-key row (auto-download is best-effort, not a complete AWS catalog). Core then falls back to its own catalog rather than recording the call as free.
 - **IAM** — Converse itself requires `bedrock:InvokeModel`; do not scope that action to embedding models only.
-- **Wiring** — after install, `plumbus init --patch` (wiring v13+, any core 0.7.x) so agents see `instructions/`.
+- **Wiring** — after install, `plumbus init --patch` (wiring v13+, any core 0.8.x) so agents see `instructions/`.
 
 ## Documentation / Agent recipes