Detect native .node binary size regressions by adding PR stats comment

Detect native .node binary size regressions by adding PR stats comment targets a $1.8B = 150,000 engineering teams x $12,000 ACV (enterprise developer-tooling + CI analytics) total addressable market with low saturation and a year-over-year growth rate of 20-30% — CI/DevTools and observability tooling continue growing as engineering orgs invest in developer experience.

Key trends driving demand: Native-module adoption -- Rust and native bindings (SWC, Rust-based tooling) produce large .node artifacts that affect install size and cold-starts; teams want visibility.; Shift to CI-first quality gates -- PR-level checks and comments are primary feedback channels, increasing demand for actionable CI metrics.; GitHub Actions ecosystem expansion -- Marketplace & Actions-based integrations make it trivial to add small checks at low friction.; Performance budgets & developer experience -- organizations apply explicit budgets beyond JS bundles to binary artifacts and infrastructure costs..