dotfile-audit

To fix DOT pipeline validation warnings, audit the graph structure for required attributes, complete failure paths, and correct human-gate wiring. Run validation iteratively, applying fixes to edges and parallel fan-out/fan-in synchronization until zero warnings remain.

A structural DOT graph audit checks required graph attributes, start and exit node counts, failure-path completeness, human-gate configuration, diamond edge conditions, and parallel fan-out/fan-in synchronization to ensure clean validation output.

To reconcile a spec with a DOT pipeline, cross-reference the design document to confirm phases, implement and test components, tech stack references, quality gates, testing frameworks, and requested human gates match the expected pipeline structure.

Yes, you can validate hand-written DOT pipeline files for execution readiness by checking full spec coverage, confirming correct edge conditions, and running repeated validation checks until the graph reports zero errors and zero warnings.

CI linting fails on third-party DOT files due to missing graph attributes, incomplete failure paths, or incorrect parallel fan-out/fan-in synchronization, requiring a structural audit and repeated validation runs to achieve clean output.