debugging-codegen-pipeline

To fix a codegen pipeline with missing or incorrect outputs, trace upstream artifacts like specs, AST/IR, and manifests to identify the source, validate inputs, and re-run the pipeline to align artifacts without editing the generated code directly.

Codegen pipelines produce non-deterministic outputs due to drift in upstream artifacts. Detect this drift by comparing regenerated artifacts, then enforce upstream corrections in the specs or AST/IR rather than modifying the generated code.

The best way to trace codegen failures to source specs is by following a guided recovery workflow that validates inputs, maps failures through AST/IR and manifests, and directs corrections upstream without touching generated code.

To stabilize a failing codegen pipeline, validate the current context with recommended checks, trace the failure to its source in the upstream artifacts, and re-run the pipeline after directing corrections to the specs or generator.

You should not edit generated code directly to fix a codegen pipeline failure. Instead, enforce upstream corrections by validating inputs, re-running the pipeline, and comparing artifacts to ensure deterministic and traceable outputs.