R CMD INSTALL and install.packages() structured logging for CI/CD failure classification

Automated R deployments rely on R CMD INSTALL and install.packages() for package installation. The goal is to programmatically classify installation failures in CI/CD pipelines by cause — missing system dependencies, compiler mismatches, version skew, or network issues — without fragile text parsing.

Current behavior is human-readable stdout/stderr with no JSON or structured logging, and only a binary exit code. Message wording varies across R versions and operating systems, and localized builds can change diagnostics. Tools like pkgdepends and pak provide richer metadata when invoked directly but do not wrap the base installation pathway used by common CI recipes. No CRAN or Bioconductor policy mandates structured build logs.

Is there a documented configuration option or environment variable that makes R CMD INSTALL or install.packages() emit machine-readable output? Is there a stable, version-agnostic mapping of exit codes or log patterns to failure classes? Can structured artifacts be produced without replacing the base installation pathway used in existing pipelines?