@cat-factory/provider-bedrock 0.7.352 → 0.7.354

package/README.md

@@ -1,6 +1,6 @@
 # @cat-factory/provider-bedrock
 
-Opt-in **AWS Bedrock** model resolver for cat-factory's AI provisioning facade — lets a
+Opt-in **AWS Bedrock** model resolver for cat-factory's AI provisioning facade: lets a
 deployment serve LLMs through Amazon Bedrock alongside (or instead of) the built-in direct
 vendors.
 
@@ -8,7 +8,7 @@ vendors.
 
 Bedrock support pulls in the AWS Bedrock SDK (`@ai-sdk/amazon-bedrock` + `ai`), which is heavy
 and irrelevant to any deployment that doesn't use Bedrock. Keeping it in a separate opt-in
-package means the core packages and the Cloudflare Worker base registry stay free of the SDK —
+package means the core packages and the Cloudflare Worker base registry stay free of the SDK:
 only a facade that actually wires Bedrock pays for it. It contributes a single provider
 (`bedrock`) to a `CompositeModelProvider` through the neutral `ModelResolver` / `ProviderRegistry`
 seam from `@cat-factory/agents`; no model-resolution logic is duplicated.
@@ -20,7 +20,7 @@ The package exports two helpers:
 - `bedrockResolver(opts)` → a `ModelResolver` for the `bedrock` provider.
 - `bedrockRegistry(opts)` → a `ProviderRegistry` (`{ bedrock: resolver }`) ready to mix in.
 
-### Node / local facade — via env
+### Node / local facade: via env
 
 The Node facade wires Bedrock automatically **when `BEDROCK_REGION` is set** (see
 `createNodeModelProviderResolver` in `backend/runtimes/node/src/modelProvider.ts`); it appends
@@ -45,10 +45,10 @@ if (env.BEDROCK_REGION) {
 
 So a Node/local deployment opts in purely with env: `BEDROCK_REGION` (required to enable),
 optional `AWS_ACCESS_KEY_ID` / `AWS_SECRET_ACCESS_KEY` / `AWS_SESSION_TOKEN` (omit to use the
-ambient AWS credential chain — instance role, `~/.aws`, etc.), and optional `BEDROCK_MODELS`
+ambient AWS credential chain; instance role, `~/.aws`, etc.), and optional `BEDROCK_MODELS`
 (comma-separated allow-list).
 
-### Cloudflare Worker facade — via `registerModelRegistry`
+### Cloudflare Worker facade: via `registerModelRegistry`
 
 The Worker's base registry ships without the SDK; a deployment mixes Bedrock in at startup
 through the installation-level model-provider extension point (see
@@ -62,7 +62,7 @@ registerModelRegistry((env) => bedrockRegistry({ region: env.BEDROCK_REGION }))
 ```
 
 Registration is process-wide and read by every `buildContainer(env)` call, so the provider
-reaches all paths — HTTP requests, the durable Workflow driver, and the cron sweeper — not just
+reaches all paths (HTTP requests, the durable Workflow driver, and the cron sweeper) not just
 one entry point. The factory receives the runtime `env`, so credentials/region come from the
 deployment's configuration.
 
@@ -89,4 +89,4 @@ message instead of a deep AWS SDK error. Omit `supportedModels` to forward any m
 
 Part of cat-factory's opt-in **AWS stack** alongside [`@cat-factory/provider-s3`](../provider-s3)
 (blob storage) and [`@cat-factory/eks`](../eks) (runner + environment backends). Each is
-independent and registers into its own seam — mix in only what you use.
+independent and registers into its own seam: mix in only what you use.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cat-factory/provider-bedrock",
-  "version": "0.7.352",
+  "version": "0.7.354",
   "description": "Opt-in AWS Bedrock model registry for the Agent Architecture Board's AI provisioning facade. Mix into a CompositeModelProvider to add the `bedrock` provider.",
   "repository": {
     "type": "git",
@@ -26,8 +26,8 @@
   "dependencies": {
     "@ai-sdk/amazon-bedrock": "^5.0.40",
     "ai": "^7.0.47",
-    "@cat-factory/agents": "0.106.0",
-    "@cat-factory/kernel": "0.216.0"
+    "@cat-factory/agents": "0.106.2",
+    "@cat-factory/kernel": "0.218.0"
   },
   "devDependencies": {
     "typescript": "7.0.2",