fix(observability): capture AI-CLI stderr + surface exhausted provider failures to Sentry

[JSONbored]

Summary

The self-host claude/codex review CLIs intermittently fail with an opaque claude_code_exit_1 / codex_exit_1, and provider outages never surface in Sentry. Two gaps:

1. defaultSpawn captured stdout but discarded stderr — where the CLI's real error (auth failure, rate limit, model-not-supported, OOM) actually lands. The exit code alone is undiagnosable.
2. Per-attempt provider failures log at warn; the central Sentry forwarder only ships error/fatal, so a genuine reviewer outage is invisible.

Changes

• src/selfhost/ai.ts — defaultSpawn now captures the child's stderr and threads it into the claude_code_exit_* / codex_exit_* error message (truncated to 500 chars). The stderr field is optional on SpawnFn so existing spawn stubs are unaffected.
• src/services/ai-review.ts — runWorkersOpinion emits one ai_review_provider_exhausted log at error level once all models × attempts have thrown (the reviewer is genuinely down). The noisy per-attempt retries stay at warn. A model that runs but returns unparseable output is not an exhaustion (no provider error) and stays silent.

Testing

• defaultSpawn captures a failing CLI's stderr (real subprocess) and surfaces it on the exit error.
• stderr appears in both the claude and codex exit errors (mocked).
• ai_review_provider_exhausted fires at error level when every attempt throws; does not fire on ran-but-unparseable output.
• Affected suites green (152 tests); patch coverage 100% on changed lines.

Advances #26 (comprehensive Sentry instrumentation — surface all failures).

[superagent-security]

Superagent found 1 security concern(s).

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.51%. Comparing base (bd59608) to head (20f47ac).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1605   +/-   ##
=======================================
  Coverage   95.50%   95.51%           
=======================================
  Files         204      204           
  Lines       22018    22030   +12     
  Branches     7957     7959    +2     
=======================================
+ Hits        21029    21041   +12     
  Misses        413      413           
  Partials      576      576           

Files with missing lines	Coverage Δ
src/selfhost/ai.ts	99.44% <100.00%> (+0.02%)	⬆️
src/services/ai-review.ts	98.64% <100.00%> (+0.01%)	⬆️

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[loopover-orb]

Warning

🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨

⏸️ Gittensory review — held for maintainer review

4 files · 1 AI reviewers · no blockers · readiness 66/100 · CI pending · blocked

⏸️ Held for maintainer review — Touches a guarded path — held for manual review

Signal	Result	Evidence
Code review	✅ No blockers	1 reviewers, synthesized
Linked issue	⚠️ Missing	No linked issue or no-issue rationale found.
Related work	✅ No active overlap found	No same-issue or scoped active PR overlap found.
Review load	✅ 20/20	Readiness component derived from cached public PR metadata and labels; size label size:M.
Validation evidence	❌ 5/25	Cached preflight status is hold.
Open PR queue	❌ 3/10	24 open PR(s), 10 likely reviewable, 14 unlinked.
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 80 PR(s), 301 issue(s).
Gate result	⚠️ Not blocking	Advisory; not blocking this PR.

Nits — 1 non-blocking

• Touches a guarded path — held for manual review — A maintainer must review and merge this change.

Review context

• Author: JSONbored
• Role context: owner (maintainer lane)
• Public audience mode: oss maintainer
• Lane context: Repository registration is not available in the local Gittensory cache.
• Public profile languages: not available
• Official Gittensor activity: 80 PR(s), 301 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Treat this as maintainer-lane context rather than normal contributor-lane activity.
• Explain no-issue PR.
• Fix blocker.
• Expect slower review.
• Refresh registry data or choose a registered active repo.
• Link the issue being solved, or explicitly explain why this is a no-issue PR.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Review load = cached public PR metadata such as size labels, changed paths, and preflight status.
• Open PR queue = repo-wide review pressure; it is not a PR quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers.

• Re-run Gittensory review

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.