@arnilo/prism 0.0.5 → 0.0.6

package/docs/providers/zai.md

@@ -1,62 +1,85 @@
-# ZAI provider package
+# Z.AI provider package
 
 ## What it does
 
-`@arnilo/prism-provider-zai` provides explicit, side-effect-free setup for the ZAI GLM
-API-key provider using Prism's OpenAI-compatible route with the
-`thinkingFormat: "zai"` model-compat setting, developer-role fallback, and
-GLM tool-stream quirks.
+`@arnilo/prism-provider-zai` provides explicit, side-effect-free setup for the Z.AI
+GLM Chat Completions API (`POST /chat/completions`) with official deep-thinking,
+reasoning-effort, and tool-stream request fields.
 
-The package registers a provider, default model metadata, and an `api_key` auth
-method through `createExtensionKernel().load([...])`.
+The package registers a provider, featured GLM model metadata, and an `api_key`
+auth method through `createExtensionKernel().load([...])`.
 
 ## When to use it
 
-Use it when a host app wants to run the ZAI GLM endpoint through Prism's
-`AgentSession` runtime with ZAI-specific thinking/tool-stream handling.
+Use it when a host app wants to run Z.AI GLM models through Prism's
+`AgentSession` runtime with official `thinking` / `reasoning_effort` /
+`tool_stream` mapping and implicit context caching.
 
-Do not use it for automatic credential discovery, catalog fetches, or
+Do not use it for automatic credential discovery, setup-time catalog fetches, or
 real-network tests.
 
 ## Inputs / request
 
 ```ts
-import { createZaiProviderPackage } from "@arnilo/prism-provider-zai";
+import {
+  createZaiProviderPackage,
+  defineZaiModel,
+  listZaiModels,
+} from "@arnilo/prism-provider-zai";
 
 createZaiProviderPackage(options: ZaiProviderPackageOptions): ProviderPackage
-defineZaiModel(config: ZaiModelConfig): ZaiModelConfig
+defineZaiModel(config: ZaiModelConfig): ModelConfig
+listZaiModels(options?: ListZaiModelsOptions): Promise<ModelConfig[]>
 ```
 
 | Field | Type | Purpose |
 | --- | --- | --- |
 | `apiKey` | `CredentialValueSource` | Direct/callback/resolver API-key source. |
 | `fetch` | `typeof fetch` | Optional fetch implementation for tests/hosts. |
-| `baseUrl` | `string` | Overrides the ZAI base URL. |
+| `baseUrl` | `string` | Overrides the Z.AI base URL (default `https://api.z.ai/api/paas/v4`). |
 | `id` | `string` | Overrides the provider id (default `zai`). |
-| `models` | `readonly ModelConfig[]` | Overrides `zaiModels` defaults. |
+| `models` | `readonly ModelConfig[]` | Overrides featured `zaiModels` defaults. |
 
-`ModelConfig.compat.thinkingFormat: "zai"` enables ZAI thinking handling;
-`developerRoleFallback` controls developer-role fallback.
+### Thinking / reasoning compat
+
+Official body fields (request `options.compat` wins over `model.compat`):
+
+| Compat / body field | Wire shape | Notes |
+| --- | --- | --- |
+| `thinking` | `boolean` or `{ type: "enabled" \| "disabled", clear_thinking?: boolean }` | Boolean `true`/`false` maps to `{ type: "enabled" }` / `{ type: "disabled" }`. |
+| `reasoning_effort` | string | GLM-5.2+: `max` (default) \| `xhigh` \| `high` \| `medium` \| `low` \| `minimal` \| `none`. |
+| `tool_stream` | boolean | GLM-4.6+: stream tool-call argument deltas (`false` by API default; featured 4.6+ models opt in). |
+| `clear_thinking` | boolean | Nested into `thinking.clear_thinking`. Default on the API is `true` (drop prior reasoning). Set `false` for Preserved Thinking. |
+| `preserveThinking` | boolean | Prism-local: when true (or when `clear_thinking: false`), replay prior thinking blocks as assistant `reasoning_content`. |
+
+`ProviderRequestOptions.cacheRetention: "none"` forces `thinking: { type: "disabled" }`.
+
+Shared Prism helpers (`applyThinkingLevel` / `thinkingFamilyForModel`) map portable
+levels into the `reasoning_effort` family for Z.AI; hosts can also set
+`thinking.type` directly for enable/disable.
 
 ## Outputs / response / events
 
 | Surface | Behavior |
 | --- | --- |
-| Provider stream | Prism text, thinking (preserved only when `model.compat.preserveThinking` is true, otherwise downgraded to text), tool-call delta/final, `usage`, `done`, redacted `error`. |
-| Block preservation | Text, thinking, assistant `tool_call` → `tool_calls`, `tool_result` → role `tool` messages, images when `capabilities.input` includes `"image"`. |
+| Provider stream | Prism text, thinking (`delta.reasoning_content`), tool-call delta/final, `usage`, `done`, redacted `error`. |
+| Block preservation | Text; thinking → `reasoning_content` when Preserved Thinking is active (otherwise dropped, never flattened into text); assistant `tool_call` → `tool_calls`; `tool_result` → role `tool`; images when `capabilities.input` includes `"image"`. |
 | Auth method | `api_key` for the configured provider id, credential name `apiKey`. |
 
 Unsupported block placements or unclaimed images fail before fetch.
 
 ## Request/response example
 
-Example request body (OpenAI-compatible Chat Completions shape):
+Example request body (official Chat Completions shape):
 
 ```json
 {
-  "model": "glm-4.6",
+  "model": "glm-5.2",
   "messages": [{ "role": "user", "content": "Hello" }],
-  "stream": true
+  "stream": true,
+  "thinking": { "type": "enabled" },
+  "reasoning_effort": "max",
+  "tool_stream": true
 }
 ```
 
@@ -64,63 +87,89 @@ Example request body (OpenAI-compatible Chat Completions shape):
 
 ```ts
 import { createExtensionKernel } from "@arnilo/prism";
-import { createZaiProviderPackage } from "@arnilo/prism-provider-zai";
+import { createZaiProviderPackage, listZaiModels } from "@arnilo/prism-provider-zai";
 
 const kernel = createExtensionKernel();
 await kernel.load([createZaiProviderPackage({ apiKey: "fake-zai-key" })]);
+
+// Optional caller-gated discovery (never runs during package setup):
+const live = await listZaiModels({ apiKey: "fake-zai-key" });
+await kernel.load([createZaiProviderPackage({ apiKey: "fake-zai-key", models: live })]);
 ```
 
-Override the provider id and models:
+Per-turn thinking override:
 
 ```ts
-import { createZaiProviderPackage, defineZaiModel, zaiModels } from "@arnilo/prism-provider-zai";
-
-await kernel.load([
-  createZaiProviderPackage({ id: "zai", apiKey: "fake", models: zaiModels }),
-]);
+await session.prompt("Plan the refactor", {
+  providerOptions: {
+    compat: {
+      thinking: { type: "enabled", clear_thinking: false },
+      reasoning_effort: "high",
+      tool_stream: true,
+    },
+  },
+});
 ```
 
 ## Extension and configuration notes
 
-- Hosts choose base URL, provider id, model list, credential source, and `fetch`
-  impl.
-- `defineZaiModel` lets apps set ZAI-specific `compat` (thinking format, developer
-  fallback).
-- Package contributes models via the extension `api` and an `api_key` auth method.
+- Default base URL is the official international endpoint
+  `https://api.z.ai/api/paas/v4`. Hosts targeting China can pass
+  `baseUrl: "https://open.bigmodel.cn/api/paas/v4"`. Coding Plan hosts may use
+  `https://api.z.ai/api/coding/paas/v4`.
+- Featured `zaiModels` are offline bootstrap aliases (`glm-5.2`, `glm-5.1`,
+  `glm-5`, `glm-5-turbo`, `glm-4.7`, `glm-4.6`, `glm-4.5`) curated from the
+  official Chat Completions model enum and overview context sizes.
+- `listZaiModels()` is caller-gated OpenAI-compatible `GET /models` discovery
+  (not a first-class docs.z.ai list page). Setup never fetches.
+- `defineZaiModel` sets Z.AI-specific `compat` (`thinking`, `reasoning_effort`,
+  `tool_stream`, `clear_thinking`, `preserveThinking`).
 
 ### Cache behavior
 
 - Z.AI GLM models use **implicit context caching**: the server caches prompt
   prefixes automatically based on request content, with no explicit request-side
   cache payload. Catalog models declare `cache: { kind: "implicit" }`.
+- Official docs: hits appear in `usage.prompt_tokens_details.cached_tokens`.
 - The provider sends no `cache_control`, `prompt_cache_key`, `prompt_cache_retention`,
   or other explicit cache-control fields regardless of `ProviderRequestOptions.cache`
   / `cacheKey` / `cacheRetention` settings — those options have no effect on the
-  Z.AI request body. Hosts relying on cache hits should keep their stable prompt
-  prefix byte-stable and stable inputs unchanged.
-- Usage accounting is preserved: `prompt_tokens_details.cached_tokens` maps to
-  `Usage.cacheReadTokens` and `prompt_tokens_details.cache_write_tokens` maps to
-  `Usage.cacheWriteTokens` when the server reports them.
+  Z.AI request body (except `cacheRetention: "none"` disabling thinking).
+- Usage accounting: `prompt_tokens_details.cached_tokens` → `Usage.cacheReadTokens`
+  and `prompt_tokens_details.cache_write_tokens` → `Usage.cacheWriteTokens` when
+  the server reports them.
 
 ## Security and performance notes
 
-- SSE streams and HTTP error bodies use bounded `@arnilo/prism/providers/transport` helpers (`readSseData`, `readBoundedResponseText`).
+- SSE streams and HTTP error bodies use bounded `@arnilo/prism/providers/transport`
+  helpers (`readSseData`, `readBoundedResponseText`).
 - No network calls during import, setup, build, or default tests.
 - No automatic environment, file, keychain, or shell credential lookup.
 - API keys are resolved per request from caller-supplied values or resolvers and
-  redacted from errors.
+  redacted from errors (including discovery failures).
 - Caller-supplied `ProviderRequest.options.headers` can add non-owned headers,
   but provider-owned headers (`content-type`, `authorization`) are applied last
   and cannot be overridden by caller headers.
-- Live tests stay opt-in behind `PRISM_LIVE_PROVIDER_TESTS=1` plus fake-safe
-  provider-specific env names; default tests are network-free.
+- Live tests stay opt-in behind `PRISM_LIVE_PROVIDER_TESTS=1` plus `ZAI_API_KEY`;
+  default tests are network-free.
 
 ## Related APIs
 
 - [Provider packages](../provider-packages.md): `defineProviderPackage`,
-  `ModelConfig`/`compat`, thinking formats.
+  caller-gated discovery, per-turn thinking.
+- [Thinking and reasoning](../thinking-and-reasoning.md): portable
+  `applyThinkingLevel` → Z.AI `reasoning_effort` / `thinking.type`.
 - [Credentials and redaction](../credentials-and-redaction.md):
   `resolveCredentialValue`, `redactSecrets`.
-- [OpenAI-compatible provider](openai-compatible.md): underlying Chat Completions
-  adapter.
+- [Provider caching](../provider-caching.md): implicit GLM context caching.
 - [Provider conformance](../provider-conformance.md): network-free adapter tests.
+
+## Official evidence
+
+- [Deep Thinking](https://docs.z.ai/guides/capabilities/thinking)
+- [Thinking Mode](https://docs.z.ai/guides/capabilities/thinking-mode) (Preserved Thinking / `clear_thinking`)
+- [Tool Streaming](https://docs.z.ai/guides/capabilities/stream-tool)
+- [Context Caching](https://docs.z.ai/guides/capabilities/cache)
+- [Chat Completion](https://docs.z.ai/api-reference/llm/chat-completion)
+- [Migrate to GLM-5.2](https://docs.z.ai/guides/overview/migrate-to-glm-new)
+- [Models overview](https://docs.z.ai/guides/overview/overview)

package/docs/release-and-install.md

@@ -6,9 +6,9 @@ Prism is published as one core package, twenty-three first-party capability pack
 
 Core package:
 
-- `@arnilo/prism` — the runtime, contracts, registries, streaming events, CLI (including `prism init`), and the `/docs` hub. `files`: `dist` (with `!dist/__tests__` and `!dist/**/*.map` negations), `docs`, `templates`, `CHANGELOG.md`. `bin`: `prism` -> `./dist/cli.js`. `sideEffects`: `["dist/cli.js"]`.
+- `@arnilo/prism` — the runtime, contracts, registries, streaming events, CLI (including `prism init`), and the `/docs` hub. `files`: `dist` (with `!dist/__tests__` and `!dist/**/*.map` negations), `docs`, `templates`, `CHANGELOG.md`. `bin`: `prism` -> `dist/cli.js`. `sideEffects`: `["dist/cli.js"]`.
 
-First-party workspace packages (each has non-optional `@arnilo/prism@0.0.5` peer and `sideEffects: false`; RAG also peers on memory, and server also peers on workflows):
+First-party workspace packages (each has non-optional `@arnilo/prism@0.0.6` peer and `sideEffects: false`; RAG also peers on memory, and server also peers on workflows):
 
 - `@arnilo/prism-provider-openai`, `@arnilo/prism-provider-openrouter`, `@arnilo/prism-provider-kimi`, `@arnilo/prism-provider-zai`, `@arnilo/prism-provider-opencode-go`, `@arnilo/prism-provider-neuralwatt` — provider adapters.
 - `@arnilo/prism-provider-ai-sdk` — optional AI SDK `LanguageModelV4` adapter; included by the provider and all umbrellas.
@@ -36,7 +36,7 @@ Family/profile packages (pure manifests, no code or `dist`; ship `README.md` and
 - `@arnilo/prism-sdk` — base + workflows + MCP + Node credentials + OpenTelemetry; providers and persistence remain explicit choices.
 - `@arnilo/prism-all` — every first-party package: code + SDK + providers + persistence + evals + memory/RAG + server + supervisor. Installation alone activates no network/listener, telemetry, database, memory, evaluation, delegation, MCP, shell, or filesystem capability.
 
-Profile footprint snapshot (Node 24/npm 11, lockfile graph, 2026-07-16): `base` reaches 6 first-party packages and one external dependency root (Ajv); `code` reaches 10 and three (Ajv, MCP SDK, diff); `sdk` reaches 11 and three (Ajv, MCP SDK, keyring); `all` reaches all 30 first-party manifests and seven external roots (those plus better-sqlite3, pg, and AI SDK provider types). Native database drivers stay out of base/code/sdk; both appear only in all.
+Profile footprint snapshot (Node 24/npm 11, lockfile graph, 2026-07-19): `base` reaches 6 first-party packages and one external dependency root (Ajv); `code` reaches 10 and three (Ajv, MCP SDK, diff); `sdk` reaches 11 and three (Ajv, MCP SDK, keyring); `all` reaches all 30 first-party manifests and seven external roots (those plus better-sqlite3, pg, and AI SDK provider types). Native database drivers stay out of base/code/sdk; both appear only in all.
 
 Each code package's `files` array is `["dist", "!dist/__tests__", "!dist/**/*.map", "README.md", "CHANGELOG.md"]`; `README.md`, `LICENSE`, and `CHANGELOG.md` ship in every code-package tarball, the core tarball also ships the `docs/` directory, and family/profile tarballs ship `README.md` + `CHANGELOG.md` + `package.json`.
 
@@ -62,9 +62,9 @@ Consumers install the core package for the runtime and add first-party packages
 | Run the default (network-free) test suite | `npm test` |
 | Dry-run pack core + every package | `npm run pack:dry-run` |
 | Local mirror of the release verify gate | `npm run release:dry-run` |
-| Validate clean tag/version/ranges and reject registry collisions | `npm run release:check -- --version 0.0.5` |
-| Preview deterministic publish order | `npm run release:publish -- --version 0.0.5 --dry-run --allow-dirty --allow-untagged` |
-| Resume interrupted tagged publication | `npm run release:publish -- --version 0.0.5 --resume --report release-artifacts/publish-report.json` |
+| Validate clean tag/version/ranges and reject registry collisions | `npm run release:check -- --version 0.0.6` |
+| Preview deterministic publish order | `npm run release:publish -- --version 0.0.6 --dry-run --allow-dirty --allow-untagged` |
+| Resume interrupted tagged publication | `npm run release:publish -- --version 0.0.6 --resume --report release-artifacts/publish-report.json` |
 | Full SDK readiness gate (typecheck + offline tests + pack) | `npm run sdk:ready` |
 
 Public core import specifiers (from the root `exports` map):
@@ -101,7 +101,7 @@ A packed tarball contains only public compiled output and release files:
 - Code packages ship `README.md`, `LICENSE`, and `CHANGELOG.md`; family/profile packages ship `README.md` and `CHANGELOG.md`.
 - The core tarball additionally ships the full `docs/` directory (the docs hub) and `templates/init/` used by `prism init`.
 - `dist/cli.js` and the `bin` link in core.
-- **Tarball filenames.** npm strips the `@scope/` prefix, so the core package `@arnilo/prism` produces a tarball named `arnilo-prism-0.0.5.tgz`; first-party packages produce `arnilo-prism-provider-<name>-0.0.5.tgz` / `arnilo-prism-compaction-<name>-0.0.5.tgz` / `arnilo-prism-coding-agent-0.0.5.tgz`; family/profile packages produce `arnilo-prism-{providers,compaction,base,code,sdk,all}-0.0.5.tgz`. The CLI bin name `prism` is unaffected by the package name (`npx prism` still works; npm allows the bin field to differ from the package name).
+- **Tarball filenames.** npm strips the `@scope/` prefix, so the core package `@arnilo/prism` produces a tarball named `arnilo-prism-0.0.6.tgz`; first-party packages produce `arnilo-prism-provider-<name>-0.0.6.tgz` / `arnilo-prism-compaction-<name>-0.0.6.tgz` / `arnilo-prism-coding-agent-0.0.6.tgz`; family/profile packages produce `arnilo-prism-{providers,compaction,base,code,sdk,all}-0.0.6.tgz`. The CLI bin name `prism` is unaffected by the package name (`npx prism` still works; npm allows the bin field to differ from the package name).
 
 Excluded from every tarball by `files` negation:
 
@@ -120,9 +120,9 @@ Excluded from every tarball by `files` negation:
   "name": "host-app",
   "type": "module",
   "dependencies": {
-    "@arnilo/prism": "0.0.5",
-    "@arnilo/prism-provider-openai": "0.0.5",
-    "@arnilo/prism-compaction-observational-memory": "0.0.5"
+    "@arnilo/prism": "0.0.6",
+    "@arnilo/prism-provider-openai": "0.0.6",
+    "@arnilo/prism-compaction-observational-memory": "0.0.6"
   }
 }
 ```
@@ -132,7 +132,7 @@ Installing the provider/compaction packages without `@arnilo/prism` present prod
 ```text
 npm error code ERESOLVE
 npm error Could not resolve dependency:
-npm error peer @arnilo/prism@"0.0.5" from @arnilo/prism-provider-openai@0.0.5
+npm error peer @arnilo/prism@"0.0.6" from @arnilo/prism-provider-openai@0.0.6
 ```
 
 ## Implementation example
@@ -165,11 +165,11 @@ For SDK readiness, run the same one-command gate directly. It composes existing
 npm run sdk:ready
 ```
 
-Release publication derives all 30 packages from the workspace once, validates exact `0.0.5` manifest/lockfile/internal ranges, then uses deterministic dependency order. `release:check` requires a clean commit tagged `v0.0.5` and rejects any existing registry version. `release:publish --resume` skips only registry versions whose internal dependency fingerprint matches the local manifest; conflicting versions fail closed. Each attempted package is written immediately to the JSON report, so a failed job can rerun safely. `--dry-run` still performs registry availability checks and invokes `npm publish --dry-run` with explicit public access, provenance, and `latest` tag.
+Release publication derives all 30 packages from the workspace once, validates exact `0.0.6` manifest/lockfile/internal ranges, then uses deterministic dependency order. `release:check` requires a clean commit tagged `v0.0.6` and rejects any existing registry version. `release:publish --resume` skips only registry versions whose internal dependency fingerprint matches the local manifest; conflicting versions fail closed. Each attempted package is written immediately to the JSON report, so a failed job can rerun safely. `--dry-run` still performs registry availability checks and invokes `npm publish --dry-run` with explicit public access, provenance, and `latest` tag.
 
 ```bash
-npm run release:check -- --version 0.0.5
-npm run release:publish -- --version 0.0.5 --dry-run --allow-dirty --allow-untagged
+npm run release:check -- --version 0.0.6
+npm run release:publish -- --version 0.0.6 --dry-run --allow-dirty --allow-untagged
 ```
 
 `--allow-dirty` and `--allow-untagged` exist only for local preview; real publication and CI never pass them. npm registry calls occur only in these release preflight/publication commands, never build/test/package discovery.
@@ -180,7 +180,7 @@ Optional live smoke tests stay separate from SDK readiness because they require
 PRISM_LIVE_PROVIDER_TESTS=1 npm run test --workspaces --if-present
 ```
 
-### 0.0.5 publish handoff
+### 0.0.6 publish handoff
 
 **Decision: GO after operator prerequisites below.** Code, tests, package graph, live PostgreSQL, registry availability, packed artifacts, and dependency-ordered publication dry-run passed from the Phase 14 working tree. Clean protected-branch CI, signed commit/tag, npm authentication, OIDC attestation, and actual publication remain operator/workflow prerequisites. No package was published during readiness work.
 
@@ -190,7 +190,7 @@ The existing GitHub Actions secret `NPM_TOKEN` is used only by the publish step
 
 #### Release commit and tag
 
-Merge through the protected release branch, then run these commands from a clean checkout of the protected merge commit. `git push origin v0.0.5` is the workflow dispatch; there is no manual publish command.
+Merge through the protected release branch, then run these commands from a clean checkout of the protected merge commit. `git push origin v0.0.6` is the workflow dispatch; there is no manual publish command.
 
 ```bash
 # Prepare and push the release commit.
@@ -199,22 +199,22 @@ npm ci
 npm run sdk:ready
 git add -A
 git diff --cached --check
-git commit -S -m "Release 0.0.5"
+git commit -S -m "Release 0.0.6"
 git push origin HEAD
 
 # Merge/confirm protected branch CI, then check out that exact clean merge commit.
 test -z "$(git status --porcelain)"
 npm ci
-npm run release:check -- --version 0.0.5 --allow-untagged --report /tmp/prism-0.0.5-preflight.json
+npm run release:check -- --version 0.0.6 --allow-untagged --report /tmp/prism-0.0.6-preflight.json
 
-git tag -s v0.0.5 -m "Prism 0.0.5"
-git verify-tag v0.0.5
-test "$(git rev-parse HEAD)" = "$(git rev-list -n 1 v0.0.5)"
-npm run release:check -- --version 0.0.5 --report /tmp/prism-0.0.5-tagged-preflight.json
-git push origin v0.0.5
+git tag -s v0.0.6 -m "Prism 0.0.6"
+git verify-tag v0.0.6
+test "$(git rev-parse HEAD)" = "$(git rev-list -n 1 v0.0.6)"
+npm run release:check -- --version 0.0.6 --report /tmp/prism-0.0.6-tagged-preflight.json
+git push origin v0.0.6
 ```
 
-The tag workflow's only publication command is `npm run release:publish -- --version "${GITHUB_REF_NAME#v}" --resume --report release-artifacts/publish-report.json`. Latest registry preflight returned `available` for all 30 `0.0.5` versions. Publisher order is stable and dependency-safe:
+The tag workflow's only publication command is `npm run release:publish -- --version "${GITHUB_REF_NAME#v}" --resume --report release-artifacts/publish-report.json`. Latest registry preflight returned `available` for all 30 `0.0.6` versions. Publisher order is stable and dependency-safe:
 
 ```text
  1 @arnilo/prism
@@ -251,7 +251,7 @@ The tag workflow's only publication command is `npm run release:publish -- --ver
 
 #### Interruption and resume
 
-Do not create another tag or rerun packages manually. Re-run failed jobs for the same tag in GitHub Actions. The workflow invokes `release:publish --resume`: registry versions with matching names, versions, and internal dependency fingerprints are skipped; any mismatch stops the job. Retain `release-artifacts-v0.0.5` and `publish-report-v0.0.5` for audit.
+Do not create another tag or rerun packages manually. Re-run failed jobs for the same tag in GitHub Actions. The workflow invokes `release:publish --resume`: registry versions with matching names, versions, and internal dependency fingerprints are skipped; any mismatch stops the job. Retain `release-artifacts-v0.0.6` and `publish-report-v0.0.6` for audit.
 
 #### Bounded post-publish smoke
 
@@ -259,9 +259,9 @@ Download the workflow artifact and run `sha256sum -c SHA256SUMS`. Then verify al
 
 ```bash
 while read -r package; do
-  test "$(npm view "$package@0.0.5" version)" = "0.0.5"
-  test "$(npm view "$package" dist-tags.latest)" = "0.0.5"
-  npm view "$package@0.0.5" dist.integrity >/dev/null
+  test "$(npm view "$package@0.0.6" version)" = "0.0.6"
+  test "$(npm view "$package" dist-tags.latest)" = "0.0.6"
+  npm view "$package@0.0.6" dist.integrity >/dev/null
 done <<'PACKAGES'
 @arnilo/prism
 @arnilo/prism-coding-agent
@@ -297,7 +297,7 @@ PACKAGES
 consumer="$(mktemp -d)"
 cd "$consumer"
 npm init -y >/dev/null
-npm install --no-audit --no-fund @arnilo/prism-all@0.0.5
+npm install --no-audit --no-fund @arnilo/prism-all@0.0.6
 node --input-type=module <<'NODE'
 for (const name of [
   "@arnilo/prism", "@arnilo/prism-coding-agent", "@arnilo/prism-coding-security",
@@ -319,14 +319,14 @@ This smoke is bounded to registry metadata, imports, CLI startup, checksums, sig
 
 #### Rollback limitations
 
-npm publication is not transactional and published versions are immutable. Partial publication is a resume case, not rollback. For a confirmed systemic defect after completion, deprecate every affected `@0.0.5`; restore `latest` to `0.0.3` only for the 13 previously published packages, and remove `latest` from the 11 first-publication packages. Exact `0.0.5` installs remain possible, so publish a fixed version promptly. Do not unpublish except for a security/legal emergency under npm policy.
+npm publication is not transactional and published versions are immutable. Partial publication is a resume case, not rollback. For a confirmed systemic defect after completion, deprecate every affected `@0.0.6`; restore `latest` to `0.0.3` only for the 13 previously published packages, and remove `latest` from the 11 first-publication packages. Exact `0.0.6` installs remain possible, so publish a fixed version promptly. Do not unpublish except for a security/legal emergency under npm policy.
 
 ## Extension and configuration notes
 
-- **Required `@arnilo/prism` peer.** Every first-party package declares `peerDependencies: { "@arnilo/prism": "0.0.5" }` with no `peerDependenciesMeta` (non-optional). The range stays pinned to `0.0.5` for the 0.x series and will widen to `^1.0.0` at the 1.x stable release. Inside the workspace each package also declares `"@arnilo/prism": "file:../.."` in `devDependencies` so `npm install` resolves the peer locally; that devDependency is stripped from consumer installs and is not a runtime dependency.
+- **Required `@arnilo/prism` peer.** Every first-party package declares `peerDependencies: { "@arnilo/prism": "0.0.6" }` with no `peerDependenciesMeta` (non-optional). The range stays pinned to `0.0.6` for the 0.x series and will widen to `^1.0.0` at the 1.x stable release. Inside the workspace each package also declares `"@arnilo/prism": "file:../.."` in `devDependencies` so `npm install` resolves the peer locally; that devDependency is stripped from consumer installs and is not a runtime dependency.
 - **Public access.** All 30 manifests (24 code packages + 6 family/profile packages) declare `"publishConfig": { "access": "public" }`; the publisher also passes `--access public` explicitly because scoped packages otherwise default to restricted on first publish.
 - **Map retention knob.** Source maps are emitted locally but stripped from tarballs by `!dist/**/*.map`. Removing that `files` negation ships maps in releases (larger tarballs, better consumer stack traces).
-- **Release workflow.** `.github/workflows/release.yml` has four jobs. `verify` runs the full SDK readiness gate on Node 24: `npm ci`, then `npm run sdk:ready` (`npm run typecheck`, network-free `npm test`, and `npm run pack:dry-run`). `node20-compat` runs on Node 20: `npm ci`, `npm run build`, then imports every public root `exports` default target from `dist/`. This proves published-package basics under declared `engines.node >=20` without docs examples, which require Node >=22.6 native TypeScript stripping. `postgres-integration` runs the PostgreSQL suite against `pgvector/pgvector:pg16`. `publish` runs only for exact `v*` tags after all three gates, checks clean/tagged state and the complete 0.0.5 graph, then publishes in topological order through `scripts/release.mjs`. The existing `NPM_TOKEN` GitHub secret is exposed only to the publish step; `id-token: write` also enables OIDC where configured. npm receives `--provenance --access public --tag latest`; no credential value is placed in source or output. Before publishing, CI packs all 30 tarballs, generates `SHA256SUMS`, and retains both pack manifests and artifacts for 30 days. Registry state is the resume journal: matching published packages are skipped, mismatches stop publication, and an incremental package-status report is also retained for 30 days. Local `npm run release:dry-run` delegates to `npm run sdk:ready`; local PostgreSQL coverage is `PRISM_TEST_POSTGRES_URL=... npm run test:postgres`.
+- **Release workflow.** `.github/workflows/release.yml` has four jobs. `verify` runs the full SDK readiness gate on Node 24: `npm ci`, then `npm run sdk:ready` (`npm run typecheck`, network-free `npm test`, and `npm run pack:dry-run`). `node20-compat` runs on Node 20: `npm ci`, `npm run build`, then imports every public root `exports` default target from `dist/`. This proves published-package basics under declared `engines.node >=20` without docs examples, which require Node >=22.6 native TypeScript stripping. `postgres-integration` runs the PostgreSQL suite against `pgvector/pgvector:pg16`. `publish` runs only for exact `v*` tags after all three gates, checks clean/tagged state and the complete 0.0.6 graph, then publishes in topological order through `scripts/release.mjs`. The existing `NPM_TOKEN` GitHub secret is exposed only to the publish step; `id-token: write` also enables OIDC where configured. npm receives `--provenance --access public --tag latest`; no credential value is placed in source or output. Before publishing, CI packs all 30 tarballs, generates `SHA256SUMS`, and retains both pack manifests and artifacts for 30 days. Registry state is the resume journal: matching published packages are skipped, mismatches stop publication, and an incremental package-status report is also retained for 30 days. Local `npm run release:dry-run` delegates to `npm run sdk:ready`; local PostgreSQL coverage is `PRISM_TEST_POSTGRES_URL=... npm run test:postgres`.
 - **Adding a package.** New workspace packages are picked up automatically by `npm run build --workspaces`, `npm test --workspaces`, `npm run pack:dry-run`, the packaging guard (`src/__tests__/packaging.test.ts`), and the install-smoke test (`src/__tests__/install-smoke.test.ts`) via the workspace glob; add the package to both tests' config arrays for explicit per-package assertions.
 
 ## Security and performance notes
@@ -349,29 +349,27 @@ npm publication is not transactional and published versions are immutable. Parti
 - **Install smoke is offline.** The install-smoke test packs core + every package into a temp dir and installs tarballs with `--offline --no-audit --no-fund` into a fresh project. External dependencies are satisfied from the lockfile-backed npm cache prepared by `npm ci`; any attempted uncached registry fetch fails the gate.
 - **Offline test budget.** The default `npm test` (no `PRISM_LIVE_PROVIDER_TESTS`) is pinned at **< 60s on Node 20** with a measured local baseline of ~45s (build ~18s + network-free tests/workspace tests/packaging smoke ~27s). The full CI `sdk:ready` gate runs on Node 24 because docs tests execute `examples/*.ts` via native TypeScript stripping. `npm run sdk:ready` also runs typecheck and pack dry-run, so it is allowed to exceed the `npm test` budget while remaining network-free. The CI `sdk:ready` step has `timeout-minutes: 5` as a hang backstop; the separate Node 20 compatibility step has `timeout-minutes: 3`. The budget was raised from 30s after the default suite grew to include every first-party package, offline install smoke, packaging guards, docs examples, and workspace tests; optimize before raising it again.
 
-### 0.0.5 dependency audit decision (2026-07-14)
+### 0.0.6 dependency audit decision (2026-07-19)
 
-`npm audit --audit-level=high` reports 0 vulnerabilities and `npm ls --all` is clean. Lockfile registry entries all carry integrity hashes and resolved registry URLs; direct/runtime dependency licenses are permissive. `@types/node` was updated within its declared Node 22 range from 22.19.21 to 22.20.1. No runtime dependency changed.
+`npm audit --audit-level=high` reports 0 vulnerabilities and `npm ls --all --depth=0` resolves the exact 30-package `0.0.6` graph. No Phase 1 dependency was added. Native `better-sqlite3` remains the sole install-script dependency and stays in the opt-in SQLite package.
 
-Major updates are deliberately deferred from this feature release: `diff` 8.0.4 → 9 requires coding-tool compatibility review, TypeScript 5.9.3 → 7 requires compiler/output review, and `@types/node` 22 → 26 would exceed the project's Node 20 support target. Revisit each in a dedicated dependency update after 0.0.5; none addresses a current audit finding. Native `better-sqlite3` is the sole dependency with an install hook and remains isolated in the opt-in SQLite package.
+### 0.0.6 release-candidate verification — 2026-07-19
 
-### 0.0.5 release-candidate verification — 2026-07-16
-
-Phase 14 validation ran from the current working tree without creating a release commit/tag or publishing. Clean protected-branch/tag checks remain mandatory in the handoff above.
+Phase 1 validation ran from this working tree without creating a release commit/tag or publishing. Clean protected-branch/tag checks remain mandatory in the handoff above.
 
 | Gate | Result |
 | --- | --- |
-| Node 24 full matrix | `npm test` 32.247 s; `npm run sdk:ready` 70.560 s; 1,618 tests (1,593 pass, 25 explicit live skips, 0 fail). The `< 60s` default-test budget and 5-minute SDK hang backstop hold. |
-| Node 20 compatibility | Node 20.20.2 imported all 44 built root/package export targets. CI repeats build + root public imports from a clean checkout. |
-| PostgreSQL | Fresh `pgvector/pgvector:pg16` container; 29 session/run/feedback/checkpoint/lease/memory/pgvector checks passed with 0 skips/failures. |
-| Packed consumer | All 30 exact 0.0.5 tarballs installed together; every root subpath/code package imported. Public packed composition covers streaming, fake AI SDK, eval/feedback, memory/RAG, durable approval, schedules/replay, server/MCP, and supervisor/A2A offline. Generated `prism init` project installs packed core, typechecks, and tests. |
-| Artifact contents | All 30 dry-run packs pass with 699 files. Follow-up umbrella snapshot: ~690.6 kB packed / 2.64 MB unpacked total; core ~403.7 kB / 1.46 MB / 221 files; `prism-providers` 1,370 / 3,540 B / 3 files; `prism-all` 1,556 / 3,561 B / 3 files. CI regenerates exact manifests/checksums after the release commit. Denied tests/maps/source/plans/internal artifacts are absent. |
-| Registry and order | Live public-registry preflight reports all 30 `@arnilo/*@0.0.5` versions available. Dependency-ordered `release:publish --dry-run` completed 30/30 and retained JSON status/order; no publish occurred. |
-| Supply chain | `npm audit --audit-level=high`: 0 vulnerabilities; `npm ls --all`: clean. CycloneDX 1.5 SBOM has 181 components and no prohibited licenses. MIT/ISC/BSD/Apache-family licenses only. `better-sqlite3` is the sole install-script package and remains isolated behind opt-in SQLite. All 30 SHA-256 tarball checksums re-verify; extracted tarball token/private-key scan has 0 hits. |
-| Provenance | Dry-run used explicit public/latest/provenance arguments. Signed npm provenance attestation is intentionally generated only by real OIDC publication from the clean signed `v0.0.5` tag workflow. |
-| Deferred live smokes | No provider API credentials, OS keychain gate, or external A2A endpoint was configured. Their tests remain explicit opt-in; offline conformance is authoritative for this release candidate. |
-
-Pack manifests, SBOM, checksums, registry report, and dry-run publish report were generated under `/tmp/prism-p14-release`; CI recreates and retains release artifacts rather than committing generated files.
+| Node 24 full matrix | `npm run sdk:ready` passed inside its five-minute backstop: 1,767 tests (1,742 pass, 25 explicit live skips, 0 fail), full typecheck/build, docs/export/install-smoke tests, and 30 dry-run packs. |
+| Node 20 compatibility | Docker Node 20.20.2 built all workspaces and imported every public root export target. |
+| PostgreSQL | Fresh `pgvector/pgvector:pg16` container: 17 session-store plus 14 memory/pgvector checks passed with 0 skips/failures. |
+| Packed consumer | Offline install-smoke packed all 30 exact `0.0.6` tarballs into a fresh consumer, imported public surfaces, ran packed integration/composition journeys, and ran the generated `prism init` project. |
+| Artifact contents | All 30 dry-run packs passed; core is 230 files, 445.5 kB packed, and 1.6 MB unpacked. Packaging guards reject tests, maps, source, plans, internal artifacts, and real-looking secrets. |
+| Registry and order | Public-registry preflight found all 30 `@arnilo/*@0.0.6` versions available. Dependency-ordered `release:publish --dry-run` completed 30/30 with explicit public/latest/provenance arguments; no publish occurred. Core uses npm's valid `bin` path form `dist/cli.js`. |
+| Supply chain | `npm audit --audit-level=high`: 0 vulnerabilities. `npm ls --all --depth=0`: clean. |
+| Provenance | Signed npm provenance is generated only by real OIDC publication from the clean signed `v0.0.6` tag workflow. |
+| Deferred live smokes | No provider credentials or external A2A endpoint were configured. `PRISM_TEST_KEYCHAIN=1` found no working system-keychain backend (native read returned no value after write); run that explicit round-trip on the release host before publication. |
+
+The temporary PostgreSQL container and local dry-run report are not release artifacts. CI recreates and retains package manifests, checksums, and the publication report.
 
 ## Release checklist