@zhivex-ai/harness 1.4.0-rc.1 → 1.4.0-rc.6

package/CHANGELOG.md

@@ -4,11 +4,52 @@ 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.
 
+## 1.4.0-rc.6 - 2026-10-05
+
+- Prepare matched Harness 1.4.0-rc.6 and Code 0.3.0-rc.6 for npm `next`, with the exact Code engine pin, private Desktop binding and an additive representative mapping using unchanged models and SDK pins.
+- Include the reviewed activity projection fix from PR185: compact bounded UI snapshot previews without failing valid runs, preserve run identities/statuses and truncation markers, and split already-redacted streamed text into bounded Unicode-safe events. Durable policy/event journals, retention limits and approval authority are unchanged.
+- Preserve the held RC.5 campaign and immutable tag/source. Its passing offline, live and 42/42 representative evidence belongs to the older artifact and does not certify RC.6. Keep the RC.4 failure history and SDK store migration requirements.
+- Require fresh exact-source/artifact validation and separate explicit approval before any paid campaign, annotated tag or publication. Stable `latest` channels and provider/API tiers remain unchanged.
+
+## 1.4.0-rc.5 - 2026-10-05
+
+- Prepare matched Harness 1.4.0-rc.5 and Code 0.3.0-rc.5 for npm `next`, with the exact engine pin, Desktop binding and a new representative mapping using unchanged models and SDK pins.
+- Include the reviewed inherited-pipe termination regression correction: account for the existing cleanup grace and verify that the descendant heartbeat stops. Production termination protections are unchanged.
+- Carry the reviewed Desktop lucide-react 1.50.0 update from main. Keep Desktop private alpha and retain all provider and API tiers.
+- Preserve the immutable RC.4 tag and its failed offline campaign. Require a new exact artifact, unchanged protected gates and separate approval for any new paid campaign or publication.
+
+The RC.4 SDK store migration requirements below still apply.
+
+## 1.4.0-rc.4 - 2026-10-05
+
+- Integrate published Core 1.30.1, Agents 1.10.3, Anthropic 0.13.2, OpenAI 0.14.1, Qwen 0.16.4 and Vertex 1.2.4. Keep Meta 0.2.9 and Gemini 0.13.0; align Code and browser contributor pins and retain a single Core runtime in Harness.
+- Prepare matched Harness 1.4.0-rc.4 and Code 0.3.0-rc.4 for npm `next`, with an exact engine pin, Desktop binding and a new representative mapping using unchanged models. Retain immutable RC.2/RC.3 evidence and all protected gates.
+- Preserve Core 1.30.1 canonical identities and memory envelopes through backup/import, retaining verified legacy runs and rejecting mismatched identities. Finalize cooperative cancellation after the worker drains so session reads do not strand at `cancel_requested`.
+- Record bounded continuity response shape, streamed event counts and usage for the next failed phase without retaining provider text. This does not identify or resolve the historical RC.3 Meta cause.
+
+- Extend experimental task acceptance to bounded native reviewed edits and declared package-script checks, tying receipts to selected/protected file digests and the manifest. Block other effect tools and delegation for native task runs. Preserve the separate SDK run status and pending human review.
+- Add a redacted recorded-check projection to beta run-result JSON and experimental Code host helpers. Stable declaration snapshots and Harness run/session/backup schemas are unchanged.
+- Carry forward Meta SDK 0.2.9 reasoning usage as a subset of output tokens, without adding it again to totals.
+
+Migration: stop all workers sharing an SDK store and upgrade them together, keeping a complete backup. Core 1.30.1 uses canonical identities for new runs; verified legacy runs retain their physical keys. Older workers cannot resolve new identities. Legacy default SDK memory without verified ownership requires explicit offline migration; do not rewrite IDs/scopes to bypass validation. See [SDK store migration](https://github.com/Zhivex/zhivex-ai-sdk/blob/4a93004395a80c183b1257bb1d02fb3a3d4050e1/docs/maintainers/AGENT_STORE_MIGRATION.md). Runs without a task contract retain their behavior. Native task contracts now enforce their edit/check tool scope and may report `pending_review`/`verified` when their watched-file requirements pass; they do not receive OCI sandbox, whole-snapshot or import guarantees. Check evidence remains invalid after watched-file drift or uncertain journal recovery.
+
+## 1.4.0-rc.3 - 2026-10-04
+
+- Retain finite stage, assertion and provider-route identities in mixed-routing release diagnostics, preserve typed operational causes across artifact class boundaries, and keep cleanup failures from masking the original gate failure. Add offline fault coverage; historical release evidence remains unchanged.
+
+- Prepare matched Harness 1.4.0-rc.3 and Code 0.3.0-rc.3 for npm `next`, preserving the complete certification workflow, model pins and provider support tiers. Keep RC.2 tags, retained artifacts and failed evidence immutable; RC.3 requires fresh source-bound artifact, OCI, live and representative gates.
+
+## 1.4.0-rc.2 - 2026-10-04
+
+- Recover bounded prior assistant reports and plans through `read_task` after local session compaction, including immediate manual compaction of the first report and continued sessions after reconnect or host restart. Keep recovered text untrusted and separate from operator requests, approvals and acceptance evidence.
+
+- Prepare the matched Harness 1.4.0-rc.2 and Code 0.3.0-rc.2 for npm `next`, retaining exact engine pins, historical model mappings and provider support tiers. Publication requires new release-bound artifact, OCI, live and representative gates.
+
 ## 1.4.0-rc.1 - 2026-10-04
 
 - Add experimental, project-scoped operator memory in the existing SQLite memory table, with explicit corrections/deletion, reviewed suggestions, provenance, freshness and bounded per-request retrieval.
 - Add local `memory` commands and `--no-memory` to Harness/Code without terminal layout changes. Curated mode stops automatic last-assistant capture; the stable engine default and explicit SDK memory integrations remain supported.
-- Preserve old state and import compatibility; document active deletion versus separately retained histories/backups and next-release engine pairing. See [Project memory](docs/PROJECT_MEMORY.md). The candidate is not yet published.
+- Preserve old state and import compatibility; document active deletion versus separately retained histories/backups and next-release engine pairing. See [Project memory](docs/PROJECT_MEMORY.md). Published to npm `next` on 2026-10-04.
 
 - Pair with Code 0.3.0-rc.1 for compact terminal flow, pageable approval review and the local browser workspace with packaged assets. Publish Harness first to `next`; preserve stable `latest`.
 

package/README.md

@@ -11,22 +11,27 @@ implement a change. Conversation context retains decisions, hypotheses and bound
 diagnostic excerpts across compaction. Edits and command execution keep their
 own permission checks; a conversational summary never grants approval.
 
+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.
+
 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 RC7 and
-Code RC2 remain published on `next`. Stable package numbering does
+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.1` and
+Code `0.3.0-rc.1` are published on `next`. The RC.6 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.
 
-This checkout prepares Harness `1.4.0-rc.1` and Code `0.3.0-rc.1` 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). The candidates are not yet published.
-
 ## Quick start
 
 Requires Node.js 22.13.0 or newer, Git and a provider API key.
 
-After RC publication, install the candidate below. Until then, use npm `latest` for stable Harness 1.3.0:
+Install the stable npm release (`latest`, currently `1.3.0`):
 
 ```sh
-npm install -g @zhivex-ai/harness@1.4.0-rc.1
+npm install -g @zhivex-ai/harness@latest
 cd /path/to/your/project
 zhx
 ```
@@ -42,6 +47,20 @@ Type `/` for common actions. `/model` changes the model, `/sessions` finds previ
 conversations, and `/diff` shows changes. Review requested actions before approving
 them. Ctrl+C stops active work; it does not undo completed changes.
 
+## Release candidates
+
+This checkout prepares Harness `1.4.0-rc.6` and Code `0.3.0-rc.6` 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.6 publication is pending. It includes the reviewed bounded activity snapshot fix; RC.5 remains held and its source/tag cannot be reused for this fix. The failed RC.4 attempt and immutable source are preserved; npm `next` currently points to Harness `1.4.0-rc.1` and Code `0.3.0-rc.1`. These prerelease candidates are separate from the stable `latest` channel.
+
+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.
+
+After publication of this exact candidate:
+
+```sh
+npm install -g @zhivex-ai/harness@1.4.0-rc.6
+```
+
 ## A few commands are enough
 
 | Command | Purpose |

package/contracts/engine-api.json

@@ -2715,6 +2715,26 @@
           "name": "readRegularFileNoFollow",
           "kind": "runtime",
           "tier": "experimental"
+        },
+        {
+          "name": "resolvePackageCheckCommand",
+          "kind": "runtime",
+          "tier": "experimental"
+        },
+        {
+          "name": "nativeTaskSnapshot",
+          "kind": "runtime",
+          "tier": "experimental"
+        },
+        {
+          "name": "TASK_ACCEPTANCE_EVIDENCE_KEY",
+          "kind": "runtime",
+          "tier": "experimental"
+        },
+        {
+          "name": "checkEvidence",
+          "kind": "runtime",
+          "tier": "experimental"
         }
       ]
     },

package/dist/acp-cli.js

@@ -12,20 +12,20 @@ import {
 import {
   createHarness,
   createHarnessClientAdapter
-} from "./index-4nf70nq1.js";
-import"./index-aqe7236b.js";
-import"./index-g0wfcb65.js";
+} from "./index-4j1h4j8c.js";
+import"./index-rd0s3gqj.js";
+import"./index-a1q355va.js";
 import {
   usagePricingSchema
-} from "./index-ds5e9x3a.js";
-import"./index-fm6ahk8m.js";
-import"./index-z0qxmkm2.js";
+} from "./index-vtqfjnab.js";
+import"./index-0g939pfs.js";
+import"./index-e6r04a18.js";
 import {
   FileChangedWhileReadingError,
   FileSizeLimitError,
   UnsafeFileTypeError,
   readRegularFileNoFollow
-} from "./index-yb239ghk.js";
+} from "./index-r0tdj04h.js";
 import {
   HARNESS_REQUIRED_CAPABILITIES,
   HARNESS_SUBAGENT_PROFILES,

package/dist/{cli-entry-645q3vwx.js → cli-entry-4k1cf0m3.js}

@@ -427,7 +427,7 @@ Use zhx help all for the full reference and exit codes.`;
 // package.json
 var package_default = {
   name: "@zhivex-ai/harness",
-  version: "1.4.0-rc.1",
+  version: "1.4.0-rc.6",
   description: "Governed, provider-portable runtime for coding agents with durable approvals and isolated repository execution.",
   type: "module",
   license: "MIT",
@@ -632,22 +632,22 @@ var package_default = {
     "smoke:mcp:installed": "bun run build && bun scripts/mcp-installed-smoke.ts"
   },
   dependencies: {
-    "@zhivex-ai/agents": "1.10.2",
-    "@zhivex-ai/anthropic": "0.13.1",
-    "@zhivex-ai/core": "1.28.0",
+    "@zhivex-ai/agents": "1.10.3",
+    "@zhivex-ai/anthropic": "0.13.2",
+    "@zhivex-ai/core": "1.30.1",
     "@zhivex-ai/gemini": "0.13.0",
-    "@zhivex-ai/meta": "0.2.8",
-    "@zhivex-ai/openai": "0.13.7",
-    "@zhivex-ai/qwen": "0.16.3",
-    "@zhivex-ai/vertex": "1.2.2",
+    "@zhivex-ai/meta": "0.2.9",
+    "@zhivex-ai/openai": "0.14.1",
+    "@zhivex-ai/qwen": "0.16.4",
+    "@zhivex-ai/vertex": "1.2.4",
     "google-auth-library": "11.1.0",
     zod: "4.6.5"
   },
   overrides: {
-    "@zhivex-ai/core": "1.28.0"
+    "@zhivex-ai/core": "1.30.1"
   },
   devDependencies: {
-    "@agentclientprotocol/sdk": "1.5.1",
+    "@agentclientprotocol/sdk": "1.7.0",
     "@modelcontextprotocol/server": "2.2.0",
     "@types/bun": "1.4.2",
     "@types/node": "^26.6.3",