fix(team): preserve anyhow cause chain in backend RPC error envelopes (OPENHUMAN-TAURI-AD)

[CodeGhost21]

Summary

• Switches both map_err sites in team::ops::get_authed_value from plain e.to_string() to format!(\"{e:#}\").
• Same anyhow-chain-rendering fix as PR fix(whatsapp_data): preserve anyhow cause chain in RPC error envelopes (OPENHUMAN-TAURI-6B) #1639 (whatsapp_data) — the report_error doc-string in core/observability.rs calls out this exact failure mode (referencing OPENHUMAN-TAURI-B2): "Without this, anyhow's default to_string() only emits the outermost context and the underlying cause is dropped — making the captured Sentry event undiagnosable."

This is not a Sentry-skip — it's the inverse. The current Sentry events are too vague to act on; the fix makes them actionable so we can diagnose the actual root cause.

Fixes OPENHUMAN-TAURI-AD (2 occurrences on openhuman@0.53.35, Windows user in St. Petersburg, Russia).

Why the chain matters here

api::rest::authed_json wraps the underlying reqwest error with .context(format!(\"backend request {} {}\", method, path)). The anyhow chain at the failure site is:

• outer: \"backend request GET /teams\"
• cause: reqwest::Error — could be connect timeout, DNS failure, TLS handshake error, immediate connection refused, non-2xx HTTP status, …

e.to_string() renders only the outer label. The Sentry events all read \"backend request GET /teams\" with no underlying cause — and elapsed_ms=49 is way too short for a real network timeout, so the true cause (immediate refusal? token rejected mid-request? URL parse error?) is the only signal worth surfacing.

{e:#} (anyhow's alternate format) joins the outer context plus every wrapped cause with \": \", so the next event will tell us why the request failed and we can fix the underlying condition.

Why fix once in get_authed_value

Every team RPC (list_teams, get_team, list_members, get_usage, create_team, update_team, delete_team, switch_team, leave_team, join_team) routes through this one helper, so a single change covers the whole domain — no per-handler fanout needed.

Test plan

• cargo check --lib — no new warnings.
• cargo fmt.
• No new tests: the {e:#} rendering contract is already covered by core::observability::tests::anyhow_chain_is_rendered_in_full. Behavioural coverage here would require a synthetic reqwest failure fixture — disproportionate for a single-helper format-specifier fix.

Follow-up

Once this ships and the next Sentry event lands with the cause chain visible, a targeted follow-up PR can address the underlying condition. The 49ms elapsed time argues against "network unreachable" (PR #1601 would silence those once their full message includes \"error sending request for url\" via this chain) — more likely an immediate transport refusal or auth boundary, both of which warrant their own handling.

Summary by CodeRabbit

• Bug Fixes

  • Enhanced error message formatting to display complete error context chains, providing more detailed information for diagnosing issues.

• Documentation

  • Added inline comments documenting how error messages are surfaced in the system.

[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: 3b350321-9df8-4ff1-b123-389b9fdb8349

📥 Commits

Reviewing files that changed from the base of the PR and between 9160317 and 80d9eb2.

📒 Files selected for processing (1)

• src/openhuman/team/ops.rs

---

📝 Walkthrough

Walkthrough

get_authed_value now formats backend client construction and request failures using Rust's {e:#} rendering to preserve full error chain context instead of simple to_string() display. Inline comments were added to document the improved error diagnostic visibility.

Changes

Backend error diagnostics

Layer / File(s)	Summary
Backend error formatting with chained context src/openhuman/team/ops.rs	get_authed_value switches backend client construction and authed request failures to use format!("{e:#}"), preserving the full error chain for better diagnostics, with comments explaining the change.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Suggested reviewers

• senamakel

Poem

🐰 Errors once whispered their surface tales,
Now chains of context rise through the veils;
With {e:#} format, diagnostics sing,
Full cause and context—a debugging wing! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically identifies the main change: preserving the anyhow cause chain in error rendering for team RPC error handling, which matches the core technical change in the changeset.
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.}