harnex 0.7.5 → 0.7.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4c6173057b1fe4fa547979d3d9803f345acb4e658dd942aefa096ef886727c33
-  data.tar.gz: da1662c9dce791ae644aa4a0ea57d2124a1698593e6db98b2ac737d9f42816f6
+  metadata.gz: f29114f723ccfc61ade344c784cb6a11144c25e79392bf136f5b722473b47f0b
+  data.tar.gz: 810686487788509887bb8bfb5f9a4c45a8a1b8bca645530b1bf178f1435cee40
 SHA512:
-  metadata.gz: e2758cfa10fc9b221235efea20ff21be32b5558c1ab06eb4515cea5485be96e1371d663735c826d9587833caa46aed65486b5c3cedfe8ce3be04e7ac1c328f7f
-  data.tar.gz: 765cf4ef020f3a7cfa8bbd1aad517ac1b4ec8901579b3720ea618ec246b20009c07c088d4d86e354ead78194844bba771790df0271d54fccecad6f6058874d9f
+  metadata.gz: 90c68832ab9218716fd2e6181f006a12b996a23c28b120a769411618aee35e507c38df43bcf9293a98fb3902923e70eb1be9e08a90795e9ec970cb5b51ca2b54
+  data.tar.gz: 64ebab38e3cf716bfe69fd7f8d1b28c0d114ef72e81f8028cb87f0b83f6a75cb555e1036a7831a41b3dddd156c0b9f71e51fa9550271f5be529dcea1fd23c9e1

data/CHANGELOG.md

@@ -2,6 +2,24 @@
 
 ## [Unreleased]
 
+## [0.7.6] - 2026-06-09 | 12:59 AM | IST
+
+### Added
+
+- `harnex status --json` now exposes work-level completion fields (`done`,
+  `work_state`, and `process_state`) so monitors can distinguish completed
+  work from a still-live interactive process.
+- `harnex wait --until done` waits for `task_complete` or terminal exit,
+  whichever arrives first, giving queue monitors a safe default fence.
+
+### Changed
+
+- Refreshed README quick-start and monitoring guidance to emphasize
+  `--context --auto-stop`, `--until task_complete` for interactive structured
+  sessions, durable terminal summaries, and timeout/artifact verification.
+- Monitoring, buddy, and recipe examples now gate unattended work on
+  `--until done` / `done` / `work_state` instead of `state=completed` alone.
+
 ## [0.7.5] - 2026-05-26 | 05:18 PM | IST
 
 ### Added

data/README.md

@@ -33,16 +33,24 @@ or project-local docs are required.
 ## What it does
 
 ```bash
-# Start an agent in tmux
-harnex run pi --id planner --tmux planner
+# Start a visible one-shot worker, give it a task, and stop on completion
+harnex run pi --id planner --tmux planner \
+  --context "Write a plan to /tmp/plan.md" --auto-stop
 
-# Send it a task and wait for it to finish
-harnex send --id planner --message "Write a plan to /tmp/plan.md" --wait-for-idle
+# Wait for the work-level completion signal and terminal telemetry
+harnex wait --id planner --until done --timeout 900
 
-# Peek at what it's doing
-harnex pane --id planner --lines 30
+# Inspect the final state or the recent dispatch history
+harnex status --id planner --json
+harnex history --limit 5
+```
+
+For a long-lived interactive session, keep the worker open and send work to it:
 
-# Stop it
+```bash
+harnex run pi --id planner --tmux planner
+harnex send --id planner --message "Write a plan to /tmp/plan.md" --wait-for-idle
+harnex pane --id planner --lines 30
 harnex stop --id planner
 ```
 
@@ -59,8 +67,9 @@ job, watch it work, stop it when done.
   tmux-backed terminal, `harnex logs` tails the persisted transcript, and
   `harnex events` streams structured JSONL lifecycle events.
 
-- **You don't want to babysit.** Send a task with `--wait-for-idle`,
-  walk away, check back when it's done.
+- **You don't want to babysit.** Use `--context --auto-stop` for
+  one-shot work, `--watch` for bounded stall recovery, or
+  `--wait-for-idle` as a send fence.
 
 - **You want local-only orchestration.** Everything runs on your
   machine. No cloud services, no API keys beyond what the agents need.
@@ -169,6 +178,30 @@ bare `--watch` means babysitter mode.
 For one-shot startup prompts, add `--auto-stop`. It requires `--context`
 and stops the session after the first task completion or PTY prompt return.
 
+## Completion and waiting
+
+Choose the wait predicate that matches how you launched the worker:
+
+- `harnex wait --id ID --until done --timeout SECS` is the safest unattended
+  work fence. It returns when Harnex sees `task_complete` or a terminal exit,
+  whichever comes first.
+- `harnex wait --id ID` waits for the wrapped process to exit. This is right
+  for already-exited sessions and terminal-summary recovery, but interactive
+  agents can stay open after finishing a turn.
+- For structured Pi RPC and Codex app-server sessions, use
+  `harnex wait --id ID --until task_complete --timeout SECS` when you need the
+  exact turn-completion event instead of terminal-exit fallback.
+- `harnex send --wait-for-idle` is an atomic send fence for PTY-style
+  interactions. It proves the turn returned to an idle/prompt state, not that
+  your acceptance criteria passed.
+- `harnex status --id ID --json` can report `running`, `completed`, `failed`,
+  or `unknown` from durable terminal summary rows even after the live registry
+  is gone. Treat `state` as process/session state; use `done` and `work_state`
+  as the work-level monitor contract.
+
+Always set a timeout for unattended waits and verify the expected artifact,
+tests, or git state after harnex reports completion.
+
 For structured subscriptions, stream JSONL events:
 
 ```bash
@@ -183,7 +216,9 @@ Schema details and compatibility policy are documented in
 Every finished `harnex run` writes dispatch records. In a git repo, the
 default path is `<repo>/.harnex/dispatch.jsonl`; outside a git repo, the
 compact history record falls back to `~/.local/state/harnex/dispatch.jsonl`.
-`harnex history` reads the compact records from that location.
+`harnex history` reads the compact records from that location, and
+`harnex status --id ID --json` / `harnex wait` can use the same durable
+terminal summaries when the live session registry is already gone.
 
 Use `harnex history` to inspect it:
 
@@ -274,14 +309,14 @@ See [recipes/03_buddy.md](recipes/03_buddy.md) for the full pattern.
 | Command | What it does |
 |---------|-------------|
 | `harnex run <cli>` | Start an agent (`--tmux` visible, `--detach` background, `--watch` built-in monitoring) |
-| `harnex send --id <id>` | Send a message (queues if busy, `--wait-for-idle` to block until done) |
+| `harnex send --id <id>` | Send a message (queues if busy, `--wait-for-idle` to block until the turn returns idle) |
 | `harnex stop --id <id>` | Send the agent's native exit sequence |
-| `harnex status` | List running sessions (`--json` for full payloads) |
+| `harnex status` | List running sessions; with `--id ID --json`, terminal summaries can classify completed/failed sessions after exit |
 | `harnex pane --id <id>` | Capture a tmux-backed session's screen (`--follow` for live) |
 | `harnex logs --id <id>` | Read session transcript (`--follow` to tail) |
 | `harnex events --id <id>` | Stream structured session events (`--snapshot` for non-blocking dump) |
 | `harnex history` | List completed dispatches from `.harnex/dispatch.jsonl` |
-| `harnex wait --id <id>` | Block until exit, a target state, or `--until task_complete` |
+| `harnex wait --id <id>` | Block until process exit by default; use `--until done` for unattended work completion or `--until task_complete` for exact structured turn completion |
 | `harnex doctor` | Run adapter dependency preflight checks; add `--sweep` for read-only session drift diagnostics |
 | `harnex guide` | Getting started walkthrough |
 | `harnex agents-guide` | Agent-facing dispatch, chain, buddy, monitoring, and naming guides |

data/guides/01_dispatch.md

@@ -73,7 +73,7 @@ for i in 1 2 3; do
   harnex run pi --id w-$i --tmux w-$i --detach \
     --context "Read and execute /tmp/task-$i.md" --auto-stop &
 done
-for i in 1 2 3; do harnex wait --id w-$i & done
+for i in 1 2 3; do harnex wait --id w-$i --until done & done
 wait
 ```
 
@@ -125,6 +125,7 @@ Use the lightest primitive that gives the signal you need:
 | Continuous pane view | `harnex pane --id pi-i-NN --follow` |
 | Transcript tail | `harnex logs --id pi-i-NN --lines 80` |
 | Structured events | `harnex events --id pi-i-NN --snapshot` |
+| Work completion fence | `harnex wait --id pi-i-NN --until done` |
 | Native turn completion | `harnex wait --id pi-i-NN --until task_complete` |
 
 For unattended policy-only stall recovery, use built-in watch mode:

data/guides/03_buddy.md

@@ -54,8 +54,8 @@ If the worker appears stuck at a prompt or permission dialog for more than
 10 minutes with no progress, nudge it:
 - `harnex send --id pi-i-42 --message "You appear to have stalled. Continue with your current task."`
 
-If `harnex status --id pi-i-42 --json` reports `state=completed` or `state=failed`, report back:
-- `tmux send-keys -t "$HARNEX_SPAWNER_PANE" "pi-i-42 terminal state reached. Check harnex status --id pi-i-42 --json." Enter`
+If `harnex status --id pi-i-42 --json` reports `done=true` or `work_state=failed`, report back:
+- `tmux send-keys -t "$HARNEX_SPAWNER_PANE" "pi-i-42 work-level state reached. Check harnex status --id pi-i-42 --json." Enter`
 
 Do not interfere with active work. Stop yourself after reporting completion.
 ```

data/guides/04_monitoring.md

@@ -17,24 +17,26 @@ Prefer signals in this order:
 | `harnex pane` | Live UI interpretation and prompt/error diagnosis |
 | `harnex status` | Session liveness and coarse state |
 
-For structured sessions (Pi RPC and Codex app-server),
-`harnex wait --until task_complete` is a strong turn-level fence. It still
-does not know your acceptance criteria; verify the expected artifact or tests
-afterward.
+For unattended monitors, prefer `harnex wait --until done`: it returns on the
+work-level `task_complete` signal or terminal exit, whichever comes first. For
+structured sessions (Pi RPC and Codex app-server), `harnex wait --until
+task_complete` remains the exact turn-level fence. Neither knows your acceptance
+criteria; verify the expected artifact or tests afterward.
 
 ## Completion Test
 
-For unattended work, first gate on harnex terminal state, then verify the task
+For unattended work, first gate on harnex work completion, then verify the task
 artifact and repo health:
 
 ```bash
-harnex wait --id pi-i-NN --timeout 5400 &&
+harnex wait --id pi-i-NN --until done --timeout 5400 &&
   test -f path/to/expected-artifact &&
   test -z "$(git status --short)"
 ```
 
-`harnex wait` succeeds from durable terminal telemetry (`--summary-out` /
-`.harnex/dispatch.jsonl` / exit status), not from tmp done markers.
+`harnex wait --until done` succeeds from `task_complete` or durable terminal
+telemetry (`--summary-out` / `.harnex/dispatch.jsonl` / exit status), not from
+tmp done markers.
 
 Adjust the artifact path to the task. The point is to avoid declaring done while
 a worker is between edits or between commits.
@@ -72,6 +74,8 @@ harnex events --id pi-i-NN
 For task completion:
 
 ```bash
+harnex wait --id pi-i-NN --until done --timeout 900
+# Or, when you specifically need the structured turn event:
 harnex wait --id pi-i-NN --until task_complete --timeout 900
 ```
 
@@ -92,12 +96,13 @@ while :; do
   fi
 
   row=$(harnex status --id pi-i-NN --json | ruby -rjson -e 'rows=JSON.parse(STDIN.read); print JSON.generate(rows.first || {})')
+  done=$(printf '%s' "$row" | ruby -rjson -e 'print(JSON.parse(STDIN.read)["done"] ? "true" : "false")')
+  work_state=$(printf '%s' "$row" | ruby -rjson -e 'print(JSON.parse(STDIN.read)["work_state"].to_s)')
   state=$(printf '%s' "$row" | ruby -rjson -e 'print(JSON.parse(STDIN.read)["state"].to_s)')
 
-  case "$state" in
-    completed) echo "pi-i-NN completed"; break ;;
-    failed|unknown) echo "pi-i-NN terminal state: $state" >&2; exit 1 ;;
-    running) harnex pane --id pi-i-NN --lines 20 ;;
+  case "$done:$work_state" in
+    true:*) echo "pi-i-NN work completed"; break ;;
+    false:failed) echo "pi-i-NN work failed; process state: $state" >&2; exit 1 ;;
     *) harnex pane --id pi-i-NN --lines 20 ;;
   esac
 
@@ -136,6 +141,7 @@ interpretation.
 
 ## Anti-Patterns
 
+- Polling `state=completed` alone and missing live sessions with `task_complete=true`.
 - Polling `state=prompt` alone and calling it done.
 - Blocking orchestrators on `/tmp/*-done.txt` as the only completion signal.
 - Letting an unattended loop run with no wall-clock cap.

data/lib/harnex/commands/status.rb

@@ -30,6 +30,8 @@ module Harnex
           Use --all when supervising workers launched from sibling worktrees.
           With --id, terminal summaries can report completed/failed/unknown
           even after the live session registry is gone.
+          `state` is process/session state; use JSON `done`/`work_state`
+          or `harnex wait --until done` for work-level completion.
           A prompt-like state is not a completion signal by itself.
       TEXT
     end
@@ -100,10 +102,14 @@ module Harnex
     end
 
     def normalize_live_status(session)
+      task_complete = task_complete?(session)
       session.merge(
         "state" => "running",
+        "process_state" => "running",
         "terminal" => false,
-        "task_complete" => !session["last_completed_at"].to_s.empty?,
+        "task_complete" => task_complete,
+        "done" => Harnex.work_done_for("running", task_complete: task_complete),
+        "work_state" => Harnex.work_state_for("running", task_complete: task_complete),
         "exit" => nil,
         "exit_code" => nil,
         "summary_out" => nil,
@@ -112,6 +118,11 @@ module Harnex
       )
     end
 
+    def task_complete?(session)
+      session["task_complete"] == true || session["task_complete"].to_s == "true" ||
+        !session["last_completed_at"].to_s.empty?
+    end
+
     def load_live_status(session)
       uri = URI("http://#{session.fetch('host')}:#{session.fetch('port')}/status")
       request = Net::HTTP::Get.new(uri)

data/lib/harnex/commands/wait.rb

@@ -21,6 +21,8 @@ module Harnex
         Options:
           --id ID         Session ID to wait for (required)
           --until STATE   Wait until session reaches STATE. Supported:
+                            done            (work fence — task_complete or
+                                             terminal exit, whichever comes first)
                             task_complete   (events JSONL — fires on
                                              turn/completed; adapter-agnostic)
                             <other>         (agent_state HTTP poll, e.g.
@@ -31,11 +33,13 @@ module Harnex
           -h, --help      Show this help
 
         Common patterns:
+          #{program_name} --id cx-i-42 --until done --timeout 900
           #{program_name} --id cx-i-42 --until task_complete --timeout 900
           #{program_name} --id cx-i-42 --until prompt --timeout 120
           #{program_name} --id cx-i-42
 
         Gotchas:
+          done is the safest work-level fence for monitors.
           task_complete is an event predicate; prompt/busy are live state polls.
           Prompt state alone does not prove work acceptance. Verify artifacts/tests.
           Exit waits can resolve from terminal summary rows when live registry/
@@ -65,7 +69,10 @@ module Harnex
       raise "--id is required for harnex wait" unless @options[:id]
 
       if @options[:until_state]
-        if EVENT_PREDICATES.include?(@options[:until_state])
+        case @options[:until_state]
+        when "done"
+          wait_until_done
+        when *EVENT_PREDICATES
           wait_until_event(@options[:until_state])
         else
           wait_until_state
@@ -135,7 +142,7 @@ module Harnex
 
           task_complete_seen = true if event_type(event) == "task_complete"
           if matches?(event, predicate, task_complete_seen)
-            return [emit_event_match(event, start_time), f.pos, task_complete_seen]
+            return [emit_event_match(event, start_time, predicate), f.pos, task_complete_seen]
           end
         end
         offset = f.pos
@@ -166,7 +173,7 @@ module Harnex
     def matches?(event, predicate, task_complete_seen)
       type = event_type(event)
       case predicate
-      when "task_complete"
+      when "task_complete", "done"
         type == "task_complete"
       when "prompt"
         type == "task_complete" ||
@@ -176,18 +183,100 @@ module Harnex
       end
     end
 
-    def emit_event_match(event, start_time)
+    def emit_event_match(event, start_time, predicate)
       waited = (Time.now - start_time).round(1)
-      puts JSON.generate(
+      payload = {
         ok: true,
         id: @options[:id],
         event: event_type(event),
         seq: event["seq"],
         waited_seconds: waited
-      )
+      }
+      if predicate == "done"
+        payload.merge!(
+          status: "done",
+          state: "running",
+          process_state: "running",
+          terminal: false,
+          task_complete: true,
+          done: true,
+          work_state: "completed"
+        )
+      end
+      puts JSON.generate(payload)
       0
     end
 
+    def wait_until_done
+      repo_root = Harnex.resolve_repo_root(@options[:repo_path])
+      events_path = Harnex.events_log_path(repo_root, @options[:id])
+      exit_path = Harnex.exit_status_path(repo_root, @options[:id])
+      registry = Harnex.read_registry(repo_root, @options[:id])
+      start_time = Time.now
+      deadline = @options[:timeout] ? start_time + @options[:timeout] : nil
+
+      offset = 0
+      task_complete_seen = false
+      final_event_deadline = nil
+
+      status, offset, task_complete_seen = scan_events(events_path, offset, "done", task_complete_seen, start_time)
+      return status if status
+
+      unless registry
+        terminal = done_status(repo_root)
+        return emit_done_terminal_status(terminal) if terminal
+        return emit_done_exit_status(exit_path, @options[:id]) if File.exist?(exit_path)
+
+        unless File.exist?(events_path)
+          warn("harnex wait: no session found with id #{@options[:id].inspect}")
+          puts JSON.generate(ok: false, id: @options[:id], state: "unknown", process_state: "unknown", terminal: false,
+                             task_complete: false, done: false, work_state: "unknown", status: "unknown")
+          return 1
+        end
+      end
+
+      target_pid = registry && registry["pid"]
+
+      loop do
+        status, offset, task_complete_seen = scan_events(events_path, offset, "done", task_complete_seen, start_time)
+        return status if status
+
+        unless registry
+          terminal = done_status(repo_root)
+          return emit_done_terminal_status(terminal) if terminal
+          return emit_done_exit_status(exit_path, @options[:id]) if File.exist?(exit_path)
+        end
+
+        if deadline && Time.now >= deadline
+          waited = (Time.now - start_time).round(1)
+          puts JSON.generate(ok: false, id: @options[:id], status: "timeout", waited_seconds: waited,
+                             done: false, work_state: "running")
+          return 124
+        end
+
+        if target_pid && !Harnex.alive_pid?(target_pid)
+          final_event_deadline ||= Time.now + FINAL_EVENT_GRACE_SECONDS
+          if Time.now >= final_event_deadline
+            await_exit_status(exit_path)
+            return emit_done_exit_status(exit_path, @options[:id]) if File.exist?(exit_path)
+
+            terminal = done_status(repo_root)
+            return emit_done_terminal_status(terminal) if terminal
+
+            waited = (Time.now - start_time).round(1)
+            puts JSON.generate(ok: false, id: @options[:id], state: "exited", process_state: "exited",
+                               terminal: true, task_complete: false, done: false, work_state: "unknown",
+                               waited_seconds: waited)
+            return 1
+          end
+        else
+          final_event_deadline = nil
+        end
+
+        sleep EVENT_POLL_INTERVAL
+      end
+    end
+
     def wait_until_state
       repo_root = Harnex.resolve_repo_root(@options[:repo_path])
       target_state = @options[:until_state]
@@ -244,7 +333,8 @@ module Harnex
         return emit_terminal_status(terminal) if terminal
 
         warn("harnex wait: no session found with id #{@options[:id].inspect}")
-        puts JSON.generate(ok: false, id: @options[:id], state: "unknown", terminal: false, status: "unknown")
+        puts JSON.generate(ok: false, id: @options[:id], state: "unknown", process_state: "unknown",
+                           terminal: false, task_complete: false, done: false, work_state: "unknown", status: "unknown")
         return 1
       end
 
@@ -259,7 +349,8 @@ module Harnex
           terminal = terminal_status(repo_root)
           return emit_terminal_status(terminal) if terminal
 
-          puts JSON.generate(ok: false, id: @options[:id], state: "unknown", terminal: false, status: "unknown")
+          puts JSON.generate(ok: false, id: @options[:id], state: "unknown", process_state: "unknown",
+                             terminal: false, task_complete: false, done: false, work_state: "unknown", status: "unknown")
           return 1
         end
 
@@ -328,19 +419,60 @@ module Harnex
       status
     end
 
+    def done_status(repo_root)
+      status = Harnex::TerminalStatus.resolve(id: @options[:id], repo_root: repo_root)
+      return nil unless status
+      return nil unless status["done"] || status["terminal"]
+
+      status
+    end
+
+    def emit_done_exit_status(exit_path, id)
+      data = JSON.parse(File.read(exit_path))
+      exit_code = data["exit_code"]
+      task_complete = data["task_complete"] == true || data["task_complete"].to_s == "true"
+      exit_success = exit_code.nil? || exit_code.to_i == 0
+      state = exit_success ? "completed" : "failed"
+      done = task_complete || exit_success
+      payload = data.merge(
+        "ok" => done,
+        "id" => id,
+        "state" => state,
+        "process_state" => "exited",
+        "terminal" => true,
+        "task_complete" => task_complete,
+        "done" => done,
+        "work_state" => Harnex.work_state_for(state, task_complete: task_complete)
+      )
+      success = done
+      puts JSON.generate(payload)
+      return 0 if success
+
+      exit_code.is_a?(Integer) && exit_code.positive? ? exit_code : 1
+    rescue JSON::ParserError
+      puts JSON.generate(ok: false, id: id, state: "failed", process_state: "exited", terminal: true,
+                         task_complete: false, done: false, work_state: "failed", status: "invalid_exit_status")
+      1
+    end
+
+    def emit_done_terminal_status(status)
+      payload = terminal_payload(status)
+      payload[:ok] = !!payload[:done]
+      payload[:status] = payload[:done] ? "done" : status["state"]
+      puts JSON.generate(payload)
+
+      if payload[:ok]
+        0
+      elsif status["exit_code"].is_a?(Integer) && status["exit_code"] > 0
+        status["exit_code"]
+      else
+        1
+      end
+    end
+
     def emit_terminal_status(status)
-      payload = {
-        ok: status["state"] == "completed",
-        id: status["id"],
-        state: status["state"],
-        terminal: true,
-        task_complete: status["task_complete"],
-        exit: status["exit"],
-        exit_code: status["exit_code"],
-        summary_out: status["summary_out"],
-        ended_at: status["ended_at"],
-        source: status["source"]
-      }
+      payload = terminal_payload(status)
+      payload[:ok] = status["state"] == "completed"
       puts JSON.generate(payload)
 
       if payload[:ok]
@@ -352,6 +484,27 @@ module Harnex
       end
     end
 
+    def terminal_payload(status)
+      task_complete = !!status["task_complete"]
+      work_state = status["work_state"] || Harnex.work_state_for(status["state"], task_complete: task_complete)
+      done = status.key?("done") ? !!status["done"] : work_state == "completed"
+      {
+        ok: false,
+        id: status["id"],
+        state: status["state"],
+        process_state: status["process_state"] || Harnex.process_state_for(status["state"], terminal: true),
+        terminal: status.key?("terminal") ? !!status["terminal"] : true,
+        task_complete: task_complete,
+        done: done,
+        work_state: work_state,
+        exit: status["exit"],
+        exit_code: status["exit_code"],
+        summary_out: status["summary_out"],
+        ended_at: status["ended_at"],
+        source: status["source"]
+      }
+    end
+
     def parser
       @parser ||= OptionParser.new do |opts|
         opts.banner = "Usage: harnex wait [options]"

data/lib/harnex/core.rb

@@ -68,6 +68,36 @@ module Harnex
     VERSION
   end
 
+  def work_state_for(session_state, task_complete: false)
+    return "completed" if task_complete
+
+    case session_state.to_s
+    when "completed"
+      "completed"
+    when "failed"
+      "failed"
+    when "running"
+      "running"
+    else
+      "unknown"
+    end
+  end
+
+  def work_done_for(session_state, task_complete: false)
+    work_state_for(session_state, task_complete: task_complete) == "completed"
+  end
+
+  def process_state_for(session_state, terminal: false)
+    return "running" unless terminal
+
+    case session_state.to_s
+    when "completed", "failed"
+      "exited"
+    else
+      "unknown"
+    end
+  end
+
   def host_info
     {
       host: Socket.gethostname,

data/lib/harnex/runtime/session.rb

@@ -221,9 +221,14 @@ module Harnex
       end
 
       payload[:input_state] = adapter.input_state(screen_snapshot) if include_input_state
+      task_complete = !!@last_completed_at
       payload[:agent_state] = @state_machine.to_s
+      payload[:process_state] = "running"
       payload[:inbox] = @inbox.stats
       payload[:last_completed_at] = @last_completed_at&.iso8601
+      payload[:task_complete] = task_complete
+      payload[:done] = Harnex.work_done_for("running", task_complete: task_complete)
+      payload[:work_state] = Harnex.work_state_for("running", task_complete: task_complete)
       payload[:model] = summary_model
       payload[:effort] = meta_hash["effort"]
       payload[:auto_disconnects] = @event_counters.snapshot[:disconnections]
@@ -733,6 +738,8 @@ module Harnex
       return unless defined?(@exit_code) && !@exit_code.nil?
 
       exit_path = Harnex.exit_status_path(repo_root, id)
+      task_complete = !!@last_completed_at
+      state = @exit_code.to_i == 0 ? "completed" : "failed"
       payload = {
         ok: true,
         id: id,
@@ -740,6 +747,11 @@ module Harnex
         session_id: session_id,
         repo_root: repo_root,
         exit_code: @exit_code,
+        state: state,
+        process_state: "exited",
+        task_complete: task_complete,
+        done: Harnex.work_done_for(state, task_complete: task_complete),
+        work_state: Harnex.work_state_for(state, task_complete: task_complete),
         started_at: @started_at.iso8601,
         exited_at: Time.now.iso8601,
         injected_count: @injected_count

data/lib/harnex/terminal_status.rb

@@ -42,8 +42,11 @@ module Harnex
         "id" => Harnex.normalize_id(id),
         "repo_root" => File.expand_path(repo_root.to_s.empty? ? Dir.pwd : repo_root),
         "state" => "unknown",
+        "process_state" => "unknown",
         "terminal" => false,
         "task_complete" => false,
+        "done" => false,
+        "work_state" => "unknown",
         "exit" => nil,
         "exit_code" => nil,
         "summary_out" => nil,
@@ -127,12 +130,17 @@ module Harnex
       meta = record["meta"] || {}
       actual = record["actual"] || {}
       state = classify_summary_state(actual)
+      task_complete = !!actual["task_complete"]
+      terminal = state != "unknown"
       {
         "id" => meta["id"].to_s,
         "repo_root" => meta["repo"] || fallback_repo_root,
         "state" => state,
-        "terminal" => state != "unknown",
-        "task_complete" => !!actual["task_complete"],
+        "process_state" => Harnex.process_state_for(state, terminal: terminal),
+        "terminal" => terminal,
+        "task_complete" => task_complete,
+        "done" => Harnex.work_done_for(state, task_complete: task_complete),
+        "work_state" => Harnex.work_state_for(state, task_complete: task_complete),
         "exit" => blank_to_nil(actual["exit"]),
         "exit_code" => actual["exit_code"],
         "summary_out" => summary_path,
@@ -164,12 +172,17 @@ module Harnex
         else
           "unknown"
         end
+      task_complete = record["terminal_event"].to_s == "task_complete"
+      terminal = state != "unknown"
       {
         "id" => record["id"].to_s,
         "repo_root" => fallback_repo_root,
         "state" => state,
-        "terminal" => state != "unknown",
-        "task_complete" => record["terminal_event"].to_s == "task_complete",
+        "process_state" => Harnex.process_state_for(state, terminal: terminal),
+        "terminal" => terminal,
+        "task_complete" => task_complete,
+        "done" => Harnex.work_done_for(state, task_complete: task_complete),
+        "work_state" => Harnex.work_state_for(state, task_complete: task_complete),
         "exit" => history_exit(status),
         "exit_code" => nil,
         "summary_out" => blank_to_nil(record["summary_out_path"]),

data/lib/harnex/version.rb

@@ -1,4 +1,4 @@
 module Harnex
-  VERSION = "0.7.5"
-  RELEASE_DATE = "2026-05-26"
+  VERSION = "0.7.6"
+  RELEASE_DATE = "2026-06-09"
 end

data/recipes/01_fire_and_watch.md

@@ -19,7 +19,8 @@ harnex run codex --id cx-23 --tmux
 If the plan file is self-contained, reference it directly:
 
 ```bash
-harnex send --id cx-23 --message "Implement koder/plans/plan_23.md. Run tests when done." --wait-for-idle --timeout 1200
+harnex send --id cx-23 --message "Implement koder/plans/plan_23.md. Run tests when done."
+harnex wait --id cx-23 --until done --timeout 1200
 ```
 
 For tasks that need structured output, tell the worker to write a
@@ -32,12 +33,13 @@ Run the full test suite when done.
 Write a short summary to /tmp/impl-23.md.
 EOF
 
-harnex send --id cx-23 --message "Read and execute /tmp/task-cx-23.md" --wait-for-idle --timeout 1200
+harnex send --id cx-23 --message "Read and execute /tmp/task-cx-23.md"
+harnex wait --id cx-23 --until done --timeout 1200
 ```
 
 ### 3. Watch until done
 
-Use `--wait-for-idle` as the fence, then read the worker's screen:
+Use `harnex wait --until done` as the work-level fence, then read the worker's screen:
 
 ```bash
 harnex pane --id cx-23 --lines 25

data/recipes/03_buddy.md

@@ -45,8 +45,9 @@ Your job:
 2. If the worker appears stuck at a prompt for more than 10 minutes
    with no progress, nudge it:
    - `harnex send --id worker-42 --message "You appear to have stalled. Continue with your current task."`
-3. If the worker has exited (status shows no session), report back:
-   - `tmux send-keys -t "$HARNEX_SPAWNER_PANE" "worker-42 has exited. Check results." Enter`
+3. If `harnex status --id worker-42 --json` reports `done=true` or
+   `work_state=failed`, report back:
+   - `tmux send-keys -t "$HARNEX_SPAWNER_PANE" "worker-42 reached a work-level terminal state. Check results." Enter`
 4. Keep watching until the worker finishes or is stopped.
 
 Do not interfere with work in progress. Only nudge when clearly stalled.

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: harnex
 version: !ruby/object:Gem::Version
-  version: 0.7.5
+  version: 0.7.6
 platform: ruby
 authors:
 - Jikku Jose
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2026-05-26 00:00:00.000000000 Z
+date: 2026-06-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.