fix(ci): rename continuation config parameters with c- prefix

[theochap]

Summary

• Rename all pipeline parameters in CircleCI continuation configs (main.yml, rust-ci.yml, rust-e2e.yml) to use a c- prefix, eliminating naming overlap with the setup config (config.yml)
• This fixes the {"message":"Conflicting pipeline parameters."} error that occurs when API-triggered pipelines (e.g. from opgitgovernance bot) pass non-default parameter values
• The path-filtering mapping in config.yml bridges between the setup parameter names (used by API triggers) and the new c- prefixed continuation parameter names

Context

CircleCI's dynamic configuration has a limitation: when the same pipeline parameter name is defined in both the setup config and the continuation config, API-triggered pipelines fail if they pass a non-default value for that parameter. Webhook and scheduled triggers are unaffected because their parameters stay at default values.

This is a known CircleCI issue discussed in their forums:

• "Conflicting pipeline parameters." at continuation step when pipeline is triggered via UI
• "Conflicting pipeline parameters." at continuation step when pipeline is triggered via curl
• Odd behavior with Continuation and Trigger Pipeline from CircleCI UI

Test plan

• Verify that webhook-triggered pipelines still work (parameters passed through mapping at default values)
• Verify that API-triggered pipelines from opgitgovernance bot no longer fail with "Conflicting pipeline parameters"
• Verify that manual dispatch from CircleCI UI works for all *_dispatch parameters

🤖 Generated with Claude Code

[almanax-ai]

Plan expired

Your subscription has expired. Please renew your subscription to continue using CI/CD integration and other features.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.0%. Comparing base (e6ce426) to head (8f9569d).
⚠️ Report is 3 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop   #19142      +/-   ##
===========================================
+ Coverage     75.7%    76.0%    +0.2%     
===========================================
  Files          692      188     -504     
  Lines        71528    10946   -60582     
===========================================
- Hits         54217     8324   -45893     
+ Misses       17165     2478   -14687     
+ Partials       146      144       -2     

Flag	Coverage Δ
cannon-go-tests-64	66.4% <ø> (-0.9%)	⬇️
contracts-bedrock-tests	81.6% <ø> (-0.1%)	⬇️
unit	?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 510 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[sebastianst]

CircleCI parameters are really a mess to deal with. I'm wondering if there's a better way to pass through params.