chore(vendor): bump tinyflows to 4e2e042 - #5697
Conversation
Brings in tinyhumansai/tinyflows#75, which lets an `agent` node carry what the host's harness did inside it — the transcript rides `AgentRunOutcome` to `NodeOutput` and onto `ExecutionStep`, where a `RunObserver` receives it. Gitlink only; no source change here. openhuman's own `flows` domain compiles against the same crate and is unaffected: the additions are new fields with defaults and two new constructors, so nothing that builds today stops building. Verified by building the downstream consumer against it — opencompany's suite (which links this vendored tinyflows through its `[patch.crates-io]`) is green at 5101 passed.
|
You have reached your Codex usage limits for security reviews. Please try again later. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthroughThe ChangesTinyflows update
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This is a localized vendor update with additive behavior and reported passing compatibility and upstream checks; no actionable merge-blocking risk remains after normal checks. Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Warning Your free Security trial is over. An organization admin can activate billing to continue. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Gitlink only. Brings in tinyhumansai/tinyflows#75, which lets an
agentnode carry what the host's harness did inside it: the transcript ridesAgentRunOutcome→NodeOutput→ExecutionStep, where aRunObserverreceives it onon_step_finish.Before it, a workflow run could be read as pass/fail and nothing more — the node's output said what came out, and nothing said what happened inside.
8f63a273→4e2e0426.Does this break openhuman's own
flowsdomain?No. Everything in that PR is additive at the type level:
Default/serde(default)onAgentRunOutcome,NodeOutputandExecutionStepAgentRunOutcome::limit_stop,::paused) and a derivedDefaultonExecutionStepTranscriptEntrymoved out of thestorefeature and re-exported, sostore::types::TranscriptEntrystill resolvesThe one thing to know: a struct literal that names every field of
ExecutionSteporAgentRunOutcomeneeds..Default::default()added. Nothing in this repo does that today — I grepped — so this is a note for the future rather than a change needed here.Verification
Rather than assert compatibility, I built the downstream consumer against it. opencompany links this vendored tinyflows through its
[patch.crates-io]entry, and its suite is green on this exact gitlink:That covers the
flows-adjacent surface opencompany exercises. tinyflows' own gates on the merged commit:--workspacetests 1126 / all-features 1159 / adaptive 278, clippy-D warningson both feature sets, coverage above the repo's 90% line gate.Why now
It unblocks the opencompany side of run observability, which needs the transcript to reach a
RunObserverin order to render what each agent did.Summary by CodeRabbit