Add CI infrastructure overview with hand-drawn SVG diagram, Mermaid alternative, and enhanced artifact flow visualization to CONTRIBUTING.md

[Copilot]

• Add CI infrastructure overview with hand-drawn SVG diagram and artifact flow visualization to CONTRIBUTING.md
• Create vectorized SVG diagram with color-coded stages for better visualization
• Address review feedback: remove specific runner names, fix GPU model references, update cache descriptions
• Convert SVG to hand-drawn Excalidraw-style design with rough, sketchy borders
• Add artifact flow arrows showing mini CTK cache reuse and wheel fetching
• Create comprehensive regeneration reference file for future updates
• Add Mermaid diagram alternative for interactive visualization
• Enhanced artifact flow arrows to TEST STAGE showing both mini CTK reuse and wheel fetch dependencies
• Document parallel execution details for build and test stages
• Add table of contents and reorganize document structure
• Fix SVG arrow colors and add wheel upload label based on review feedback
• Change artifact flow arrows from black to orange for consistent visual language
• Update Mermaid diagram to include wheel upload arrow with orange dashed styling

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[leofang]

@copilot

The flow looks ok. But I'd like to highlight

• cuda-pathfinder artifact flows from the main branch's artifact space to that of the backport branch
• older cuda-bindings artifacts flow in the opposite direction

Please find a way to present it in the flowchart.

Also, if possible please generate a vectorized .svg file, and let's see how it looks. We will decide later if we want to revert back to the ascii-based one, like what you've generated.

[Copilot]

@copilot

The flow looks ok. But I'd like to highlight
...

I've updated the flowchart to highlight the artifact flows between branches and created an SVG version as requested. The branch-specific artifact flow section now explicitly shows:

• cuda-pathfinder artifacts flowing from main branch to backport branches
• older cuda-bindings artifacts flowing from backport branches to main branch

I've also created a vectorized SVG diagram (ci-pipeline.svg) with color-coded stages for better visualization. The documentation now includes both the SVG version and the ASCII version for different viewing preferences.

Commit: 2816809

[leofang]

@copilot

[leofang]

@copilot

[Copilot]

@copilot throughout this PR, I don't want to mention "Push to pull-request/* branches" as a trigger event. As mentioned in an earlier comment, this is an implementation detail of the CI that is out of...

Removed "Push to pull-request/* branches" trigger event from all CI documentation files as requested. Updated CONTRIBUTING.md Mermaid diagram, ci/ci-pipeline.svg, and ci/.ci-pipeline-regen.md regeneration instructions to exclude implementation-specific triggers.

Commit: 9ce239a

[rparolin]

👍 lgtm

[rwgk]

There are still some minor glitches (a couple superfluous arrows), but I think this isn't worth our time, it's already great for merging.

[leofang]

Thanks, Ralf & Rob!

There are still some minor glitches (a couple superfluous arrows), but I think this isn't worth our time

Yeah I am really unhappy with the arrow heads, but the SVG code looks fine to me and I don't have time to dig further.

FWIW, I meant to ask if you have any preference over SVG or Mermaid. I don't, so let me keep both for now and wait until someone has an opinion 🙂

[github-actions]

Doc Preview CI
Preview removed because the pull request was closed or merged.