fix(flows): repair main compile break from crossed PRs

[senamakel]

Summary

• Repairs the compile break on main (failing run: https://github.com/tinyhumansai/openhuman/actions/runs/29917654044, job "Rust Quality (fmt, clippy)"): error[E0061], error[E0308], error[E0277].
• Restores the four vendor submodule pointers (tinyagents, tinyflows, tinychannels, tinyjuice) that fix(flows): reject an unknown agent_ref at author time instead of mid-run #5114 accidentally rolled backwards.
• Updates the one finish_flow_run_row call in flows_resume that was still on the pre-feat(flows): FlowRunFinished event — fully event-driven runs rail (completes B35) #5115 6-argument signature.

Problem

Two merged PRs crossed:

• chore(deps): update vendored runtime crates #5081 moved the vendored runtime crates forward (vendor/tinyagents to v2.1.0, vendor/tinyflows to a commit requiring tinyagents = "2.1") with the matching Cargo.toml/Cargo.lock.
• feat(flows): FlowRunFinished event — fully event-driven runs rail (completes B35) #5115 added a flow_id parameter to finish_flow_run_row (needed to publish FlowRunFinished), making it 7 arguments.
• fix(flows): reject an unknown agent_ref at author time instead of mid-run #5114 was developed before both and merged last. Its commit (81ac128) rolled all four vendor gitlinks backwards (stale local submodules: tinyagents v2.1.0 → v1.9.0, tinyflows back to a commit requiring tinyagents = "1.2"), and its new flows_resume compatibility-gate path calls finish_flow_run_row with the old 6-argument shape.

Consequences on main:

• error[E0061] at src/openhuman/flows/ops.rs:4039 — 6 args passed to the 7-arg finish_flow_run_row.
• With vendor/tinyagents at 1.9.0, the [patch.crates-io] no longer satisfies the root crate's tinyagents = "2.1" requirement, so the dependency graph splits into two tinyagents versions. That yields error[E0308] (tinyflows::engine::GraphObservation vs tinyagents::GraphObservation at ops.rs:3680) and error[E0277] (SqliteCheckpointer<Value>: Checkpointer<Value> not satisfied at src/openhuman/tinyflows/caps.rs:3391 — "multiple different versions of crate tinyagents").

PR branches missed this because the vendor pointer regression only materializes at merge time on main.

Solution

Minimal, two commits:

• Restore the vendor gitlinks to exactly the commits chore(deps): update vendored runtime crates #5081 landed (no other submodule movement): vendor/tinyagents 2583fcc (v2.1.0), vendor/tinyflows 56998ec, vendor/tinychannels 14057e0, vendor/tinyjuice e6848ed. This re-unifies the graph on one tinyagents 2.1.0 and fixes E0308/E0277 with zero code change.
• Pass flow_id (already in scope and semantically correct — it is the flow whose resume was rejected) to the finish_flow_run_row call in flows_resume, matching every other call site updated by feat(flows): FlowRunFinished event — fully event-driven runs rail (completes B35) #5115.

Cargo.toml/Cargo.lock are untouched — they were already correct; only the gitlinks and one call site drifted.

Submission Checklist

• Tests added or updated — N/A: compile-break repair; behavior is already pinned by the existing #5114/#5115 flows tests, which could not run while main failed to compile
• Diff coverage ≥ 80% — N/A: one-line call-site fix + submodule pointer restore; exercised by the existing flows_resume tests
• Coverage matrix updated — N/A: no feature change
• All affected feature IDs from the matrix are listed in the PR description under ## Related — N/A: no feature change
• No new external network dependencies introduced
• Manual smoke checklist updated — N/A: no release-cut surface touched
• Linked issue closed via Closes #NNN — N/A: no issue filed; fixes the red main run cited above

Impact

• Unbreaks main CI (Rust Quality lane and everything downstream of a compiling core crate).
• No runtime behavior change beyond what chore(deps): update vendored runtime crates #5081/fix(flows): reject an unknown agent_ref at author time instead of mid-run #5114/feat(flows): FlowRunFinished event — fully event-driven runs rail (completes B35) #5115 already intended; run-history rows from the flows_resume compatibility gate now carry the correct flow_id.

Related

• Closes:
• Follow-up PR(s)/TODOs: consider a CI guard that fails a PR whose vendor gitlink moves backwards relative to its merge base.

---

AI Authored PR Metadata (required for Codex/Linear PRs)

Linear Issue

• Key: N/A
• URL: N/A

Commit & Branch

• Branch: fix/flows-compile-break
• Commit SHA: f03ba0f

Validation Run

• pnpm --filter openhuman-app format:check — N/A (no frontend change)
• pnpm typecheck — N/A (no frontend change)
• Focused tests: N/A (compile repair)
• Rust fmt/check (if changed): cargo clippy -p openhuman -- -D warnings (the exact CI Lite "Rust Quality" command) passes locally
• Tauri fmt/check (if changed): N/A (shell untouched)

Validation Blocked

• command: N/A
• error: N/A
• impact: N/A

Behavior Changes

• Intended behavior change: none — restores the already-merged intent of chore(deps): update vendored runtime crates #5081/fix(flows): reject an unknown agent_ref at author time instead of mid-run #5114/feat(flows): FlowRunFinished event — fully event-driven runs rail (completes B35) #5115.
• User-visible effect: none.

Parity Contract

• Legacy behavior preserved: yes.
• Guard/fallback/dispatch parity checks: N/A.

Duplicate / Superseded PR Handling

• Duplicate PR(s): N/A
• Canonical PR: N/A
• Resolution (closed/superseded/updated): N/A

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 44 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: db50715f-651a-4703-8019-2223143e752a

📥 Commits

Reviewing files that changed from the base of the PR and between 5b8a9f2 and f03ba0f.

📒 Files selected for processing (5)

• src/openhuman/flows/ops.rs
• vendor/tinyagents
• vendor/tinychannels
• vendor/tinyflows
• vendor/tinyjuice

---

_{Comment @coderabbitai help to get the list of available commands.}