dev-review-diagrams

To validate diagram correctness before pushing, you cross-check registered diagrams against lesson README content, parsing diagram code references and README descriptions to verify data flow, axis labeling, and pipeline steps.

Diagram validation in CI prevents regressions by integrating pre-push checks that cross-reference the DIAGRAMS dictionary with README documentation, catching inconsistencies in GPU, math, and engine tracks before they reach review.

Yes, you can automate diagram review by reading scripts/forge_diagrams to enumerate registered diagrams, parsing lesson READMEs to extract descriptions, and executing verification logic to ensure the diagram matches the README.

The best way to cross-check diagrams against lesson documentation is to parse diagram code references and README descriptions, verifying data flow, axis labeling, and pipeline steps for consistency before pushing changes.

Yes, diagram review integrates into pre-push or CI workflows to prevent diagram-related regressions specifically in GPU, math, and engine tracks by validating diagram correctness against README documentation.

Your lesson diagram may not match the README because the verification logic checks the DIAGRAMS dictionary against README content, detecting inconsistencies in data flow, axis labeling, or pipeline steps that require correction before pushing.