status(2): Q1 Adversary PASS; Q2 keycloak in flight (timeouts bumped to 900s)

Per REVIEW-2 ## Q1 — PASS @2026-05-28: F2-3 + F2-4 closed; cold e2e on Adversary clone all 5
stages PASS; deploy-count=1; HC1 non-vacuous; teardown sacred; NO VETO. Builder may advance to Q2.

Q2.1 keycloak in flight: first attempt hit 502 from /realms/master at 600s; bumped DEPLOY_TIMEOUT
+ HTTP_TIMEOUT to 900s in tests/keycloak/recipe_meta.py.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-05-28 07:12:47 +01:00
parent adb3bf9669
commit 9c79215fb9

View File

@ -49,19 +49,15 @@ tree must carry:
- **Q5** — Completeness + docs; flip `## DONE`.
## In flight
**Q2 — SSO providers (keycloak + authentik).** Q1 CLAIMED — n8n + custom-html both full-green via
the existing run path; PARITY.md + functional/ + playwright/ in place; data-integrity proven via
the lifecycle overlay pattern. Next: keycloak parity port + OIDC-flow harness primitive.
**Q2 — SSO providers (keycloak + authentik).** Q1 Adversary PASS landed. Keycloak Phase-2 content
drafted (PARITY.md + 3 functional tests: parity health_check + password_grant_token + create_client_and_use); e2e in flight (background task `bxnhxrolk`, log `/root/ccci-q2-keycloak-r2.log`).
First e2e attempt (`bmdkj7egr`) failed with `not healthy over HTTPS /realms/master (last status
502)` at 600s; bumped DEPLOY_TIMEOUT + HTTP_TIMEOUT to 900s in `tests/keycloak/recipe_meta.py`.
## Gate
**Gate: Q1 — RE-CLAIMED, awaiting Adversary @2026-05-28** (commit `fc89552` F2-3 + F2-4 fixes on
top of original Q1 claim `2f3d5aa`). Acceptance per plan §6 Q1 + Adversary Q1 FAIL findings:
- **F2-4 closed:** `tests/n8n/functional/test_workflow_roundtrip.py` lands the plan §4.3
prescribed test (owner setup → workflow create → workflow read-back), removing the prohibited
"needs owner setup" excuse. Cold e2e PASS.
- **F2-3 closed:** `tests/n8n/test_install.py` now wraps `page.goto(...)` in `try/except
PlaywrightError` inside the retry loop so transient `net::ERR_*` errors trigger a retry instead
of test failure. Cold e2e PASS first try.
**Gate: Q1 — Adversary PASS @2026-05-28** (REVIEW-2 `## Q1 — PASS @2026-05-28 (re-verify after
F2-3 + F2-4 fixes)`; cold e2e on `/root/adv-verify` HEAD `fc89552` → all 5 stages PASS,
deploy-count=1, HC1 non-vacuous; F2-3 + F2-4 CLOSED; NO VETO). Builder may advance to Q2.
**Objective evidence pointers (Q1):**
- **custom-html (Q1.1)** — already cold-verified in Q0 PASS. Same evidence stands: full e2e green,