ci: set a dummy QSEAL_SECRET for the test jobs (fail-closed allow-paths need a signing secret)

Since the 0.4.x hardening, an allow-path that cannot sign its witness
refuses (POLICY_BLOCK) rather than run unsigned — by design. The
suite's documented invocation sets QSEAL_SECRET; CI never did, so
test_langchain_tool_allows_safe_read went red on the first CI exposure
of the fail-closed era. Bisected: same wheels pass with the secret set,
fail without it, on both PyPI-installed and repo code. Value is a
CI-only dummy, not a credential.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: Sdvegas21

.github/workflows/clawzero-ci.yml

@@ -18,6 +18,11 @@ jobs:
       fail-fast: false
       matrix:
         python-version: ["3.10", "3.11", "3.12"]
+    env:
+      # Since the 0.4.x fail-closed hardening, allow-paths refuse rather than
+      # run unsigned when no QSEAL secret is present (by design). The suite's
+      # documented invocation sets one; this is a CI-only dummy, not a secret.
+      QSEAL_SECRET: ci-only-dummy-qseal-secret
 
     steps:
       - uses: actions/checkout@v5
@@ -48,6 +53,8 @@ jobs:
     name: Attack Pack Validation
     runs-on: ubuntu-latest
     needs: test
+    env:
+      QSEAL_SECRET: ci-only-dummy-qseal-secret
 
     steps:
       - uses: actions/checkout@v5

.github/workflows/test.yml

@@ -13,6 +13,9 @@ jobs:
       matrix:
         os: [ubuntu-latest, macos-latest]
         python-version: ["3.10", "3.11", "3.12", "3.13"]
+    env:
+      # Fail-closed allow-paths need a signing secret; CI-only dummy value.
+      QSEAL_SECRET: ci-only-dummy-qseal-secret
 
     steps:
       - name: Checkout