test(agent): run dispatch tests through conversation work - #1604
Open
dcramer wants to merge 1 commit into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
dcramer
marked this pull request as ready for review
August 17, 2026 04:50
dcramer
force-pushed
the
codex/agent-dispatch-test-boundaries
branch
from
August 17, 2026 18:01
e89716c to
de7c398
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Agent dispatch integration tests now use the production conversation-work composition for new work, durable resume, delivered-reply replay, and terminal failure recovery. They fake only model output and Slack I/O. Fixed worker decisions, including resumable state and delivery receipts, remain in component coverage.
The shared fixture now exposes only the queue, state, runtime, and worker function that these tests need. A test-architecture rule rejects direct dispatch worker or router construction in integration tests, so future coverage must keep using the production path.