fix(flows): expose unrecoverable turn failures - #22
Merged
Conversation
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
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.
Summary
Unrecoverablethrough the backend-neutralhmz.flowsAPIWhy
The official
humanize1:gen-planflow must distinguish transient turn failures from failures that cannot succeed on retry. Importinghmz.agentsdirectly would violate the flow layering contract, so the vocabulary needs to be forwarded byhmz.flows.This is the prerequisite for humanfia/flowverse#2, which contains the complete backend-neutral gen-plan convergence fix.
Verification
uv run pytest -q tests/test_flow_interface.pyuv run pre-commit run --all-filescheckjob passed on commitd66ad04