From 265eae5365556a6c2c9f7d769e0f7e3e4ff28c21 Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Fri, 29 May 2026 19:13:39 +0100 Subject: [PATCH] =?UTF-8?q?status(2):=20Q4.2=20mumble=20enrolling=20?= =?UTF-8?q?=E2=80=94=20TCP-protocol=20recipe,=20mumbleweb+host-ports=20pla?= =?UTF-8?q?n,=20P2=20corpus=20port?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 4.8 (1M context) --- machine-docs/STATUS-2.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/machine-docs/STATUS-2.md b/machine-docs/STATUS-2.md index 6f52438..70ca157 100644 --- a/machine-docs/STATUS-2.md +++ b/machine-docs/STATUS-2.md @@ -49,6 +49,15 @@ tree must carry: - **Q5** — Completeness + docs; flip `## DONE`. ## In flight +**Q4.2 mumble — ENROLLING (not claimed) @2026-05-29.** Next P1-coverage gap (mumble is in §5 target +set; was unenrolled). mumble has a recipe-maintainer corpus (P2 NON-vacuous): `health_check.py` (TCP +64738), `mumble_connect.py` (full TLS protocol handshake → ServerSync + channel presence), `web_client.py` +(mumble-web HTTP UI). Plan: enroll with `COMPOSE_FILE=compose.yml:compose.mumbleweb.yml:compose.host-ports.yml` +— mumbleweb gives an HTTP readiness endpoint (generic `wait_healthy`) + the web_client parity test; +host-ports publishes 64738 on the cc-ci host so the TLS-protocol tests (run on-host by cc-ci-run) connect +to 127.0.0.1:64738. P4 via sqlite (recipe backupbot dumps `/data/mumble-server.sqlite`). 3 version tags +(0.1.0/0.2.0/1.0.0) → real upgrade tier. De-risking reachability with a smoke deploy first. + **Q3.3 lasuite-meet — ✅ Adversary PASS @2026-05-29 (REVIEW-2 `a46f7d4`).** Cold-verify all 5 tiers GREEN, real upgrade crossover, meeting_flow + OIDC PASSED, ci_marker survives, clean teardown; WebRTC media-relay non-port got explicit Adversary sign-off. Q3.2+Q3.3 PASS; Q3.4 cryptpad green (F2-9