From 2955f9289adc916afcc9784ebaa35a8e9768d6f8 Mon Sep 17 00:00:00 2001
From: Robert DeLanghe <oink_monocle_7d@icloud.com>
Date: Sun, 28 Jun 2026 23:51:51 -0400
Subject: [PATCH] site-deploy: make the RFC 9110 probe opt-in (skip if no
 config)

A reusable workflow shouldn't force every site to ship contract/http-probe.json. Skip
the probe (with a notice) when the config file is absent; sites enable it by adding the
config. Lets bounded.tools derive the pipeline without a probe contract it doesn't have.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 .github/workflows/site-deploy.yml | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/.github/workflows/site-deploy.yml b/.github/workflows/site-deploy.yml
index b2196f0..7a1948e 100644
--- a/.github/workflows/site-deploy.yml
+++ b/.github/workflows/site-deploy.yml
@@ -183,8 +183,16 @@ jobs:
           exit 1
 
       # RFC 9110 HTTP-correctness probe of the live edge.
+      # Opt-in: a site that ships a probe config gets the RFC 9110 check; one that doesn't is not
+      # forced to (a reusable workflow shouldn't mandate a per-site contract file). Add the config
+      # at `probe_config` to enable it.
       - name: HTTP correctness probe (RFC 9110)
         env:
           DOMAIN: ${{ inputs.domain }}
           PROBE_CONFIG: ${{ inputs.probe_config }}
-        run: PROBE_CONFIG="$PROBE_CONFIG" node vendor/conformance-kit/integrity/http-probe.mjs "$DOMAIN"
+        run: |
+          if [ ! -f "$PROBE_CONFIG" ]; then
+            echo "::notice::no probe config at $PROBE_CONFIG — skipping the RFC 9110 probe for this site"
+            exit 0
+          fi
+          PROBE_CONFIG="$PROBE_CONFIG" node vendor/conformance-kit/integrity/http-probe.mjs "$DOMAIN"