docs: R-STATE-01 green + chainsaw =~ harness fix (F-TEST1)

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>

DECISIONS-LOG.md

@@ -363,6 +363,17 @@ all Ready, 5/5 HelmReleases Ready, no unhealthy pods). **NOTE:** `bitnamilegacy`
 mirror — a durable follow-up is to pin a maintained kubectl image (shell-capable, e.g. rancher or
 alpine/k8s) once tested, or a newer kyverno chart that drops the bitnami dependency.
 
+### R-STATE-01 GREEN + harness fix F-TEST1 (2026-08-17, main @ 76478f2)
+- **R-STATE-01 (data durability) PROVEN:** the L3 `data-survival` test runs against live Longhorn — writes
+  a canary to a `longhorn` PVC, DESTROYS the pod entirely, re-binds a fresh pod to the same PVC, and the
+  data survives (`DATA_SURVIVED_OK`). This is the platform's headline stateful-durability requirement.
+- **F-TEST1 — every chainsaw `check` used an unsupported `=~` operator (FIXED):** all 10 tests wrote
+  `(($stdout =~ 'X')): true`; chainsaw's expression engine rejects `=~` ('SyntaxError: Unknown char: ~'),
+  so each test FAILED on the assertion even when the behavior passed (caught because data-survival printed
+  DATA_SURVIVED_OK yet FAILED). Converted all to JMESPath `contains($stdout, 'X')` in BLOCK style (flow
+  `{ }` breaks on the comma inside `contains()`). data-survival passes; the 9 later-phase tests
+  (egress/vpn/alerting/dr/updates/drift/sso) are now syntactically correct for when their phases deploy.
+
 ## KNOWN ISSUES to fix before Phase-2 un-suspend (logged, not yet fixed)
 | # | Issue | Impact | Fix |
 |---|---|---|---|