@zhivex-ai/harness 1.2.0-rc.5 → 1.2.0-rc.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -4,6 +4,31 @@ All notable changes to Zhivex Harness are documented in this file.
4
4
 
5
5
  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.
6
6
 
7
+ ## 1.2.0-rc.8 - 2026-09-26
8
+
9
+ - Include durable child and descendant OCI snapshots in parent completion checks. Report `OCI_CHILD_DELIVERY_PENDING` when a delegated edit has not reached the host; missing descendant state fails closed without requesting an import from the wrong workspace.
10
+
11
+ - Prevent OCI runs from completing while edits remain only in their isolated snapshot. Detect pending delivery from actual host contents and modes, including resumed runs and command-created edits. Allow at most two read-only completion reminders, preserve import approvals and refusals, and persist an explicit incomplete-delivery result when delivery cannot finish.
12
+ - Report pending OCI delivery separately from verifier failures in representative release diagnostics.
13
+
14
+ - Prepare fresh exact-artifact certification for RC8. RC7 failed the Meta representative matrix before publication; its tag and evidence remain unchanged. Local Meta regression evidence does not replace certification of the new candidate.
15
+
16
+ ## 1.2.0-rc.7 - 2026-09-26
17
+
18
+ - Split live approval/resume diagnostics into receipt count, tool success, file read/content, and journal count/status checkpoints. Include bounded receipt and journal counters without tool arguments, file contents or provider output. Preserve every release acceptance assertion and the unpublished RC6 failure evidence.
19
+
20
+ - Prepare fresh exact-artifact certification for RC7 with the same Meta contributor, Qwen Flash and OpenAI Luna cohort. RC6 failed its base live gate before publication; its tag and evidence remain unchanged.
21
+
22
+ ## 1.2.0-rc.6 - 2026-09-26
23
+
24
+ - Deduplicate identical unsigned Qwen reasoning summaries against their streamed text before context accounting, including restored sessions. Preserve distinct, signed, and encrypted provider data.
25
+ - Treat the compaction threshold as a target that must fit the newest indivisible interaction, while keeping transport and run budgets authoritative. Validate repeated compaction followed by a real file edit and executable check.
26
+ - Guide scoped implementation toward editing once the relevant code and check are known; clarify exact tool names and dependency lookup paths to avoid repeated blocked discovery.
27
+
28
+ - Render pipe-delimited Markdown tables as aligned, wrapped terminal grids, with stacked cells on narrow terminals and Unicode-aware widths. Preserve plain redirected output and terminal-control sanitization.
29
+ - Keep Meta Responses conversation history locally with `store: false` and encrypted reasoning replay, instead of depending on `previous_response_id` availability. Resume existing sessions from retained messages and tool receipts without rerunning completed tools; older turns without encrypted reasoning retain their visible history only.
30
+ - Allow two bounded receipt-only continuation backoffs (1s and 2s) for legacy stateful requests. Add generate/stream replay regressions and an opt-in live check for encrypted replay across model instances.
31
+
7
32
  ## 1.2.0-rc.5 - 2026-09-26
8
33
 
9
34
  - Adapt the assistant loop to explanation, investigation, design and implementation without imposing a repair ceremony on read-only work. Remove the `strict`/`repair` runtime profile choice; callers requiring verified completion use `requireVerifiedDelivery` or `--require-verified-delivery` directly. This is an intentional pre-promotion API/CLI break; saved connection profiles and subagent roles remain independent.
package/README.md CHANGED
@@ -11,12 +11,12 @@ implement a change. Conversation context retains decisions, hypotheses and bound
11
11
  diagnostic excerpts across compaction. Edits and command execution keep their
12
12
  own permission checks; a conversational summary never grants approval.
13
13
 
14
- Version `1.2.0-rc.5` is prepared as an unpublished release candidate for npm `next`,
14
+ Version `1.2.0-rc.8` is prepared as an unpublished release candidate for npm `next`,
15
15
  with console, local service and governed delegation improvements. Certification
16
16
  and publication remain pending. The
17
17
  [repository release status](https://raw.githubusercontent.com/Zhivex/zhivex-harness/main/release-status.json)
18
18
  preserves historical stable evidence. The installation commands below target
19
- 1.2.0-rc.5 once published; stable users can install `@zhivex-ai/harness@latest`.
19
+ 1.2.0-rc.8 once published; stable users can install `@zhivex-ai/harness@latest`.
20
20
  Desktop retains its separate private alpha status.
21
21
 
22
22
  ## Quick start
@@ -24,7 +24,7 @@ Desktop retains its separate private alpha status.
24
24
  Requires Node.js 22.13.0 or newer, Git and a provider API key.
25
25
 
26
26
  ```sh
27
- npm install -g @zhivex-ai/harness@1.2.0-rc.5
27
+ npm install -g @zhivex-ai/harness@1.2.0-rc.8
28
28
  cd /path/to/your/project
29
29
  zhx
30
30
  ```
@@ -165,7 +165,7 @@
165
165
  },
166
166
  {
167
167
  "name": "createHarness",
168
- "sha256": "sha256:5ac9e360ce7d0260b5205fc549bc76ee17d8c1ce1f370b343485caeaeb65d712"
168
+ "sha256": "sha256:587e0ddcd2294c92ef9d1f2d4c4b15d3344183c5bcc34f5ceccf763a17d11f66"
169
169
  },
170
170
  {
171
171
  "name": "createHarnessMcpTools",
@@ -173,7 +173,7 @@
173
173
  },
174
174
  {
175
175
  "name": "createHarnessOciExecutionEnvironment",
176
- "sha256": "sha256:6a62e4a6befffc36d8f702c45a0a833fdb62b6eaf64bf28a13200fc30dafd8c4"
176
+ "sha256": "sha256:c4f8f25e3a78c2bcbdf4a6a2238e4afd2e80cf14bc91c414874088126d6f92cc"
177
177
  },
178
178
  {
179
179
  "name": "createHarnessStateBackup",
@@ -273,7 +273,7 @@
273
273
  },
274
274
  {
275
275
  "name": "runHarness",
276
- "sha256": "sha256:f266ec6259ad47f209e5be97f03c15ce0e9a6f6649d0eda1647825cc68f1aae7"
276
+ "sha256": "sha256:713a8a62198f1ab9d96b7f071084021895538259b2ef504dcb9dc37a341812d2"
277
277
  },
278
278
  {
279
279
  "name": "serializeStreamEvent",
@@ -487,8 +487,8 @@
487
487
  },
488
488
  {
489
489
  "name": "ZhivexHarness",
490
- "sha256": "sha256:236fa1dd85851bf31083217eb72318a871645be8548486c829ba79d2a1a0933e"
490
+ "sha256": "sha256:e244fbf6f5df2c07e247b6df7810fca4e53a92046940c3e327ecd5d5224deee3"
491
491
  }
492
492
  ],
493
- "digest": "sha256:7dd369f0c3163b628a2907c3ec092d88892d3f7ae11385c802fb0197e2f28629"
493
+ "digest": "sha256:540d453617592b39457b2412085b041193a0336c70e16f9f54d5ef81a264dce3"
494
494
  }