Add section numbering and formatting to GPU + CPU TEE article

[igotstatik]

Adds section numbering (1, 2, 3 / 3.1, 1.1) to the GPU + CPU TEE requirements article, bolds system names with trailing periods in 3.1/3.2, duplicates driver release links across both Blackwell sections (2.2, 2.3), and updates the 1.2/1.3 TEE configuration lists.

Summary by CodeRabbit

• Documentation
  • Reorganized GPU-CPU-TEE requirements documentation with improved hierarchical structure and explicit numbering for enhanced clarity and navigation
  • Expanded and clarified guidance on supported GPU and CPU configurations, including updated technical specifications and device qualification details
  • Refined unsupported configurations documentation with additional context on CPU-GPU pairings

[coderabbitai]

Walkthrough

This PR restructures the GPU-CPU TEE Requirements documentation with explicit numbered sections and subsections throughout. Core TEE Requirements, Technical Insights, and Unsupported Configurations sections are reorganized with consistent numbering; CPU configuration descriptions are updated with clarified processor names and AMD SEV-SNP support constraints starting from AMD Genoa.

Changes

Documentation Structure Reorganization

Layer / File(s)	Summary
Core TEE Requirements section restructuring docs/fundamentals/gpu-cpu-tee-requirements.md	The "Core TEE Requirements" section is renumbered into explicit subsections for TEE Mode Compatibility, Recommended Instance Types, and Supported GPU + CPU Configurations with a dedicated "Expected" subheading.
Technical Insights GPU and TEE configuration sections docs/fundamentals/gpu-cpu-tee-requirements.md	The "Hopper and Blackwell in TEE Mode" section is renumbered as section 1, GPU & Memory Boundaries is numbered as subsection 1.1, and TEE configurations are split into numbered subsections for Hopper (SPT CC and PPCIe), Blackwell HGX/DGX (SPT CC and MPT CC), and RTX PRO 6000.
NVIDIA Confidential Computing Driver Releases section docs/fundamentals/gpu-cpu-tee-requirements.md	The driver releases overview is reframed as section 2 with subsections for Hopper (2.1), Blackwell HGX/DGX NVLink (2.2), and RTX PRO 6000 (2.3); driver-release links are preserved while structural numbering is added.
Intel CPU Support and narrative sections renumbering docs/fundamentals/gpu-cpu-tee-requirements.md	Remaining narrative sections are renumbered: Intel CPU Support for TEE becomes section 3, Certification vs Functioning becomes section 4, OEM Validation Practices becomes section 5, and System Configuration Matters becomes section 6.
Unsupported Configurations with updated CPU details docs/fundamentals/gpu-cpu-tee-requirements.md	Unsupported Configurations is renumbered as section 7 with subsections 7.1 (GPU Configurations) and 7.2 (CPU Configurations); CPU incompatibility text is updated with clarified Sapphire Rapids naming and notes that Super Protocol support for AMD SEV-SNP starts from AMD Genoa.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Super-Protocol/docs#431: Both PRs modify docs/fundamentals/gpu-cpu-tee-requirements.md; this PR restructures and clarifies existing content while the related PR introduces the initial article content.

Poem

A rabbit hops through numbered rows,
With sections neat in careful throes,
From GPU dreams to CPUs bright,
The structure shines with organization's light! 🐰📄

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: adding section numbering and formatting to the GPU + CPU TEE requirements article, which aligns with the file modifications documented in the raw summary.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch article/gpu-cpu-tee-numbering

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/fundamentals/gpu-cpu-tee-requirements.md`:
- Line 18: The renumbered heading "1. TEE Mode Compatibility" changed
autogenerated anchor IDs and will break existing deep links; before each
renumbered heading (e.g., the "1. TEE Mode Compatibility" heading and the other
listed headings) insert an explicit HTML anchor tag using the established anchor
naming scheme (the pre-existing anchor slug used prior to adding numeric
prefixes) so the anchor remains stable; update headings in
docs/fundamentals/gpu-cpu-tee-requirements.md by placing the custom anchor tag
immediately above each affected heading (use the exact original slug string for
anchors), and apply the same pattern to the other headings referenced in the
comment to preserve existing inbound links.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 4a25d970-8fc7-44a7-8563-096c5b170770

📥 Commits

Reviewing files that changed from the base of the PR and between 3eef7e3 and 6778985.

📒 Files selected for processing (1)

• docs/fundamentals/gpu-cpu-tee-requirements.md

[coderabbitai]

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Preserve stable deep-link anchors after heading renumbering.

Adding numeric prefixes to headings changes autogenerated anchor IDs, which can break existing inbound links/bookmarks. Add explicit custom anchor tags (using the pre-existing anchor naming scheme) before each renumbered heading to keep links stable.

Proposed pattern

-### 1. TEE Mode Compatibility
+<a id="tee-mode-compatibility"></a>
+### 1. TEE Mode Compatibility

-### 2. Recommended Instance Types
+<a id="recommended-instance-types"></a>
+### 2. Recommended Instance Types

-### 3. Supported GPU + CPU Configurations
+<a id="supported-gpu-cpu-configurations"></a>
+### 3. Supported GPU + CPU Configurations

Apply the same pattern to the rest of newly numbered headings.

As per coding guidelines, "Follow the established cross-referencing pattern with custom anchor tags".

Also applies to: 22-22, 28-28, 30-30, 49-49, 67-67, 83-83, 93-93, 109-109, 118-118, 129-129, 139-139, 143-143, 152-152, 160-160, 170-170, 180-180, 192-192, 202-202, 213-213, 217-217, 229-229, 235-235

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/fundamentals/gpu-cpu-tee-requirements.md` at line 18, The renumbered
heading "1. TEE Mode Compatibility" changed autogenerated anchor IDs and will
break existing deep links; before each renumbered heading (e.g., the "1. TEE
Mode Compatibility" heading and the other listed headings) insert an explicit
HTML anchor tag using the established anchor naming scheme (the pre-existing
anchor slug used prior to adding numeric prefixes) so the anchor remains stable;
update headings in docs/fundamentals/gpu-cpu-tee-requirements.md by placing the
custom anchor tag immediately above each affected heading (use the exact
original slug string for anchors), and apply the same pattern to the other
headings referenced in the comment to preserve existing inbound links.