Fix hosted replies and preserved workflow dispatch - #122
Merged
Merged
Conversation
boudra
changed the title
This was referenced Sep 8, 2026
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.
Live hosted QA after #118 found two failures: new GitHub agents received no reply tool, and preserved legacy workflows failed before dispatch because the continuation-default reader parsed their documents as new triggers.
Expose replies through the dynamic registration for every provider, using the active provider's availability check. Preserve the existing policy when an adapter revision contains a legacy workflow document. No schema or daemon protocol changes.
Both failures have failing-first regressions. The hosted-registration test verifies reply materialization and comment delivery; the configuration test reads a preserved legacy adapter revision without adding continuation. The provider, configuration, migration, and related suites pass (179 tests), and the source-built Hub/daemon E2E suite passes all seven tests. Final local verification also passes: 1,252 tests (17 skipped), all 79 browser tests, typecheck, lint, formatting, migration checks, build, and the production-container smoke test. Live GitHub QA will be repeated after deployment.
Risk surface: dynamic reply availability and reading stored organization-trigger revisions. Legacy workflow configuration and historical execution intents remain unchanged.
Refs #118, #121.