Skip to content

Add Mission Control for Herdr 0.7.5#32

Merged
moneycaringcoder merged 2 commits into
mainfrom
feat/mission-control
Jul 24, 2026
Merged

Add Mission Control for Herdr 0.7.5#32
moneycaringcoder merged 2 commits into
mainfrom
feat/mission-control

Conversation

@moneycaringcoder

@moneycaringcoder moneycaringcoder commented Jul 24, 2026

Copy link
Copy Markdown
Owner

Summary

Adds the Mission Control phase for Herdr 0.7.5+ while preserving basic workload management on Herdr 0.7.3 and 0.7.4.

Mission Control turns the existing Observer workflow into a live, status-first control room for mixed local and SSH-backed Tether workloads. It uses Herdr's typed socket and event APIs for recognized agents, keeps bounded tmux capture as the detached/non-agent fallback, and fails closed whenever identity or delivery is uncertain.

What changed

  • Added a reusable typed Herdr socket client for snapshots, agent reads, focus, semantic waits, reviewed prompt-and-wait delivery, pane metadata, and reconnecting event subscriptions.
  • Added exact group/member/pane binding through bounded group, session, and membership-epoch metadata tokens.
  • Added the independent prompt_agent capability, defaulting to false; observation and interactive-open permissions never imply prompt authority.
  • Evolved Observer into Mission Control with explicit DETACHED, IDLE, WORKING, BLOCKED, DONE, UNKNOWN, UNREACHABLE, and STALE states; bounded multi-target review; and per-target DELIVERED, REJECTED, or UNCERTAIN results.
  • Replaced recurring SSH capture for exactly bound agents with Herdr events and agent.read, while retaining safe fallback capture for detached and non-agent workloads.
  • Added bounded OpenSSH connection reuse, successful-observation latency, stale-state retention, and cycle-safe ssh_config Include alias discovery.
  • Added native Agents sidebar filters for the selected group, agents needing attention, and remote group agents.

Safety and compatibility

  • state.json remains schema version 4; prompt_agent is additive and omitted when false.
  • Prompt text remains memory-only and is never written to state.json.
  • Every prompt revalidates membership epoch, exact Tether ownership, running state, metadata binding, recognized occupant, capability, and settled state.
  • Uncertain prompt delivery is never retried automatically; partial fan-out results remain explicit.
  • Closing Mission Control or another Herdr view never stops the underlying Tether workload.
  • Herdr 0.7.3/0.7.4 retains ordinary workload management and read-only Observer behavior with a clear 0.7.5 upgrade message for Mission Control.

Commit structure

  1. f410147 — Mission Control implementation and automated coverage.
  2. 3b7ec6a — documentation, README, security, troubleshooting, architecture, changelog, and Hermes integration pass.

Verification

The implementation passed one complete same-run release verification:

  • cargo fmt --all -- --check
  • cargo clippy --locked --all-targets --all-features -- -D warnings
  • cargo test --locked --all-features — 387 tests passed across 14 suites
  • Python quality suites — 78 tests passed
  • documentation, release, package, and public-contract checks
  • package verification — 54 files; 23 curated public examples
  • Herdr 0.7.3 live-product smoke
  • Herdr 0.7.5 live-product smoke

Both live-product smokes verified actions, continuity, exact close behavior, and every placement mode.

The follow-up documentation commit additionally passed git diff --check, the documentation contracts, all 78 Python quality tests, and the 54-file package-content check.

@moneycaringcoder
moneycaringcoder merged commit f083b61 into main Jul 24, 2026
8 checks passed
@moneycaringcoder
moneycaringcoder deleted the feat/mission-control branch July 24, 2026 16:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant