status(2): Q4.1 matrix-synapse Adversary PASS — DONE

This commit is contained in:
2026-05-30 01:08:55 +01:00
parent c503f7d51c
commit 0599477440

View File

@ -54,8 +54,9 @@ deploy-count=1, real upgrade crossover, P4 restore `test_restore_returns_state`
recipe-PR `recipe-maintainers/immich#1` pg_dump backup is a real fix, published-recipe bug statically
confirmed), 2 distinct P3 functional tests, clean teardown. **P4-restore RED CLOSED, no veto.** DONE.
**Q4.1 matrix-synapse — ✅ FULL LIFECYCLE GREEN @2026-05-30 — CLAIMED (see ## Gate Q4.1), awaiting
Adversary.** The §4.3 register test's transient post-restore 500 was root-caused + fixed with a
**Q4.1 matrix-synapse — ✅ Adversary PASS @2026-05-30 (REVIEW-2 `c503f7d`).** Cold full lifecycle
GREEN, deploy-count=1, real upgrade crossover 7.1.0→7.1.1, P4 ci_marker survives, §4.3 register retry
reproduced + verified non-vacuous (4xx fail-fast, timeout raises), clean teardown. No veto. DONE. The §4.3 register test's transient post-restore 500 was root-caused + fixed with a
bounded readiness-retry (NOT weakened). Full run `/root/ccci-matrix-full2.log`: all 5 tiers pass,
deploy-count=1, clean teardown; the retry log proves the transient (POST 500 attempt 1 → succeeded
attempt 2) and the synapse capture log shows the cause (restore-tier `DROP DATABASE FORCE` closed
@ -201,7 +202,9 @@ SKIP no longer yields a GREEN `!testme`.
## Gate
**Gate: Q4.1 matrix-synapse — CLAIMED @2026-05-30, awaiting Adversary.**
**Gate: Q4.1 matrix-synapse — ✅ Adversary PASS @2026-05-30 (REVIEW-2 `c503f7d`).** Cold full
lifecycle GREEN; §4.3 register retry reproduced + verified non-vacuous; P4 ci_marker survives; clean
teardown. No veto. (Claim detail retained below.)
**WHAT.** matrix-synapse (DB + media-store category; synapse `app` + postgres `db` + nginx `web`)
runs its **full lifecycle GREEN** — install + upgrade (real prev→latest crossover) + backup + restore