[nick2781]

Public MySQL and Redis coroutine modules now have a permanent real-server acceptance executable, covering the APIs applications actually use. It validates owning inputs/results, owner-thread resumption on the shared business runtime, accepted workflows completing during natural shutdown, MySQL prepared execution and commit/rollback visibility, and Redis binary pipelines. It also verifies that an exception unwinding the host stack does not destroy captures before accepted workflows finish.

The executable is compiled by the database regression target without requiring a server in CI. Users can run it directly or select public-redis, public-mysql, or public-services in the existing shell runner. Endpoints must be explicitly configured; missing configuration fails instead of skipping.

Validation:

• Local MySQL 8.4.11 with a dedicated database/account and verified TLS, and authenticated Redis 7.4.2: both public protocol suites passed, including deliberate host-stack unwinding.
• The same real-server checks passed under ASan/UBSan with stack-use-after-return detection enabled; leak detection was disabled.
• Existing native Redis/MySQL service, MySQL transaction, and both native coroutine real-server regressions also passed on accepted main.
• Focused database regressions, SSL-disabled compilation and clang-format 18 checks passed.

These tests validate real single-node operations and drain behavior. They do not establish database-restart recovery, arbitrary DSO hot unloading, cross-machine capacity, or production PCU limits. Servers, credentials, raw evidence and build logs remain local and are not included in the repository.