harnex 0.10.1 → 0.10.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 869ca6ae88939347c40b89586d058fcb64ea2785981155afebcfcb8ffcb7bf4f
-  data.tar.gz: e66e87cc0839ec329a394c9e17ba784e690d094d6ac639232dbc85638c11f9dc
+  metadata.gz: 25ba2b12b69cc6351e2ca4ee1e72e5f378a3828f7486498a2e2a026cf9da771b
+  data.tar.gz: 7e3cc95587c16dcb0a7b9a3e8339546a9ffbe085e4517407f1325e87fd2f45ce
 SHA512:
-  metadata.gz: 6da098e592bd3937ceb378f8cd3c654675c213d3d5c79606a206eb5ddb043dba3e38bc3f05d39e9562add5f2779bd53981ca5a7ba1c17e85e1b9f837f3e59cc3
-  data.tar.gz: 63a34a367fd56167001f530aad631e8f8b17739fd7f209a949847245a68b66b79cef3664cf657918b3fea07c567482d738dbe16aa2773d1f5acd2ccda2a53318
+  metadata.gz: fcaa6d99632c375c1315bfc553b99ccf5c583b58a52e627e0af951493481bf33af9b5de50ca4704a1e6e2d7d9a8aa6999b42d94347ff942b76ac5033eb870dae
+  data.tar.gz: 929011b78aa399cc098b644f0bb2a0995222df71698e450e7ab4785e1be9249e07e4d40225fbf80e02ea9a11f6fefd7913c27682110944ccadacea8f879e7200

data/CHANGELOG.md

@@ -1,8 +1,32 @@
 # Changelog
 
+## [0.10.2] - 2026-08-08 | 06:49 PM | IST
+
+Docs-only patch: no library or CLI behavior changes. Released so the
+packaged `agents-guide` surfaces serve the corrected guidance instead of the
+stale 0.10.1 copies.
+
+### Changed
+
+- `guides/04_monitoring.md`: the Completion Test's clean-tree check now
+  documents excluding the harness-owned dispatch stream
+  (`git status --short -- . ':!.harnex'`) in repos that track
+  `.harnex/dispatch.jsonl`. New anti-patterns: claiming "no live sessions"
+  from memory (finished agents park at prompts — sweep proven-done sessions,
+  then prove with `harnex status`) and failing clean-tree fences on
+  dispatch-stream growth.
+- `docs/dispatch-telemetry.md`: new "Clean-Tree Checks And The Tracked
+  Stream" section — the tracked stream grows mid-run and is harness-owned;
+  fences and worker briefs must exclude it and never revert it.
+
+Context: holm Analysis 803 (queue-process failure meta-analysis). During
+Q107 g2 a worker aborted after misreading dispatch-stream growth as foreign
+dirt, and a coordinator claimed "no live sessions" while 12 completed
+workers sat parked at prompts.
+
 ## [0.10.1] - 2026-08-04 | 12:20 AM | IST
 
-Patch release candidate: closes the recovery and regression-checking gap left
+Patch release: closes the recovery and regression-checking gap left
 after `0.10.0` removed the upstream telemetry mirror. The canonical
 `.harnex/dispatch.jsonl` stream remains the only writer; this release adds
 operator tooling to prove and repair that stream without schema migration.

data/docs/dispatch-telemetry.md

@@ -11,6 +11,16 @@ git repo it is `~/.local/state/harnex/dispatch.jsonl`. `harnex history`,
 `status --id`, and `wait` consume the same rows. Legacy v1 thin rows and
 pre-v2 envelope-less summaries may coexist and remain readable/skippable.
 
+## Clean-Tree Checks And The Tracked Stream
+
+Some repos deliberately track `.harnex/dispatch.jsonl` as project telemetry.
+There the stream grows while sessions run, so worker briefs, completion
+fences, and orchestration clean-tree checks must treat the path as
+harness-owned: expected to be dirty mid-run, never foreign dirt to abort on,
+and never a file a worker should revert or "clean up". Exclude it explicitly,
+for example `git status --porcelain -- . ':!.harnex'`, and commit its growth
+alongside the work it describes.
+
 ## CLI flags
 
 ```text

data/guides/04_monitoring.md

@@ -100,6 +100,17 @@ terminal work signal.
 Adjust the artifact path to the task. The point is to avoid declaring done while
 a worker is between edits or between commits.
 
+In repos that track the dispatch stream (`.harnex/dispatch.jsonl`), exclude it
+from the clean-tree check — harnex appends to it during every run, so it is
+legitimately dirty mid-run:
+
+```bash
+test -z "$(git status --short -- . ':!.harnex')"
+```
+
+Never treat harness-owned telemetry as foreign dirt, and never instruct a
+worker to revert or "clean up" the stream to satisfy a fence.
+
 ## Why Pane State Alone Is Not Enough
 
 Avoid using `state=prompt` or a quiet pane as the only completion signal:
@@ -199,3 +210,8 @@ interpretation.
 - Reading raw tmux panes instead of `harnex pane`.
 - Using `--wait-for-idle` as acceptance proof.
 - Reusing a worker after a failure changes the task scope.
+- Claiming "no live sessions" from memory. Finished agents park at prompts
+  indefinitely; sweep proven-done sessions, then prove the claim with
+  `harnex status`.
+- Failing a clean-tree fence on `.harnex/dispatch.jsonl` growth in repos that
+  track the dispatch stream.

data/lib/harnex/version.rb

@@ -1,4 +1,4 @@
 module Harnex
-  VERSION = "0.10.1"
-  RELEASE_DATE = "2026-08-04"
+  VERSION = "0.10.2"
+  RELEASE_DATE = "2026-08-08"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: harnex
 version: !ruby/object:Gem::Version
-  version: 0.10.1
+  version: 0.10.2
 platform: ruby
 authors:
 - Jikku Jose
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2026-08-03 00:00:00.000000000 Z
+date: 2026-08-08 00:00:00.000000000 Z
 dependencies: []
 description: A local PTY harness that wraps terminal AI agents (Claude, Codex, Pi)
   and adds a control plane for discovery, messaging, and coordination.