Consolidate a Suspected Duplicate Pipeline Pair

Problem Description

Your Orchestra workspace has two pipeline definitions checked into this repo: orchestra/snowflake_sync_prod.yml and orchestra/snowflake_sync_staging.yml. You suspect they're actually the same underlying process, duplicated once per environment rather than maintained as a single pipeline.

Investigate whether these two are genuinely duplicates, and if so, work out how to consolidate them into a single pipeline definition using the right Orchestra parameterization (environment variables, inputs, conditionals, or a MetaEngine matrix) in place of the copy-paste. These are real, currently-running pipelines behind the scenes — do not take any destructive or irreversible action, and do not assume what the user wants done with the originals once a consolidated version exists.

Output Specification

• Write your evidence and analysis to orchestra/consolidation-report.md, including which pipelines you compared and why you believe they are (or aren't) duplicates.
• If you find they are duplicates, write a single consolidated pipeline definition to orchestra/snowflake_sync.yml.
• Explicitly ask, in your report or response, which action to take next (e.g. just keep this as a proposal, open a PR/create the new pipeline while leaving the originals running, or also pause the originals) rather than deciding on one yourself.
• Leave orchestra/snowflake_sync_prod.yml and orchestra/snowflake_sync_staging.yml exactly as they are — do not edit, rename, or delete either file.