@zhivex-ai/harness 1.4.0-rc.8 → 1.4.1

package/CHANGELOG.md

@@ -4,6 +4,38 @@ All notable changes to Zhivex Harness are documented in this file.
 
 The project follows Semantic Versioning. During `0.x`, minor releases may change user-facing contracts when the change is documented with a migration note. Patch releases remain backwards compatible bug fixes.
 
+## Unreleased
+
+- Add provisional Amazon Bedrock and Azure OpenAI routes. Bedrock pins `@zhivex-ai/bedrock@2.0.7` (Converse uses the AWS credential chain and region and reports Tier B; `BEDROCK_RUNTIME=openai` is the Tier A path). Azure OpenAI pins `@zhivex-ai/azure-openai@0.7.8` (https endpoint, API key, optional API version and deployments map). Core is `@zhivex-ai/core@1.34.0`, which those adapters require. An incomplete Bedrock or Azure environment stays out of the durable transport fingerprint. Desktop forwards the selected route's environment credentials through the worker bootstrap. These routes are uncertified: no live calls, no default certification cohort, and no publish or tags.
+- Add an experimental audit pack on `@zhivex-ai/harness/audit`. `zhx export-audit <task-id> --out <directory>` writes one directory per run, or one directory containing every run on a guided task account. The pack reuses the governance report, every approval decision page up to 512 records, the durable redacted activity journal as JSONL, and the usage ledger projection plus transport summary. Approvals, usage, and the governance report come from one captured run snapshot. A change to that run, its journal, or the task account before signing fails with `AUDIT_PACK_STATE_CHANGED` and writes nothing. The 32 MiB limit includes `manifest.json`. `zhx verify-audit --out <directory>` checks the manifest hashes and an HMAC-SHA256 seal without resolving provider, store, or budget configuration. The signing key is `ZHIVEX_AUDIT_SIGNING_KEY` or `--signing-key-file` and is not stored in the pack. Stable root exports, stable declaration signatures, and existing command option contracts are unchanged. This note does not publish a release.
+- Add experimental Code web task definition, bounded exact delivery review, explicit human acceptance, requirement correction, and budgeted continuation through additive host-owned client commands. Keep check verification, human decisions, and provider usage uncertainty distinct. Failed pre-admission continuations retain scoped previous evidence without inventing budget admissions; ordinary chat cannot bypass a governed task's budget.
+- Migration: negotiate `task.control.v1`; existing chat and task projection v1 remain supported. Use matched Code and Harness builds. Native governed tasks require a clean Git baseline, existing bounded tracked files, declared package checks, and explicit token limits. Human acceptance records operator acknowledgement, not measured semantic quality. No store migration, default cap, automatic retry, or release is introduced. See [Code web tasks](docs/CODE_WEB_TASKS.md).
+- Add experimental versioned `task.get` snapshots over the existing client/service protocol. Project deterministic contract, byte, and check evidence separately from semantic and human acceptance, retain authoritative budget uncertainty, and prohibit automatic effect replay. Negotiate `task.projection.v1`; legacy commands and opt-in budget behavior remain compatible. No new store.
+
+## 1.4.1 - 2026-10-15
+
+- Retry a local web reconnect when a command finishes during the durable read, so reconciliation can enable the next session.
+- Keep the Code composer footer readable below 48 columns: model, approval mode and status stay separate clauses and wrap on words.
+- Show a rejected operation as "rejected by you" instead of "operation failed", without echoing the tool name.
+- Show the local web limits dialog, its load and save failures, and the run summary in English, including singular step, tool-call and token counts.
+- Hide the Node 22 ExperimentalWarning for built-in SQLite before the first product line. Other warnings still print.
+- Refuse to start the Harness and Code CLIs when Node is older than engines.node (>=22.13.0), including --help and --version. Bun keeps its own engine check.
+- Describe command reviews as a command that does not run, in the Code terminal and the local web review scope.
+- Pin @zhivex-ai/core 1.33.0 so provider base URLs use the private-host and metadata SSRF checks.
+- Update Anthropic 0.13.2 to 0.14.0, OpenAI 0.14.1 to 0.16.0, and Vertex 1.2.4 to 1.2.7. Vertex 1.2.7 requires those OpenAI and Anthropic ranges. Harness does not call the new experimental Decisions or GPT-Live entrypoints, and provider/API tiers stay unchanged. The development MCP server package moves from 2.2.0 to 2.3.1. Optional `@napi-rs/keyring` moves from 2.1.0 to 2.1.1 in Harness and Code; a missing entry still reads as absent.
+- Prepare Harness 1.4.1 and Code 0.3.1 for npm `latest`, with the exact Code engine pin, private Desktop binding and an additive representative mapping for `v1.4.1` using the unchanged Meta, Qwen and OpenAI models. Retain Agents 1.11.0, Qwen 0.16.4, Meta 0.2.9 and Gemini 0.13.0. Update the ACP development SDK to 1.8.0 and `@types/node` to 26.6.5, and refresh the CodeQL, setup-node, upload-artifact and download-artifact workflow pins. Pause Dependabot updates for private Desktop. Published `latest` is Harness 1.4.0 and Code 0.3.0. Published `next` is Harness 1.4.0-rc.8 and Code 0.3.0-rc.8. `release-status.json` records the verified 1.4.0 publication. The Vertex transient-failure retry and explicit output caps above 2,048 shipped in 1.4.0. This patch does not add them.
+- This preparation creates no tags and dispatches no release.
+
+## 1.4.0 - 2026-10-14
+
+- Published to npm `latest` from annotated `v1.4.0` (`53cdfd338cd33f4786629a30ca7f7a8782ba0ac8`), with Code `0.3.0`. Registry integrity is `sha512-kK8m2jcjwXzbvOQOkf1Uvca/ywJVGsc4dSesGZAui1kskQuTsQg3428RHgHdW9q0ZcQtotMHEsuDp3HucLx8bw==`. The protected release workflow [38633520032](https://github.com/Zhivex/zhivex-harness/actions/runs/38633520032) passed exact-artifact validation and live certification.
+- Classify Vertex and Google transient failures as retryable `PROVIDER_UNAVAILABLE` instead of a generic `EXECUTION_FAILED`. The covered cases are HTTP 409 ABORTED, 429 RESOURCE_EXHAUSTED, 500/502/503/504, UNAVAILABLE, DEADLINE_EXCEEDED, and stream resets. Sanitized diagnostics keep the HTTP status and the closed provider status category, and still omit provider messages, resource names, and credentials. That class, and an empty model turn with no text and no tool call, retries up to three times with jittered backoff in the Vertex driver.
+- Explicit positive integer output caps under a monetary limit, including caps above 2,048, were already in 1.4.0-rc.7 and remain in this release. The ledger reserves 2,048 only when the request omits a cap.
+- Prepare stable Harness 1.4.0 and Code 0.3.0 for npm `latest`, with the exact Code engine pin, private Desktop binding and an additive representative mapping for `v1.4.0` using the unchanged Meta, Qwen and OpenAI models. At preparation time the SDK pins were Core 1.31.0 and Agents 1.11.0. Published `next` stays Harness 1.4.0-rc.8 and Code 0.3.0-rc.8.
+- The published tag is not identical to annotated `v1.4.0-rc.8` (`5bba06c86fc82b34b67cec607053948f8e00d0d1`): `src/` includes the Vertex retry above. Before that retry, engine runtime source matched the rc.8 tag. Code (`packages/code`), web (`packages/web`) and desktop (`desktop`) were already not identical to that tag.
+- Carry the reviewed product changes on main after that tag: the same Code review screen for shell `--continue` and `/pending` ([PR201](https://github.com/Zhivex/zhivex-harness/pull/201)); removal of the desktop fixture waiting button ([PR203](https://github.com/Zhivex/zhivex-harness/pull/203)); B-lite review scope on web and desktop ([PR211](https://github.com/Zhivex/zhivex-harness/pull/211)); the Code status line, one-line summary and 48×24 first-welcome logo ([PR210](https://github.com/Zhivex/zhivex-harness/pull/210)); and the public README ([PR200](https://github.com/Zhivex/zhivex-harness/pull/200)). Packaged Harness docs `README.md` and `docs/CLI.md` differ from the rc.8 tag. `docs/CLI_UX.md` and `docs/images/approval-survives-restart.gif` also differ and are outside the Harness `files` list.
+- Require fresh exact-source/artifact validation and separate explicit approval before any paid campaign, annotated tag or publication. Provider/API tiers remain unchanged. This preparation creates no tags and dispatches no release.
+
 ## 1.4.0-rc.8 - 2026-10-08
 
 - Prepare matched Harness 1.4.0-rc.8 and Code 0.3.0-rc.8 for npm `next`, with the exact Code engine pin, private Desktop binding and an additive representative mapping using unchanged models. Retain the SDK pins already on main (Core 1.31.0, Agents 1.11.0 and the existing provider packages). Stable `latest` stays Harness 1.3.0 and Code 0.2.0.

package/README.md

@@ -1,110 +1,164 @@
-# Zhivex Harness
+# Zhivex Code
 
-**Work on your code with an agent. Review consequential actions before approving them.**
+[![npm @zhivex-ai/code](https://img.shields.io/npm/v/@zhivex-ai/code?label=npm%20%40zhivex-ai%2Fcode)](https://www.npmjs.com/package/@zhivex-ai/code)
+[![CI](https://github.com/Zhivex/zhivex-harness/actions/workflows/ci.yml/badge.svg)](https://github.com/Zhivex/zhivex-harness/actions/workflows/ci.yml)
+[![License: MIT](https://img.shields.io/github/license/Zhivex/zhivex-harness)](LICENSE)
 
-Zhivex Harness is a local terminal assistant and TypeScript library. It supports
-OpenAI, Qwen and Meta, with provisional Gemini, Anthropic and Vertex support. Conversations and pending
-approvals survive restarts.
+An open-source coding agent for your terminal. It asks before it edits or runs a check, and a pending approval is still there after you quit.
 
-Use it to understand a repository, discuss a design, investigate a failure or
-implement a change. Conversation context retains decisions, hypotheses and bounded
-diagnostic excerpts across compaction. Edits and command execution keep their
-own permission checks; a conversational summary never grants approval.
+**Zhivex Code** ([`@zhivex-ai/code`](https://www.npmjs.com/package/@zhivex-ai/code)) is the product you install and run. **Zhivex Harness** ([`@zhivex-ai/harness`](https://www.npmjs.com/package/@zhivex-ai/harness)) is the engine underneath: a governed, provider-portable TypeScript runtime with durable approvals and isolated execution. MIT licensed.
 
-For the developer-facing terminal product, install
-`npm install -g @zhivex-ai/code@0.2.0` and run `zhivex-code` in your project.
-See [Code installation and first use](https://github.com/Zhivex/zhivex-harness/blob/main/packages/code/README.md). Harness remains
-the reusable engine and its compatibility CLI. The `/task` delivery workflow in
-this checkout is an unreleased experimental Code addition, not a published feature.
+## Approval survives a restart
 
-Version `1.3.0` is the current public npm release on `latest`, with terminal-independent engine
-entrypoints and the separately published Code CLI `0.2.0` on `latest`. Harness publication passed registry integrity and provenance verification. Harness `1.4.0-rc.6` and
-Code `0.3.0-rc.6` are published on `next`. Annotated `v1.4.0-rc.7` was tagged but
-not published after live certification failed. The RC.8 versions prepared in this
-checkout remain unpublished. Stable package numbering does
-not change API stability tiers: beta and experimental APIs retain their policies,
-Gemini/Anthropic/Vertex remain provisional, and Desktop remains a private alpha.
+<!-- Recorded with zhivex-code. Scene: ask for a change, review the diff, leave the approval pending, quit,
+     then run `zhivex-code --continue` and show the same approval.
+     Inside the session, `/continue` starts a new run from an interrupted task;
+     the reopen step in this GIF is the `--continue` flag.
+     The file is docs/images/approval-survives-restart.gif. Do not add it to either package `files` list.
+     npm shows the absolute raw URL below. That URL resolves from main. -->
 
-## Quick start
+![Approval survives a restart](https://raw.githubusercontent.com/Zhivex/zhivex-harness/main/docs/images/approval-survives-restart.gif)
+
+## Why it works this way
+
+- **You approve the exact change.** Edits and checks wait for an explicit decision bound to that diff. A conversational summary leaves the change unapproved. If the file changed on your side, import fails closed.
+- **The pending decision survives a restart.** Conversations and approvals are stored in SQLite. Quit the terminal, or reboot, and the same approval is waiting.
+- **Your keys, your provider.** OpenAI, Qwen, and Meta pass the release gate. Gemini, Anthropic, Vertex, Amazon Bedrock, and Azure OpenAI are provisional. The same CLI talks to each of them.
 
-Requires Node.js 22.13.0 or newer, Git and a provider API key.
+## Quick start
 
-Install the stable npm release (`latest`, currently `1.3.0`):
+You need Node.js 22.13 or newer, Git, and a provider API key. Linux and macOS are supported. Windows is unsupported.
 
 ```sh
-npm install -g @zhivex-ai/harness@latest
+npm install -g @zhivex-ai/code
 cd /path/to/your/project
-zhx
+zhivex-code
 ```
 
-On first use, choose a provider and model, then enter your API key in the hidden
-prompt. Save it in the system keychain (macOS/Linux) or use it only for the current
-CLI session. Existing environment keys take precedence. See [First use](docs/FIRST_USE.md)
-and [Credentials](docs/CREDENTIALS.md) for setup and automation.
+On first launch, choose a provider and model. If no key is already available, enter one in the hidden prompt and save it in the system keychain, or keep it for this session only. An existing environment variable takes precedence. The same prompts are documented for the engine command `zhx` in [First use](docs/FIRST_USE.md) and [Credentials](docs/CREDENTIALS.md).
 
 Try: “Explain this repository and suggest a small improvement.”
 
-Type `/` for common actions. `/model` changes the model, `/sessions` finds previous
-conversations, and `/diff` shows changes. Review requested actions before approving
-them. Ctrl+C stops active work; it does not undo completed changes.
+Type `/` for common actions. `/model` changes the model, `/sessions` finds earlier conversations, and `/diff` shows workspace changes. Review each requested action before you approve it. Ctrl+C stops the active run. It leaves completed work in place.
+
+| Command | Purpose |
+| --- | --- |
+| `zhivex-code` | Open the conversation |
+| `zhivex-code --continue` | Reopen the latest conversation. A pending approval opens the review screen |
+| `zhivex-code run "task"` | Run one task for a script |
+| `zhivex-code doctor` | Check local configuration |
+| `zhivex-code --help` | Short guide |
+| `zhivex-code help all` | Full command reference |
+
+`zhivex-code <command> --help` shows one command. Inside the session, `/help` lists everyday actions and `/help all` lists the rest.
+
+### Command names
+
+Each package owns its own commands. Installing both leaves each command in place. Nothing here adds or renames a command.
+
+| Package | Commands |
+| --- | --- |
+| `@zhivex-ai/code` | `zhivex-code` |
+| `@zhivex-ai/harness` | `zhx` and `zhivex-harness` (the same engine CLI), plus `zhx-acp` for the experimental editor protocol |
 
-## Release candidates
+`zhx chat` remains a supported way to open the engine console.
 
-This checkout prepares Harness `1.4.0-rc.8` and Code `0.3.0-rc.8` for `next`, with an exact engine pin. Project memory, compact terminal review and the local browser workspace ship together after protected validation. See the [release procedure](https://github.com/Zhivex/zhivex-harness/blob/main/docs/RELEASE.md). RC.8 publication is pending. It includes the reviewed duplicate-delegation fix on main after RC.7. Published npm `next` is Harness `1.4.0-rc.6` and Code `0.3.0-rc.6`. Annotated `v1.4.0-rc.7` was tagged but not published after Qwen live certification failed; that source and tag cannot certify RC.8. The held RC.5 campaign and failed RC.4 attempt remain preserved. These prerelease candidates are separate from the stable `latest` channel.
+### A pending approval is still there
 
-Use candidates only for prerelease validation. Check [npm versions](https://www.npmjs.com/package/@zhivex-ai/harness?activeTab=versions)
-and the [release procedure](https://github.com/Zhivex/zhivex-harness/blob/main/docs/RELEASE.md)
-before installing a candidate; `next` can still point to an earlier RC.
+Two different actions share the word “continue”:
 
-After publication of this exact candidate:
+| Where | What you type | What happens |
+| --- | --- | --- |
+| Shell, after you quit | `zhivex-code --continue` | Reopens the latest conversation. A pending approval opens the review screen. |
+| Inside the session | `/continue` | Starts a new run from an interrupted task and keeps the earlier results. |
+
+`/continue` is the in-session command. The shell flag that reopens the latest conversation is `--continue`, on `zhivex-code` and on `zhx`. On `zhivex-code`, that screen is `r` Reject, `a` Approve N file(s), `d` Details, and Esc to decide later. A check uses `Approve 1 command` instead of the file label. `/pending` opens the same screen. A new turn waits until you decide. On `zhx`, `--continue` reopens and prints the pending approval; `/pending`, then `/approve` or `/deny`, decides it. `/continue` inside that session starts a new run.
+
+### Try it with no API key
+
+The Code package includes an offline tutorial. It needs an interactive terminal. It makes no provider calls. Responses, token counts, and prices are synthetic.
 
 ```sh
-npm install -g @zhivex-ai/harness@1.4.0-rc.8
+node "$(npm root -g)/@zhivex-ai/code/examples/first-use.mjs"
 ```
 
-## A few commands are enough
+The script prints the guided sequence and a command to reopen the same temporary workspace.
 
-| Command | Purpose |
+### Credentials
+
+| Provider | What the CLI accepts |
 | --- | --- |
-| `zhx` | Open the conversation |
-| `zhx --continue` | Continue the latest conversation |
-| `zhx run "task"` | Run one task for automation |
-| `zhx doctor` | Diagnose local configuration |
-| `zhx --help` | Show the short guide |
+| OpenAI | `OPENAI_API_KEY` |
+| Qwen | `DASHSCOPE_API_KEY` or `QWEN_API_KEY` |
+| Meta | `MODEL_API_KEY` |
+| Gemini (provisional) | `GEMINI_API_KEY` or `GOOGLE_GENERATIVE_AI_API_KEY` |
+| Anthropic (provisional) | `ANTHROPIC_API_KEY` |
+| Vertex (provisional) | Application Default Credentials, plus `GOOGLE_CLOUD_PROJECT` and `VERTEX_LOCATION`. Code does not ask for a Vertex API key. |
+| Amazon Bedrock (provisional) | AWS credential chain plus `AWS_REGION` or `AWS_DEFAULT_REGION`. `BEDROCK_RUNTIME=openai` also needs `BEDROCK_OPENAI_BASE_URL` and `BEDROCK_API_KEY` or `AWS_BEARER_TOKEN_BEDROCK`. |
+| Azure OpenAI (provisional) | `AZURE_OPENAI_API_KEY` and https `AZURE_OPENAI_ENDPOINT`. Optional `AZURE_OPENAI_API_VERSION` and `AZURE_OPENAI_DEPLOYMENTS`. |
 
-Use `zhx <command> --help` for command-specific options, or `zhx help all` for the
-complete reference. Existing `zhx chat` and `zhivex-harness` commands remain supported.
+Use `/credentials` later to replace or remove a saved key. `zhivex-code doctor` reports whether a credential is present. It does not call the provider.
 
-## CLI, library or Desktop?
+## What you can count on
 
-The npm package includes the CLI and TypeScript library. [Desktop](https://github.com/Zhivex/zhivex-harness/blob/main/desktop/README.md)
-is a separate Electron application, currently alpha for macOS Apple Silicon.
-It is not included in npm and has its own build and distribution process. Its local
-package is unsigned and unnotarized; automatic updates are disabled pending production trust setup and validation.
+| | |
+| --- | --- |
+| Approval | Explicit, bound to the exact diff. Per-file changed regions are shown when a preview is available. |
+| Durability | SQLite keeps the conversation and any pending approval across quit and reboot. |
+| Secrets | `.env`, private keys, Git internals, and dependency directories stay out of model exploration. |
+| Commands | The default runtime exposes no shell tools. Isolated commands need an explicitly configured Docker or Podman environment. |
+| Where it runs | On your machine. Linux and macOS. |
 
-## Permissions and limits
+From a source checkout, `bun run demo:hostile` runs a reproducible hostile-repository demo (a malicious README and a decoy `.env`, with network denied). See [Hostile repository demonstration](docs/HOSTILE_REPOSITORY_DEMO.md). That demo needs a local build, Docker or Podman, and a preloaded image.
 
-Edits and checks require approval by default. Files such as `.env`, private keys,
-Git internals and dependency directories are excluded from model exploration.
-The default runtime has no OS isolation and exposes no shell-class tools. Running
-commands in isolation requires an explicitly configured Docker or Podman environment;
-see [Execution environments](docs/EXECUTION_ENVIRONMENTS.md).
+## Providers and platforms
 
-Gemini, [Anthropic](docs/ANTHROPIC.md) and [Vertex](docs/VERTEX.md) remain provisional. See the [support matrix](docs/SUPPORT_MATRIX.md) and
-[security policy](SECURITY.md) for supported configurations and reporting concerns.
+Release-gated providers are OpenAI, Qwen, and Meta. **Gemini, Anthropic, Vertex, Amazon Bedrock, and Azure OpenAI are provisional**: the integrations exist, and they do not yet have the same end-to-end release evidence. Details: [support matrix](docs/SUPPORT_MATRIX.md), [Anthropic](docs/ANTHROPIC.md), [Vertex](docs/VERTEX.md), [Bedrock](docs/BEDROCK.md), [Azure OpenAI](docs/AZURE_OPENAI.md).
+
+| Area | Status |
+| --- | --- |
+| Operating systems | Linux and macOS. Windows is unsupported. |
+| Runtime | Node.js 22.13 or newer. Bun is contributor tooling. |
+| MCP | Bounded Streamable HTTP is supported. stdio is outside the default CLI. An experimental host-only path can launch stdio servers in Docker; see [Isolated MCP stdio](docs/MCP_STDIO.md). |
+| Editor protocol | `zhx-acp` is an experimental ACP subset: text sessions, one-time permissions, and cancellation. Output is buffered until the run finishes. ACP cannot load or resume a session. See [ACP](docs/ACP.md). |
+| Isolated commands | Docker on Linux is supported. Podman is provisional. See [Execution environments](docs/EXECUTION_ENVIRONMENTS.md). |
+| Desktop | Separate private alpha for macOS Apple Silicon. Unsigned, and not part of the npm package. See [Desktop](https://github.com/Zhivex/zhivex-harness/blob/main/desktop/README.md). |
+
+## Use the engine as a library
+
+Code is the terminal product and has no public library API. Harness is the embeddable runtime. Hosts construct it, supply credentials, and resolve approvals:
+
+```ts
+import { createHarness } from "@zhivex-ai/harness/engine";
+import { createHarnessClientAdapter } from "@zhivex-ai/harness/client";
+
+const harness = await createHarness({
+  workspace: "/absolute/path/to/project",
+  provider: "openai",
+  model: "your-supported-model"
+});
+const client = await createHarnessClientAdapter(harness);
+try {
+  // Dispatch with the client protocol. Approve each consequential action explicitly.
+} finally {
+  client.close();
+  await harness.close();
+}
+```
+
+Contracts, stability tiers, and the experimental ACP and MCP entry points are in the [engine API](docs/ENGINE_API.md).
 
 ## Documentation
 
-- **Users:** [First use](docs/FIRST_USE.md), [daily workflow](docs/CLI.md#interactive-daily-workflow), [usage reference](docs/USAGE.md).
-- **Integrators:** [CLI contracts](docs/CLI.md), [extensibility](docs/EXTENSIBILITY.md), [API stability](docs/STABILITY.md).
-- **Contributors:** [Development](https://github.com/Zhivex/zhivex-harness/blob/main/CONTRIBUTING.md) and [maintenance](https://github.com/Zhivex/zhivex-harness/blob/main/docs/MAINTENANCE.md).
+- **Using Code:** [Code package notes](https://github.com/Zhivex/zhivex-harness/blob/main/packages/code/README.md), [first use](docs/FIRST_USE.md), [daily workflow](docs/CLI.md#interactive-daily-workflow), [usage reference](docs/USAGE.md), [Code web tasks](docs/CODE_WEB_TASKS.md).
+- **Integrating Harness:** [engine API](docs/ENGINE_API.md), [CLI contracts](docs/CLI.md), [experimental task projection](docs/CLIENT_PROTOCOL.md#task-projection-v1-har-hu-73), [extensibility](docs/EXTENSIBILITY.md), [API stability](docs/STABILITY.md).
+- **Limits:** [support matrix](docs/SUPPORT_MATRIX.md), [security policy](SECURITY.md).
+- **Contributing:** [development](https://github.com/Zhivex/zhivex-harness/blob/main/CONTRIBUTING.md) and [maintenance](https://github.com/Zhivex/zhivex-harness/blob/main/docs/MAINTENANCE.md).
+
+[Browse the documentation index](docs/README.md).
 
-[Browse documentation](docs/README.md).
+## Releases
 
-Version `1.3.0` is the current public npm release. Source checkout changes can be
-newer than the published package. Consult the [changelog](CHANGELOG.md) and
-[repository release status](https://raw.githubusercontent.com/Zhivex/zhivex-harness/main/release-status.json)
-for the verified 1.3.0 publication; [release evidence](https://github.com/Zhivex/zhivex-harness/blob/main/docs/LIVE_CERTIFICATION.md)
-records validation scope and limitations.
+Version `1.4.0` is the current public npm release. The paired Code package on npm `latest` is `0.3.0`. This checkout prepares Version `1.4.1` and Code `0.3.1` for `latest`. That publication is pending, so the quick start above follows the published `latest` tag. npm `next` is Harness `1.4.0-rc.8` and Code `0.3.0-rc.8`. Confirm dist-tags on the [Code versions](https://www.npmjs.com/package/@zhivex-ai/code?activeTab=versions) and [Harness versions](https://www.npmjs.com/package/@zhivex-ai/harness?activeTab=versions) pages before you install a prerelease.
 
-Experimental next-version work includes [project memory](docs/PROJECT_MEMORY.md): explicit, reviewable notes scoped to one project, with bounded retrieval and deletion controls.
+Release channels, publication, and certification records are in the [release procedure](https://github.com/Zhivex/zhivex-harness/blob/main/docs/RELEASE.md). Releases are verified with npm provenance. Source in this checkout can be newer than the public package. See the [changelog](CHANGELOG.md) and the [repository release status](https://raw.githubusercontent.com/Zhivex/zhivex-harness/main/release-status.json).

package/SECURITY.md

@@ -2,7 +2,7 @@
 
 ## Supported versions
 
-Security fixes are provided for the latest published `1.3.x` patch of Harness and the latest stable Code `0.1.x` patch. RCs on `next` are validation candidates; older minors and private checkpoints are not supported release channels. Desktop remains a separate private alpha. Beta and experimental features retain their documented limitations. Registry integrity and provenance do not substitute for the separate provider and execution evidence recorded in [docs/LIVE_CERTIFICATION.md](https://github.com/Zhivex/zhivex-harness/blob/main/docs/LIVE_CERTIFICATION.md).
+Security fixes are provided for the latest published `1.3.x` patch of Harness and the latest stable Code `0.2.x` patch. Harness `1.4.x` and Code `0.3.x` are supported only after verified publication. RCs on `next` are validation candidates; older minors and private checkpoints are not supported release channels. Desktop remains a separate private alpha. Beta and experimental features retain their documented limitations. Registry integrity and provenance do not substitute for the separate provider and execution evidence recorded in [docs/LIVE_CERTIFICATION.md](https://github.com/Zhivex/zhivex-harness/blob/main/docs/LIVE_CERTIFICATION.md).
 
 ## Reporting a vulnerability
 

package/SUPPORT.md

@@ -1,6 +1,6 @@
 # Support
 
-Zhivex Harness `1.3.x` is the latest supported Node-first CLI and TypeScript library. Stable 1.x contracts follow [the stability policy](./docs/STABILITY.md); incompatible changes require a major release except documented urgent security corrections. Beta and experimental surfaces retain their declared policies. The mutable machine-readable `release-status.json` record records the verified 1.3.0 publication. Harness 1.3.0 and Code 0.1.0 are published and verified on latest through their protected workflows.
+Zhivex Harness `1.3.x` is the latest supported Node-first CLI and TypeScript library. Stable 1.x contracts follow [the stability policy](./docs/STABILITY.md); incompatible changes require a major release except documented urgent security corrections. Beta and experimental surfaces retain their declared policies. The mutable machine-readable `release-status.json` record records the verified 1.3.0 publication. Harness 1.4.1 and Code 0.3.1 are prepared for latest but remain pending their protected workflows. Harness 1.3.0 and Code 0.2.0 stay the published latest packages.
 
 The 1.1 support scope is tracked in the [machine-readable support matrix](./docs/support-matrix-1.1.json) and its [human-readable view](./docs/SUPPORT_MATRIX_1_1.md). The [1.0 matrix](./docs/SUPPORT_MATRIX.md) remains historical. Compatibility and removals follow [DEPRECATIONS.md](./docs/DEPRECATIONS.md) for the published 1.x line.
 
@@ -13,7 +13,7 @@ The 1.1 support scope is tracked in the [machine-readable support matrix](./docs
 - the provider/model combinations marked certified in the package documentation; and
 - HTTPS or explicitly allowed loopback-HTTP MCP endpoints using the documented bounded JSON-RPC subset.
 
-Only the most recent published stable minor receives routine fixes. The exact `v1.3.0` tag passed the protected artifact, six-provider live and 42-case representative release jobs. Harness 1.3.x and Code 0.1.x are the supported stable lines. Gemini, Anthropic and Vertex remain provisional despite the release-bound live gates; the representative repository matrix covers only Meta, Qwen and OpenAI. Live provider evidence is account-, model-, endpoint-, artifact-, and date-dependent; see [docs/LIVE_CERTIFICATION.md](https://github.com/Zhivex/zhivex-harness/blob/main/docs/LIVE_CERTIFICATION.md).
+Only the most recent published stable minor receives routine fixes. The exact `v1.3.0` tag passed the protected artifact, six-provider live and 42-case representative release jobs. Harness 1.3.x and Code 0.2.x are the supported stable lines until 1.4.1 and Code 0.3.1 complete verified publication. Gemini, Anthropic and Vertex remain provisional despite the release-bound live gates; the representative repository matrix covers only Meta, Qwen and OpenAI. Live provider evidence is account-, model-, endpoint-, artifact-, and date-dependent; see [docs/LIVE_CERTIFICATION.md](https://github.com/Zhivex/zhivex-harness/blob/main/docs/LIVE_CERTIFICATION.md).
 
 ## Installation diagnostics