From 71af595915417d068f1111e732d5503461f506a2 Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Sat, 30 May 2026 04:08:04 +0100 Subject: [PATCH] =?UTF-8?q?review(2):=20Q4.7=20plausible=20=C2=A74.3=20flo?= =?UTF-8?q?or=20NOW=20FIRST-HAND=20GREEN=20=E2=80=94=20my=20cold=20run=20(?= =?UTF-8?q?adv-plausible-cold2)=20install+custom=20pass,=20deploy-count=3D?= =?UTF-8?q?1,=20BOTH=20*=5Fevent=5Froundtrip=20PASSED=20(ClickHouse=20even?= =?UTF-8?q?ts=5Fv2=20read-back),=20clean=20teardown;=20prior=20readiness-4?= =?UTF-8?q?04=20was=20a=20transient=20ClickHouse-boot=20flake;=20Q4.7=20fi?= =?UTF-8?q?rst-hand-evidence=20obligation=20CLEARED;=20note:=20ClickHouse?= =?UTF-8?q?=20boot=20intermittently=20flaky=201/2=20on=20single=20node?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- machine-docs/REVIEW-2.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/machine-docs/REVIEW-2.md b/machine-docs/REVIEW-2.md index 8d2768a..86fdb8c 100644 --- a/machine-docs/REVIEW-2.md +++ b/machine-docs/REVIEW-2.md @@ -1714,3 +1714,26 @@ round-trips cleanly (a genuine recipe difference from the postgres recipes, born **Isolation note:** verdict from the plan (P1–P8) + the test code (_p4.py / ops.py / test_{restore, backup,upgrade}.py / functional/{test_account_and_post,test_session_auth}.py) + the STATUS Gate-Q4.3 verification info + my own cold full-lifecycle run. JOURNAL-2 not consulted before this verdict. + +## Q4.7 plausible — §4.3 floor NOW FIRST-HAND GREEN (break-it probe, my cold run) @2026-05-30T02:05Z + +Settled my OWN long-pending first-hand confirmation (the prior `/root/adv-q47-plausible-cold.log` had +FAILED at install readiness — `/api/health` 404, a transient ClickHouse-boot miss). Re-ran cold from +`/root/adv-verify`: `RECIPE=plausible PR=0 STAGES=install,custom cc-ci-run runner/run_recipe_ci.py` +→ `/root/adv-plausible-cold2.log`. This time ClickHouse (events_db) booted and the run is GREEN: +- RUN SUMMARY: `deploy-count = 1`; `install : pass`, `custom : pass`. +- `tests/plausible/functional/test_event_tracking.py::test_pageview_event_roundtrip PASSED` (53s) + + `::test_custom_event_roundtrip PASSED` — the genuine create-event→ClickHouse-`events_v2`-read-back + on a unique pathname (non-vacuous; a broken ingestion path raises→FAILS). `test_plausible_root_serves + PASSED`. Clean teardown: post-run no plau stack; 0 plau secrets/volumes/networks. +- (The prepull `service "app" depends on undefined service "events_db"` warning is benign — it's the + prepull config-probe, which doesn't include the events compose file; the real deploy includes it and + ClickHouse booted, as the 53s read-back tests prove.) + +**Upgrade to my Q4.7 verdict:** the §4.3 event-roundtrip FLOOR is now confirmed GREEN by my own cold +run, not just Builder logs — the earlier readiness 404 was a transient ClickHouse-boot flake, not a +structural failure. Q4.7's only open item (first-hand green evidence) is CLEARED. Plausible's full +upgrade/backup/restore tiers were not in this scoped run (install,custom only) — P4/upgrade for +plausible still ride the normal gate path if/when claimed; this probe targeted the §4.3 floor that was +my standing obligation. No VETO. NOTE: ClickHouse boot is intermittently flaky on the single node +(1-in-2 here) — a real env-fragility worth a retry/readiness margin if plausible runs go in CI rotation.