Skip to content

fix: honor precise Flow execution outcomes - #23

Merged
abrichr merged 1 commit into
mainfrom
fix/precise-flow-outcomes
Jul 28, 2026
Merged

fix: honor precise Flow execution outcomes#23
abrichr merged 1 commit into
mainfrom
fix/precise-flow-outcomes

Conversation

@abrichr

@abrichr abrichr commented Jul 28, 2026

Copy link
Copy Markdown
Member

Summary

  • make Flow's precise execution outcome authoritative for MCP run and report results
  • ensure COMPLETED_UNVERIFIED and ROLLED_BACK never become MCP success
  • fail closed on malformed, contradictory, or envelope-inconsistent reports
  • preserve legacy reports that only expose the boolean success field
  • keep all public projections count-only and use one fixed message mapping

Verification

  • 89 tests passed
  • Ruff passed for src, tests, and scripts
  • diff check passed

The output change is additive: execution_outcome appears only when the persisted Flow report provides a recognized precise value. Existing status and success fields remain compatible.

@abrichr
abrichr merged commit 976ddb2 into main Jul 28, 2026
7 checks passed
@abrichr
abrichr deleted the fix/precise-flow-outcomes branch July 28, 2026 06:15
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