Remove outdated report-schemas documentation and clean up references

Author: dev-dist

public/samples/DataLink/ClientReportsVerifier.sol

@@ -82,7 +82,7 @@ contract ClientReportsVerifier {
     error InvalidReportVersion(uint16 version);
 
     // ----------------- Report schemas -----------------
-    // More info: https://docs.chain.link/datalink/pull-delivery/reference/report-schemas/v3
+    // Extract schema version from feed ID (first 2 bytes of the feed ID)
     /**
      * @dev DataLink report schema v3.
      *      Prices, bids and asks use 8 or 18 decimals depending on the feed.

src/config/sidebar.ts

@@ -2441,24 +2441,6 @@ export const SIDEBAR: Partial<Record<Sections, SectionEntry[]>> = {
               title: "API, SDKs, Onchain Verification",
               url: "datalink/pull-delivery/reference/api-sdk-onchain-verification",
             },
-            {
-              title: "Report Schemas",
-              url: "datalink/pull-delivery/reference/report-schemas",
-              children: [
-                {
-                  title: "V2",
-                  url: "datalink/pull-delivery/reference/report-schemas/v2",
-                },
-                {
-                  title: "V3",
-                  url: "datalink/pull-delivery/reference/report-schemas/v3",
-                },
-                {
-                  title: "V4",
-                  url: "datalink/pull-delivery/reference/report-schemas/v4",
-                },
-              ],
-            },
           ],
         },
       ],

src/content/datalink/pull-delivery/reference/index.mdx

@@ -10,20 +10,6 @@ isIndex: true
 
 This section provides technical reference documentation for integrating with DataLink pull-delivery feeds. Use these resources to understand data structures, API specifications, and implementation details.
 
-## API and SDK Reference
+## API, SDKs, and Onchain Verification
 
-### API, SDKs, Onchain Verification Reference
-
-[Complete reference](/datalink/pull-delivery/reference/api-sdk-onchain-verification) for DataLink APIs, SDKs, and onchain verification infrastructure. DataLink uses the same APIs, SDKs, and verification infrastructure as Chainlink Data Streams, enabling you to leverage existing integration patterns and tooling.
-
-**Key topics covered:**
-
-- REST API endpoints and authentication
-- Go and Rust SDK documentation
-- WebSocket streaming protocols
-- Onchain verification contracts and methods
-- Integration patterns and best practices
-
-## Report Schemas
-
-Learn about the different [report schema versions](/datalink/pull-delivery/reference/report-schemas) used by DataLink feeds and how to decode their structured data.
+Learn how to integrate DataLink into your applications using APIs, SDKs, and onchain verification methods.

src/content/datalink/pull-delivery/reference/report-schemas/index.mdx

@@ -67,7 +67,7 @@ Data Providers may use different report schema versions. The schema version dete
 1. Import the appropriate schema version in your code (e.g., `v4`).
 1. Use that version when decoding the report with `report.Decode[v4.Data]()`.
 
-Different schema versions have different fields and structures. For detailed information about each schema version and its fields, refer to the [Report Schemas](/datalink/pull-delivery/reference/report-schemas) documentation.
+Different schema versions have different fields and structures.
 
 In this example, we're using report schema `v4` for the EUR/USD feed, but your implementation should match the schema version specified by your Data Provider.
 
@@ -286,7 +286,7 @@ When working with different DataLink providers, you'll need to adapt your code t
      decodedReport, err := report.Decode[v3.Data](reportResponse.FullReport)
      ```
 
-1. Access fields according to the schema version structure. Refer to the [Report Schemas](/datalink/pull-delivery/reference/report-schemas) documentation for complete field references for each version.
+1. Access fields according to the schema version structure.
 
 ## Explanation
 

src/content/datalink/pull-delivery/reference/report-schemas/v2.mdx

@@ -69,7 +69,7 @@ Data Providers may use different report schema versions. The schema version dete
 1. Import the appropriate schema version in your code (e.g., `v4`).
 1. Use that version when decoding the report with `report.Decode[v4.Data]()`.
 
-Different schema versions have different fields and structures. For detailed information about each schema version and its fields, refer to the [Report Schemas](/datalink/pull-delivery/reference/report-schemas) documentation.
+Different schema versions have different fields and structures.
 
 In this example, we're using report schema `v4` for the EUR/USD feed, but your implementation should match the schema version specified by your Data Provider.
 
@@ -224,7 +224,7 @@ When working with different DataLink providers, you'll need to adapt your code t
      let report_data = ReportDataV3::decode(&report_blob)?;
      ```
 
-1. Access fields according to the schema version structure. Refer to the [Report Schemas](/datalink/pull-delivery/reference/report-schemas) documentation for complete field references for each version.
+1. Access fields according to the schema version structure.
 
 ## Explanation
 

src/content/datalink/pull-delivery/reference/report-schemas/v3.mdx

@@ -138,9 +138,7 @@ The `verifyReport` function is the core function that handles onchain report ver
 
 - **Report data extraction**:
   - The function decodes the `unverifiedReport` to extract the report data.
-  - It then extracts the report version by reading the first two bytes of the report data, which correspond to the schema version encoded in the feed ID:
-    - Schema version `0x0003` corresponds to the [report schema v3](/datalink/pull-delivery/reference/report-schemas/v3).
-    - Schema version `0x0004` corresponds to the [report schema v4](/datalink/pull-delivery/reference/report-schemas/v4).
+  - It then extracts the report version by reading the first two bytes of the report data, which correspond to the schema version encoded in the feed ID.
   - If the report version is unsupported, the function reverts with an InvalidReportVersion error.
 
 - **Fee calculation and handling**: