status(2): Q4.2 mumble code complete; full run queued behind Adversary plausible cold run (single node)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-05-29 19:34:22 +01:00
parent 999dd0d564
commit 3360f1b266

View File

@ -64,6 +64,15 @@ set; was unenrolled). mumble has a recipe-maintainer corpus (P2 NON-vacuous): `h
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.
**CODE COMPLETE (commits 6841048+6bf0425+999dd0d):** recipe_meta + 3 parity ports
(test_tcp_health/test_protocol_handshake/test_web_client) + 2 specific (welcome-text + max-users
config round-trips over the protocol) + P4 (ops/test_backup/test_restore via sqlite ci_marker) +
test_install overlay + PARITY.md + install_steps.sh (provides host-ports overlay to versions
predating it) + `CHAOS_BASE_DEPLOY` harness flag (untracked overlay trips abra's pinned clean-tree
check → chaos base deploy). Smoke proved web 200 + `Mumble`/`config.js`, TCP 64738 host-published,
sqlite3 in container. **Full harness run QUEUED behind the Adversary's in-flight plausible cold run
(`/root/adv-q47-plausible-cold.log`, stack `plau-0c70fd`) — single node; not deploying concurrently
to protect their clean cold-verify signal.**
**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