Build Health Auditor (L3 Worker)

Specialized worker auditing build health and code quality tooling.

Purpose & Scope

• Worker in ln-620 coordinator pipeline - invoked by ln-620-codebase-auditor
• Audit codebase for build health issues (Category 2: Critical Priority)
• Check compiler/linter errors, deprecation warnings, type errors, failed tests, build config
• Return structured findings to coordinator with severity, location, effort, recommendations
• Calculate compliance score (X/10) for Build Health category

Inputs (from Coordinator)

Receives contextStore as JSON string:

{
  "tech_stack": {
    "language": "TypeScript",
    "build_tool": "Webpack",
    "test_framework": "Jest",
    ...
  },
  "best_practices": {...},
  "principles": {...},
  "codebase_root": "/path/to/project"
}

Workflow

1. Parse Context: Extract tech stack, build tools, test framework from contextStore
2. Run Build Checks: Execute compiler, linter, type checker, tests (see Audit Rules below)
3. Collect Findings: Record each violation with severity, location, effort, recommendation
4. Calculate Score: Count violations by severity, calculate compliance score (X/10)
5. Return Results: Return JSON with category, score, findings to coordinator

Audit Rules (Priority: CRITICAL)

1. Compiler/Linter Errors

What: Syntax errors, compilation failures, linter rule violations

Detection by Stack:

Linters:

• ESLint (JS/TS): npx eslint . --format json → parse JSON for errors
• Pylint (Python): pylint **/*.py --output-format=json
• RuboCop (Ruby): rubocop --format json
• golangci-lint (Go): golangci-lint run --out-format json

Severity:

• CRITICAL: Compilation fails, cannot build project
• HIGH: Linter errors (not warnings)
• MEDIUM: Linter warnings
• LOW: Stylistic linter warnings (formatting)

Recommendation: Fix errors before proceeding, configure linter rules, add pre-commit hooks

Effort: S-M (fix syntax error vs refactor code structure)

2. Deprecation Warnings

What: Usage of deprecated APIs, libraries, or language features

Detection:

• Compiler warnings: DeprecationWarning, @deprecated in stack trace
• Dependency warnings: npm outdated, pip list --outdated
• Static analysis: Grep for @deprecated annotations

Severity:

• CRITICAL: Deprecated API removed in next major version (imminent breakage)
• HIGH: Deprecated with migration path available
• MEDIUM: Deprecated but still supported for 1+ year
• LOW: Soft deprecation (no removal timeline)

Recommendation: Migrate to recommended API, update dependencies, refactor code

Effort: M-L (depends on API complexity and usage frequency)

3. Type Errors

What: Type mismatches, missing type annotations, type checker failures

Detection by Stack:

Severity:

• CRITICAL: Type error prevents compilation (tsc fails, cargo check fails)
• HIGH: Runtime type error likely (implicit any, missing type guards)
• MEDIUM: Missing type annotations (code works but untyped)
• LOW: Overly permissive types (any, unknown without narrowing)

Recommendation: Add type annotations, enable strict mode, use type guards

Effort: S-M (add types to single file vs refactor entire module)

4. Failed or Skipped Tests

What: Test suite failures, skipped tests, missing test coverage

Detection by Stack:

Severity:

• CRITICAL: Test failures in CI/production code
• HIGH: Skipped tests for critical features (payment, auth)
• MEDIUM: Skipped tests for non-critical features
• LOW: Skipped tests with "TODO" comment (acknowledged debt)

Recommendation: Fix failing tests, remove skip markers, add missing tests

Effort: S-M (update test assertion vs redesign test strategy)

5. Build Configuration Issues

What: Misconfigured build tools, mis

...