fix(composio/triage): demote provider-config-rejection rollups (Sentry TAURI-RUST-1V)

[oxoxDev]

Summary

• Routes [composio][triage] run_triage failed through the central observability classifier instead of raw tracing::error! — so user-config / budget-exhausted rollups from the upstream provider chain get demoted to info-level breadcrumbs.
• Adds "may not be available on your provider" to is_provider_config_rejection_message — the canonical phrase emitted by reliable.rs:332 when the user's reliability.model_fallbacks chain is misconfigured.
• Net effect: drops the bulk of self-hosted Sentry TAURI-RUST-1V (10,692 events / 14d) where the inner provider attempts the provider layer already demoted were re-surfaced by the outer composio re-emit.

Problem

Self-hosted Sentry tauri-rust project's #4 unresolved by event count (14d, sort=freq) is [composio][triage] run_triage failed at 10,692 events. Breadcrumbs show every event boils down to:

[llm_provider] native_chat budget-exhausted 400 — not reporting to Sentry          (correct demote, inner)
Non-retryable error, moving on
Exhausted retries, trying next provider/model
llm_provider.reliable_chat skipped expected budget-exhausted error: The model `chat-v1` may not be available on your provider. Configure a fallback chain via `reliability.model_fallbacks` in …    (correct demote, inner)
[triage::evaluator] agent turn dispatch failed
[composio][triage] run_triage failed       ← raw tracing::error! emits a Sentry error event

The reliable-provider stack and the inference observability layer already classify these as user-config — but the bus-level re-emit at memory_sync/composio/bus.rs:354 used a raw tracing::error! that bypassed the classifier entirely.

Root cause is user-side: the user's reliability.model_fallbacks config doesn't list a model the provider actually serves. Remediation = fix that config. Sentry has no remediation path.

Solution

Two surgical changes, kept as separate micro-commits for review:

1. src/openhuman/inference/provider/config_rejection.rs — append "may not be available on your provider" to the PHRASES table feeding is_provider_config_rejection_message. Canonical phrase, anchored to reliable.rs:332 (the sole producer in-tree). Comment cross-links the call site so future drift of that wording is caught at review.

2. src/openhuman/memory_sync/composio/bus.rs — swap the raw tracing::error! at L354 with crate::core::observability::report_error_or_expected(..., "composio", "trigger_triage", &[("label", …)]). Same structured fields as before, but now the classifier runs. Genuine runtime bugs that don't classify still surface as full Sentry errors.

The two changes are additive; either landed alone would partially help, but only the pair fully closes the loop.

Submission Checklist

• Tests added or updated (happy path + at least one failure / edge case) per Testing Strategy
• Diff coverage ≥ 80% — changed lines (Vitest + cargo-llvm-cov merged via diff-cover) meet the gate enforced by .github/workflows/coverage.yml. Run pnpm test:coverage and pnpm test:rust locally; PRs below 80% on changed lines will not merge.
• Coverage matrix updated — added/removed/renamed feature rows in docs/TEST-COVERAGE-MATRIX.md reflect this change (or N/A: behaviour-only change)
  • N/A: behaviour-only change — classifier anchor + call-site swap, no new user-facing feature row.
• All affected feature IDs from the matrix are listed in the PR description under ## Related
• No new external network dependencies introduced (mock backend used per Testing Strategy)
• Manual smoke checklist updated if this touches release-cut surfaces (docs/RELEASE-MANUAL-SMOKE.md)
  • N/A: observability classifier internals — no release-cut surface touched.
• Linked issue closed via Closes #NNN in the ## Related section
  • N/A: Sentry-only fix — no GitHub issue. Sentry-Issue trailer in ## Related instead.

Impact

• Runtime/platform: desktop only. Demoted events still appear as info! breadcrumbs in local trace, so support can still inspect them. Sustained outages — were they ever to indicate a real triage bug — would surface via separate health/escalation paths.
• Performance: negligible (classifier already runs on the surrounding paths; one extra substring scan per failed triage turn).
• Security/migration: none.
• Compatibility: no public API change.

Related

• Sentry-Issue: TAURI-RUST-1V (self-hosted sentry.tinyhumans.ai → tauri-rust project, 10,692 events / 14d)
• Pattern precedent: fix(observability,composio): demote direct-mode Composio 401/Invalid API key noise (Sentry TAURI-RUST-X9) #2481 (composio direct-mode 401 demote), fix(observability,embeddings): demote Ollama embed user-config rejections (Sentry TAURI-RUST-XS + MA/KM/GX) #2612 (Ollama embed user-config demote), fix(app): guard CEF IPC fallback sync throw via safeInvoke wrapper (Sentry TAURI-REACT-7 + 6) #2619 (CEF IPC fallback guard)
• Closes:
• Follow-up PR(s)/TODOs:
  • Companion PRs for self-hosted Sentry TAURI-RUST-15 (Discord supervision restart-storm, 11.4k events) and TAURI-RUST-34H (Cloudflare anti-bot 500 wrap, 8.9k events) — coming behind this one to keep PR surface small.
  • Phase 7 Step 4.5 auto-resolve grep regex currently only matches OPENHUMAN-(TAURI|REACT|CORE)-… and BACKEND-ALPHAHUMAN-… shapes; self-hosted prefix is TAURI-RUST-…. Widen the regex (separate workflow-tooling PR) so the post-merge Sentry resolve sweep finds these IDs.

---

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

Linear Issue

• Key: N/A: Sentry-only — no Linear issue
• URL: N/A: Sentry-only — no Linear issue

Commit & Branch

• Branch: fix/sentry-1v-composio-triage-noise
• Commit SHA: $(git rev-parse HEAD)

Validation Run

• `pnpm --filter openhuman-app format:check`
  • N/A: no app/ files touched
• `pnpm typecheck`
  • N/A: no app/ files touched
• Focused tests: `cargo test --lib openhuman::inference::provider::config_rejection` (7/7 passed)
• Rust fmt/check (if changed): `cargo fmt --check` clean; `cargo check --manifest-path Cargo.toml` clean (pre-existing warnings only, not from this PR)
• Tauri fmt/check (if changed):
  • N/A: no Tauri shell files touched

Validation Blocked

• `command:`
• `error:`
• `impact:`

Behavior Changes

• Intended behavior change: Composio-triage failures whose underlying err already classifies as user-state via the central observability classifier now demote to info-level breadcrumbs instead of emitting Sentry errors.
• User-visible effect: None — UI surfaces of the underlying conditions (budget-exhausted toasts, model-unavailable banners) are emitted at the inner layers and unchanged. Only the Sentry noise drops.

Parity Contract

• Legacy behavior preserved: All structured fields previously logged (`label`, `error`) are preserved in the routed report's message and tag set. Genuine runtime errors that don't classify still reach Sentry.
• Guard/fallback/dispatch parity checks: `is_provider_config_rejection_message` continues to require an anchored substring match — false-positive surface is identical to existing entries; new entry is the canonical `reliable.rs:332` remediation phrase.

Duplicate / Superseded PR Handling

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

Summary by CodeRabbit

• Bug Fixes

  • Improved detection of provider configuration-related error messages to correctly classify fallback scenarios.

• Chores

  • Enhanced error reporting system to better capture and communicate diagnostics for internal monitoring and troubleshooting.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: deb77e97-5986-4d63-ab64-cad20effa3b7

📥 Commits

Reviewing files that changed from the base of the PR and between 844a26c and 5fa4ca8.

📒 Files selected for processing (2)

• src/openhuman/inference/provider/config_rejection.rs
• src/openhuman/memory_sync/composio/bus.rs

---

📝 Walkthrough

Walkthrough

This PR extends provider config-rejection message detection to classify model-fallback exhaustion remediation as user-config state, and updates Composio triage error handling to route through the centralized observability system instead of direct logging.

Changes

Error Classification and Observability

Layer / File(s)	Summary
Provider config-rejection detection src/openhuman/inference/provider/config_rejection.rs	Adds "may not be available on your provider" substring to the config-rejection phrase list with documentation linking it to the reliable model-fallback exhaustion path. Introduces a test verifying both the multi-line rollup wrapper and the inner remediation message are correctly detected by is_provider_config_rejection_message.
Composio triage observability routing src/openhuman/memory_sync/composio/bus.rs	Replaces direct tracing::error! with report_error_or_expected in the run_triage error branch, routing failures through centralized observability with formatted error detail, category/context ("composio", "trigger_triage"), and label attribute.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• tinyhumansai/openhuman#2309: Previously extended is_provider_config_rejection_message to recognize additional provider-config rejection message shapes.
• tinyhumansai/openhuman#2239: Introduced ExpectedErrorKind::ProviderConfigRejection and report_error_or_expected routing that this PR now leverages for Composio trigger triage.
• tinyhumansai/openhuman#1712: Main PR introducing the "may not be available on your provider" remediation message from the ReliableProvider model-fallback exhaustion path.

Suggested labels

bug

Suggested reviewers

• graycyrus
• senamakel

---

🐰 A little hop through error flows,
Where fallbacks fail and messages glow,
Now config rejects are known,
And observability's shown,
A cleaner path wherever we go! 🌿

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: demoting provider-config-rejection rollups in the composio triage path to reduce noisy Sentry errors. It directly reflects the core objective of both coordinated code changes.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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

[graycyrus]

LGTM — clean, surgical fix with good test coverage.

Nice work routing the composio triage error path through report_error_or_expected instead of the raw tracing::error!. The new phrase anchor in config_rejection.rs is well-scoped (sole producer at reliable.rs:332) and the cross-referencing comments will help catch drift.

Both changes follow the established pattern used across ~10 other call sites in the codebase. Tests cover the multi-line rollup and bare phrase cases. The {e:#} alternate Display for the error chain in the detail string is correct.

CI note: all failures are Docker login (GHCR auth) issues for the contributor's fork — unrelated to these changes. The Tauri build, E2E suites, and core image build all pass.