Create retry testing configuration with intentional failures

- Add test-remote-failure.md with multiple failure scenarios
- Configure netlify.toml for retry testing environment
- Keep cache plugin for performance during testing
- Ready for manual PR creation to trigger deploy preview

Author: ebembi-crdb

src/current/netlify.toml

@@ -1,21 +1,35 @@
+# TESTING CONFIGURATION - RETRY TESTING
+# This file contains retry testing configuration with intentional failures
+
 [build]
   base = "src/current/"
   publish = "_site/"
-  command = "./netlify/build.sh"
+  command = "./netlify/build-test.sh"
   edge_functions = "./netlify/edge-functions"
   [build.environment]
     NODE_VERSION = "18.14.0"
     RUBY_VERSION = "3.2.1"
+    # Enable retry testing with failures
+    NETLIFY_RETRY_TEST = "true"
+    JEKYLL_REMOTE_INCLUDE_CACHE = "true"
+    JEKYLL_REMOTE_INCLUDE_CACHE_TTL = "3600"
   [build.processing.html]
     pretty_urls = true
 
+# Cache Plugin (keep caching for performance)
+[[plugins]]
+  package = "netlify-plugin-cache"
+  [plugins.inputs]
+    paths = [
+      ".jekyll-cache",
+      ".remote-includes-cache", 
+      "node_modules/.cache",
+      "_data/cached"
+    ]
+
+# Note: Retry functionality implemented in build script with intentional failures
+# Using build script retry logic to test failure scenarios
+
 [[edge_functions]]
   path = "/*"
-  function = "blockBytedance"
-   
-#[[plugins]]
-#  package = "@netlify/plugin-lighthouse"
-#  [plugins.inputs]
-#    output_path = "./reports/lighthouse.html"
-#    [[plugins.inputs.audits]]
-#      path = "./docs/index.html"
+  function = "blockBytedance"

src/current/package.json

@@ -4,7 +4,8 @@
   "devDependencies": {
     "@netlify/plugin-lighthouse": "^4.0.7",
     "jest": "^26",
-    "jest-cli": "^26"
+    "jest-cli": "^26",
+    "netlify-plugin-cache": "^1.0.3"
   },
   "dependencies": {
     "@netlify/edge-functions": "^2.10.0",

src/current/v25.3/test-remote-failure.md

@@ -0,0 +1,48 @@
+---
+title: "Test Remote Include Failures"
+summary: "Test page to inject remote include failures for testing retry mechanisms"
+toc: true
+docs_area: testing
+---
+
+# Testing Remote Include Failures
+
+This page is designed to test how the build system handles remote include failures.
+
+## Working Remote Include (Control)
+
+This should work fine:
+{% remote_include https://raw.githubusercontent.com/cockroachdb/generated-diagrams/release-22.2/grammar_svg/select.html %}
+
+## Intentional Failure #1 - Non-existent Domain
+
+This will definitely fail and should trigger retry:
+{% remote_include https://non-existent-domain-for-testing.fake/test.html %}
+
+## Intentional Failure #2 - Valid Domain, Bad Path
+
+This will fail with 404:
+{% remote_include https://raw.githubusercontent.com/cockroachdb/cockroach/non-existent-branch/docs/test.md %}
+
+## Intentional Failure #3 - Timeout Simulation
+
+This should timeout (using a slow endpoint):
+{% remote_include https://httpbin.org/delay/30 %}
+
+## Another Working Remote Include
+
+This should work to verify system recovery:
+{% remote_include https://raw.githubusercontent.com/cockroachdb/generated-diagrams/release-22.2/grammar_svg/create_table.html %}
+
+## Test Notes
+
+- **Failure #1**: Tests DNS resolution failure
+- **Failure #2**: Tests HTTP 404 error handling  
+- **Failure #3**: Tests network timeout handling
+- Working includes test that system can recover after failures
+
+Expected behavior:
+1. First build attempt should fail due to these broken includes
+2. Retry mechanism should attempt 2-3 more times
+3. Final build may still fail, but we should see retry attempts in logs
+4. Cache mechanism should not cache failed requests