fix(conformance): block-style chainsaw checks (flow-map broke on contains comma)

My previous commit converted =~ to contains() but kept flow style
'check: { (contains($stdout, 'X')): true }' — the comma inside contains() is a
YAML flow-map separator, so 9 tests failed yamllint ('expected , or }'). Convert
those checks to block style (matching data-survival), where a comma in the key
scalar is fine. Gate PASS; data-survival still green.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
This commit is contained in:
jakman85andClaude Opus 4.8 committed 2026-08-17 17:02:05 -05:00
1 parent 3440bbad92
commit 70c0701d6f
9 files changed
+32 -16

No files matched your search

@@ -51,14 +51,16 @@ spec:
echo "LEAK: vpn workload reached internet with tunnel down" >&2; exit 1
fi
echo NO_LEAK_OK
check: { (contains($stdout, 'NO_LEAK_OK')): true }
check:
(contains($stdout, 'NO_LEAK_OK')): true
- script:
# AND: internet-class workload is unaffected.
content: |
set -euo pipefail
kubectl -n "$NAMESPACE" exec egress-internet -- \
curl -fsS --max-time 5 https://api.ipify.org && echo INTERNET_UNAFFECTED_OK
check: { (contains($stdout, 'INTERNET_UNAFFECTED_OK')): true }
check:
(contains($stdout, 'INTERNET_UNAFFECTED_OK')): true
- name: when-tunnel-recovers-connectivity-returns
try:
- script: