status(5): record matrix-synapse V6 dead-end

machine-docs/STATUS-5.md

@@ -74,8 +74,8 @@ preferred, `/root/cc-ci` fallback) instead of hard-coding `/root/cc-ci`.
 | V2 — testme-on-pr.sh reads verdict | DONE | GREEN ✓ (build #29/#35); RED ✓ (build #34); rerun fix ✓ (build #43) |
 | V3 — /recipe-upgrade sandbox GREEN | DONE | custom-html-tiny PR#2; build #29 SUCCESS |
 | V4 — 3-iter regression loop | DONE | custom-html-tiny PR#5; build #34 RED, build #37 GREEN |
-| V5 — stale-test DEFAULT = comment | IN PROGRESS | matrix-synapse PR#1 comment posted; no test edits; awaiting full evidence bundle |
-| V6 — --with-tests opens+verifies cc-ci test PR | TODO | |
+| V5 — stale-test DEFAULT = comment | IN PROGRESS | matrix-synapse default-mode comment posted, but later invalidated as a likely real regression; next candidate pending |
+| V6 — --with-tests opens+verifies cc-ci test PR | TODO | matrix-synapse branch invalidated by real regression; next candidate pending |
 | V7 — mirror reconciliation | DONE | PR#1 superseded, PR#4 merged-upstream, main=upstream ✓ |
 | V8 — /upgrade-all DEFAULT run | TODO | |
 | V8a — cc-ci-upgrader agent | TODO | |
@@ -123,12 +123,22 @@ preferred, `/root/cc-ci` fallback) instead of hard-coding `/root/cc-ci`.
   Default-mode explanatory PR comment posted with no test edit:
   `https://git.autonomic.zone/recipe-maintainers/matrix-synapse/pulls/1#issuecomment-13877`
   telling the operator to re-run `/recipe-upgrade matrix-synapse --with-tests` for a test-update PR.
+- Adversary finding A5-4 is now cleared on current live behavior: re-`!testme` on the same PR head
+  produced build `#63`; `POST=0 ... testme-on-pr.sh matrix-synapse 1` returned
+  `VERDICT=RED BUILD=https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/63`; and
+  `GET /repos/recipe-maintainers/matrix-synapse/commits/21e5d844.../status` now shows
+  `cc-ci/testme state=failure target_url=.../63`.
+- V6 branch verification on `matrix-synapse` no longer supports the stale-test hypothesis. In a
+  dedicated cc-ci branch checkout with a real Matrix data-survival upgrade assertion, the helper path
+  now resolves the recipe branch to its head SHA correctly, generic upgrade PASSes, but the upgraded
+  app still fails the real post-upgrade assertion: the pre-upgrade Matrix user cannot log in after the
+  upgrade (`HTTP 403 Invalid username or password`). That points to a true recipe upgrade regression,
+  not a stale test.
 
 ## Verification next step
 
-- Advance this `matrix-synapse` stale-test candidate into V6 by preparing a dedicated cc-ci test branch,
-  updating the synthetic upgrade assertion to a real app-data-preservation check, and verifying the
-  recipe upgrade with that test change applied.
+- Move to the next enrolled candidate for V5/V6. Current shortlist: `n8n` first, then `lasuite-docs`,
+  then `keycloak`.
 
 ## Phase 5 gates