Detect and explain common React runtime errors in CI and dev tools

Detect and explain common React runtime errors in CI and dev tools targets a $9.6B = 2,000,000 dev teams x $4,800 ACV. Rationale: global developer teams building web apps that would pay for per-team observability/developer-experience tooling at roughly $400/mo. total addressable market with medium saturation and a year-over-year growth rate of 12% - growth of developer tools and observability markets driven by more client-side apps and CI adoption.

Key trends driving demand: React ecosystem scale -- large installed base means many recurring, framework-specific runtime errors that generic tools miss.; CI and test automation -- teams run tests and CI on every push so surfacing actionable diagnostics there improves TTD and is high value.; Shift to developer experience metrics -- companies are investing to reduce MTTR and time-to-fix which increases willingness to pay.; AI pattern recognition for code -- improved models can map error traces to known fixes and code snippets, making automated explanations feasible..