Skip to content

feat(comms): add durable provider-native delivery#528

Open
tangemicioglu wants to merge 10 commits into
mainfrom
research/cmux-hcom-comms
Open

feat(comms): add durable provider-native delivery#528
tangemicioglu wants to merge 10 commits into
mainfrom
research/cmux-hcom-comms

Conversation

@tangemicioglu

@tangemicioglu tangemicioglu commented Jun 8, 2026

Copy link
Copy Markdown
Member

Description

Adds provider-native communication delivery plumbing for Wardian agents across live PTY submission, mailbox drain, workflow live routing, remote control sends, and headless provider execution.

Follow-up fixes on this branch also:

  • Drain queued live deliveries after telemetry-derived idle readiness.
  • Require workflow structured replies to be executed through wardian reply, not printed as transcript markers.
  • Preserve scheduled workflow instance identity so one running schedule does not make sibling schedules for the same blueprint appear running.
  • Render Workflow History as one chronological run stream so newer failed or completed runs are not hidden behind older workflow summaries.
  • Keep live workflow waits alive when provider watch evidence rolls over before the structured reply arrives.
  • Mark live workflow agents Processing only after confirmed prompt delivery, using the same post-delivery path as normal sends.

Key pieces:

  • Durable delivery attempts and interaction records for live-surface and headless-provider delivery.
  • Shared live-surface delivery service with provider-aware submit states, retry-safe mailbox failure handling, and redacted persisted prompt bodies.
  • Canonical submit_sent_unconfirmed delivery state across backend, CLI/frontend DTOs, docs, and tests.
  • Provider-native communication spec plus command-panel and IPC/developer documentation updates.

Related Issues

Fixes #526

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update

Screenshot Evidence

workflow scheduled instance state

workflow history chronological order

How Has This Been Tested?

Fresh local verification after the workflow monitor fixes:

  • npm run lint
  • npm run test - 112 files, 1044 tests passed
  • npm run build
  • npm run test -- WorkflowMonitor.test.tsx - 16 tests passed
  • npm run check:frontend-screenshot -- origin/main HEAD

Fresh local backend verification after the live workflow fixes:

  • cd src-tauri && cargo test live_agent_reply_wait_survives_watch_cursor_rollover - failed red before the fix, passed after
  • cd src-tauri && cargo test workflow_live_surface_request_marks_prompt_started_after_delivery - failed red before the fix, passed after
  • cd src-tauri && cargo test workflow::runner::tests::live_agent - 6 tests passed
  • cd src-tauri && cargo test - 903 unit tests, 7 mock provider tests, 1 workflow executor test passed
  • cd src-tauri && cargo clippy
  • cd src-tauri && cargo check
  • git diff --check
  • git diff --cached --check

Earlier local backend verification on this branch:

  • cd src-tauri && cargo test run_summary_carries_schedule_id_from_invocation
  • Autoreview workflow 1780878073370-aa0cffeb converged with no unresolved accepted findings.

Checklist:

  • My code follows the stylistic guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I checked docs/developer/docs-maintenance.md for user docs, public links, release notes, and screenshot refresh needs
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • (Frontend changes) Feature-specific screenshot evidence is embedded above, or not applicable

@codecov

codecov Bot commented Jun 8, 2026

Copy link
Copy Markdown

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.

Provider-native agent communication delivery

1 participant