cyberneticlibrary

Run API client quality and health audit

healthworkflowsetup L32
cavi-ai/cavi-api-client
What it does

Run quality gate, API diagnosis, and repo audit in parallel then synthesize

Best for

Single comprehensive health gate before release combining quality, API surface, and repo state in one report.

Inputs
  • · package root cwd (implicit)
Outputs
  • · GO / NO-GO health summary
  • · quality gate: pass/fail per step (test, typecheck, build, lint, pack)
  • · API diagnosis: divergent REST count, native drift status, live gateway tallies
  • · repo audit: branch, cleanTree, local/npm version, latest CI, open PR count
Requires
  • · pnpm (verify, typecheck, typecheck:gate, build)
  • · node (diagnose.mjs)
  • · git CLI
  • · gh (GitHub CLI)
  • · OPENCLAW_SOURCE_DIR optional for native drift (peer repo)
Preconditions
  • · pnpm installed and working
  • · package.json scripts defined (verify, typecheck, build)
  • · git repo initialized
  • · gh CLI authenticated (for PR list, run list)
  • · node runtime available
Failure modes
  • · pnpm verify fails → gate.pass=false, details in steps array (non-fatal)
  • · diagnose.mjs not found → diagnosis skipped gracefully
  • · OPENCLAW_SOURCE_DIR unset → live probing skipped, native drift marked skipped (non-fatal)
  • · gh not authenticated → CI/PR audit skipped, other probes proceed
Trust signals
  • · Three independent parallel probes (gate, diagnosis, audit) — single point of failure impossible
  • · Zero-warnings policy enforced in synthesis (warnings block a clean gate)
  • · Live API probing on gateway if GATEWAY_URL set (finds real divergence)
  • · Native drift detection via peer OPENCLAW_SOURCE_DIR if available