@namzu/bedrock 5.0.0 → 5.1.0

package/CHANGELOG.md

@@ -1,5 +1,31 @@
 # Changelog
 
+## 5.1.0
+
+### Minor Changes
+
+- 03e363c: Declare the Node floor these packages already had, and export a type `TelemetryConfig` already required.
+
+  **`engines.node: ">=20.0.0"`.** Only `@namzu/cli` declared one; the other fourteen published without any, so npm could not warn a consumer installing onto an unsupported runtime — they got a crash at some later import instead. The floor is not new: `@namzu/cli` has declared it since it shipped and `install.sh` has enforced it since it existed. This makes the other fourteen say the same thing.
+
+  If you install with `engine-strict=true` on Node 18, an install that previously emitted nothing will now fail. Upgrade to Node 20 or newer, which the code already assumed. Everyone else sees no change, or an `EBADENGINE` warning that replaces a later crash.
+
+  Worth stating plainly: CI verifies Node 22 and 24. The 20 floor is a declared minimum, not a tested one.
+
+  **`SpanProcessorLike` is now exported from `@namzu/telemetry`.** `TelemetryConfig.spanProcessors` takes `readonly SpanProcessorLike[]`, and the type had no export — a field on the public surface whose type was not on it, so a host supplying the value had to inline the shape or reach for `any`.
+
+## 5.0.1
+
+### Patch Changes
+
+- 5394981: Make each driver's README an npm package page rather than its manual.
+
+  Every driver README carried its full reference — configuration tables, capability matrices, error surfaces — between 167 and 392 lines of it. That is a reasonable shape for a single-package repository, where the README _is_ the documentation, and the wrong one for a package in a monorepo that has a `docs/` tree: it duplicates what the docs say, and nothing checks that the two agree.
+
+  The README is now what a reader needs in the first minute — what the driver is, install, one working example, links. The reference moved to `docs/providers/<name>.md`, whole, and its code samples are now compiled against the built SDK by the doc-fence gate on every CI run. They never were before; several did not compile.
+
+  No API change.
+
 ## 5.0.0
 
 ### Major Changes

package/README.md

@@ -1,6 +1,36 @@
-# @namzu/bedrock
+<!-- okf
+type: Reference
+title: "@namzu/bedrock"
+description: >-
+  Implements the kernel's `LLMProvider` interface over AWS Bedrock, carrying
+  the region and credential semantics natively rather than as a base-URL
+  override.
+tags: [readme, package, provider, bedrock]
+timestamp: 2026-08-17T00:00:00Z
+status: active
+diataxis: reference
+-->
 
-AWS Bedrock LLM provider for [`@namzu/sdk`](https://www.npmjs.com/package/@namzu/sdk). Thin wrapper around `@aws-sdk/client-bedrock-runtime` exposing Bedrock's **Converse API** (chat + streaming) with full tool-use support, conformant to the `LLMProvider` contract.
+<div align="center">
+
+<h1>@namzu/bedrock</h1>
+
+**The Bedrock model driver for [Namzu](https://github.com/cogitave/namzu).**
+
+[![npm](https://img.shields.io/npm/v/@namzu/bedrock.svg)](https://www.npmjs.com/package/@namzu/bedrock)
+[![build](https://github.com/cogitave/namzu/actions/workflows/ci.yml/badge.svg)](https://github.com/cogitave/namzu/actions/workflows/ci.yml)
+[![license](https://img.shields.io/badge/license-FSL--1.1--MIT-blue.svg)](https://github.com/cogitave/namzu/blob/main/LICENSE.md)
+
+[Install](#install) · [Usage](#usage) · [Documentation](#documentation)
+
+</div>
+
+---
+
+Implements the kernel's `LLMProvider` interface over AWS Bedrock, carrying
+the region and credential semantics natively rather than as a base-URL
+override. Installed only if you use it — the kernel has no preferred vendor
+and no driver is a dependency of it.
 
 ## Install
 
@@ -8,7 +38,7 @@ AWS Bedrock LLM provider for [`@namzu/sdk`](https://www.npmjs.com/package/@namzu
 pnpm add @namzu/sdk @namzu/bedrock
 ```
 
-`@namzu/bedrock` declares `@namzu/sdk` as a peer dependency. Install both.
+`@namzu/sdk` is a peer dependency. Install both.
 
 ## Usage
 
@@ -16,67 +46,30 @@ pnpm add @namzu/sdk @namzu/bedrock
 import { ProviderRegistry } from '@namzu/sdk'
 import { registerBedrock } from '@namzu/bedrock'
 
-// Register once at app startup.
-registerBedrock()
+registerBedrock() // once, at startup
 
-// Fully typed via module augmentation: ProviderConfigRegistry['bedrock'].
-const { provider, capabilities } = ProviderRegistry.create({
+const { provider } = ProviderRegistry.create({
   type: 'bedrock',
   region: 'us-east-1',
-  accessKeyId: process.env.AWS_ACCESS_KEY_ID!,
-  secretAccessKey: process.env.AWS_SECRET_ACCESS_KEY!,
 })
 
-const response = await provider.chat({
-  model: 'anthropic.claude-sonnet-4-20250514',
-  messages: [{ role: 'user', content: 'Hello' }],
-})
-```
-
-Streaming:
-
-```ts
 for await (const chunk of provider.chatStream({
-  model: 'anthropic.claude-sonnet-4-20250514',
-  messages: [{ role: 'user', content: 'Tell me a story' }],
+  model: 'us.anthropic.claude-sonnet-4-5-20250929-v1:0',
+  messages: [{ role: 'user', content: 'Hello' }],
 })) {
   if (chunk.delta.content) process.stdout.write(chunk.delta.content)
 }
 ```
 
-## Authentication
-
-Credentials resolve in this order:
-
-1. Explicit `accessKeyId` + `secretAccessKey` (+ optional `sessionToken`) on the config object.
-2. AWS SDK default credential chain — environment variables (`AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, `AWS_SESSION_TOKEN`), shared config/credentials files (`~/.aws/credentials`), IAM role (EC2/ECS/Lambda), SSO profiles.
-
-If you pass neither, the SDK's default chain runs — useful for EC2/ECS/Lambda where the instance role provides credentials automatically.
-
-### Region
-
-Either set `region` on the config or rely on `AWS_REGION` / `AWS_DEFAULT_REGION` env var. Bedrock is region-scoped; Claude and Nova models are available in different regions. See [AWS Bedrock model regions](https://docs.aws.amazon.com/bedrock/latest/userguide/models-regions.html).
-
-### Model access
-
-Bedrock requires explicit model access enablement in the AWS console. Enable the models you plan to call at **AWS Console → Bedrock → Model access → Enable specific models**.
-
-## Capabilities
-
-```ts
-import { BEDROCK_CAPABILITIES } from '@namzu/bedrock'
-
-// {
-//   supportsTools: true,
-//   supportsStreaming: true,
-//   supportsFunctionCalling: true,
-// }
-```
+`chatStream` is the only model entry point; a non-streaming call is that
+stream collected. In practice the kernel's run loop calls it and hands you
+events.
 
-## Observability
+## Documentation
 
-This package ships without observability hooks in `0.1.x`. OpenTelemetry span emission and structured logging are roadmapped for the forthcoming `@namzu/telemetry` package — a separate opt-in dependency that wraps any `LLMProvider` to emit GenAI semantic-convention spans. Track progress in the [Namzu roadmap](https://github.com/cogitave/namzu).
+- [The AWS Bedrock driver — model ids, credentials and prompt caching](https://github.com/cogitave/namzu/blob/main/docs/providers/bedrock.md)
+- [Namzu docs](https://github.com/cogitave/namzu/tree/main/docs)
 
 ## License
 
-FSL-1.1-MIT. Same as `@namzu/sdk`.
+FSL-1.1-MIT, converting to MIT two years after each release.

package/package.json

@@ -1,8 +1,11 @@
 {
   "name": "@namzu/bedrock",
-  "version": "5.0.0",
+  "version": "5.1.0",
   "description": "AWS Bedrock LLM provider for @namzu/sdk. Provides Converse API (chat + streaming) with full tool-use support.",
   "license": "FSL-1.1-MIT",
+  "engines": {
+    "node": ">=20.0.0"
+  },
   "type": "module",
   "homepage": "https://github.com/cogitave/namzu#readme",
   "repository": {
@@ -54,7 +57,7 @@
     "@types/node": "^22.19.17",
     "typescript": "^5.5.0",
     "vitest": "^3.2.6",
-    "@namzu/sdk": "^26.0.0"
+    "@namzu/sdk": "^30.1.0"
   },
   "scripts": {
     "build": "tsc --build",