sync-change

To keep pipeline documentation consistent after structural changes, you can run an automated synchronization process that aligns README.md, orchestrator SKILL.md, and progress_utils.py. This prevents drift and ensures all references stay aligned across your pipeline files.

Resolving contradictions across pipeline documentation requires detecting inconsistencies between sources and proposing actionable resolution options. This minimizes drift and guides manual resolution to maintain a single source of truth across files.

To synchronize orchestrator frontmatter and progress utilities after adding or removing stages, apply an automated documentation alignment process. This enforces correct progress_utils.py API usage and checks for contradictions across the updated outputs.

Yes, automated documentation alignment works for changes to output folders and skill frontmatter. It synchronizes these structural updates across README.md and orchestrator files, checking for contradictions and surfacing actionable resolutions to maintain consistency.

You should run documentation synchronization after making non-trivial structural changes to your pipeline, such as stage renumbering, renaming, adding or removing stages, and modifying output folders. This ensures all tracked files remain in sync.