Fix footnote formatting and convert .txt to .md for pipeline regeneration docs

Co-authored-by: leofang <5534781+leofang@users.noreply.github.com>

Author: Copilot

CONTRIBUTING.md

@@ -207,4 +207,4 @@ flowchart TD
 
 ---
 
-<a id="footnote1">1</a>: `cuda.bindings` follows the contributing guidelines from this repository (`cuda-python`).
+<a>1</a>: The `cuda-python` meta package shares the same license and the contributing guidelines as those of `cuda-bindings`.

ci/.ci-pipeline-regen.txt ci/.ci-pipeline-regen.mdci/.ci-pipeline-regen.txt renamed to ci/.ci-pipeline-regen.md

@@ -1,12 +1,12 @@
 # SPDX-FileCopyrightText: Copyright (c) 2025 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
 # SPDX-License-Identifier: Apache-2.0
 
-CUDA Python CI Pipeline SVG Regeneration Instructions
-====================================================
+# CUDA Python CI Pipeline SVG Regeneration Instructions
 
-This file contains the prompt and requirements for regenerating ci-pipeline.svg with the same styling and content.
+This file contains the prompt and requirements for regenerating `ci-pipeline.svg` with the same styling and content.
 
 ## Styling Requirements
+
 - Hand-drawn Excalidraw-style design with rough, sketchy borders
 - Comic Sans MS font family for all text
 - Imperfect lines and curves that mimic hand-drawn aesthetics
@@ -19,6 +19,7 @@ This file contains the prompt and requirements for regenerating ci-pipeline.svg
   - Release Pipeline: #ffebee background, #f44336 border, #D32F2F text
 
 ## Content Structure
+
 1. **Title**: "CUDA Python CI Pipeline Flow"
 
 2. **Trigger Events** (top blue box):
@@ -51,6 +52,7 @@ This file contains the prompt and requirements for regenerating ci-pipeline.svg
    - Details: Manual workflow dispatch with run ID, Supports individual component or full releases
 
 ## Arrow Requirements
+
 - Main flow arrows: Trigger → Build → Artifact → Test → Release
 - Additional artifact flow arrows (dashed, orange #FF9800):
   - From GitHub Cache (mini CTK) back to Build Stage with "mini CTK reuse" label
@@ -59,6 +61,7 @@ This file contains the prompt and requirements for regenerating ci-pipeline.svg
 - Use stroke-dasharray="5,3" for artifact flow arrows
 
 ## Critical Arrow Positioning Requirements (UPDATED)
+
 **IMPORTANT**: Arrows must NOT overlap with stage boxes. Ensure proper clearance:
 
 1. **Mini CTK reuse arrow** (GitHub Cache → Build Stage):
@@ -74,28 +77,32 @@ This file contains the prompt and requirements for regenerating ci-pipeline.svg
    - Text should be to the LEFT of the arrow for better spacing
 
 ## Font Size Requirements (UPDATED)
+
 - ALL text labels must use consistent 12pt font size for readability
 - No 9pt text - this is too small and hard to read
 - Title: 16pt, Stage headers: 14pt, All other text: 12pt
 
 ## Key Features
+
 - All boxes use rough, hand-drawn paths (not perfect rectangles)
 - Text should be properly sized and positioned within boxes
 - Platform boxes within each stage should be clearly separated
 - Maintain consistent spacing and alignment
 - Orange arrow heads must match the orange arrow color
 
 ## Text Positioning
+
 - Use text-anchor="middle" for centered headers
 - Use text-anchor="start" for left-aligned bullet points
 - Ensure all text fits within their enclosing boxes
 - Use transforms for angled text labels on artifact flow arrows
 - Artifact flow arrow text positioning is critical - follow positioning requirements above
 
 ## Recent Manual Adjustments Applied
+
 - Fixed arrow endpoint positioning to prevent overlap with stage boxes
 - Moved mini CTK reuse arrow endpoint from y=285 to y=295
 - Moved wheel fetch arrow endpoint from y=650 to y=645
 - Repositioned text labels for better visual separation
 - Standardized all text to 12pt font size for consistency
-- Changed arrow heads from black to orange to match arrow color
+- Changed arrow heads from black to orange to match arrow color