[chubes4]

Summary

• keep each native MariaDB startup candidate local until readiness is proven
• prevent failed-attempt process state from becoming shared cleanup state
• replace the fake client's timing-based readiness with explicit daemon-bind evidence

Closes #2435.

Root Cause

The fake MariaDB client returned socket readiness after an arbitrary 200 ms. On a hot host, it could report success before the fake daemon processed EADDRINUSE, so provisioning accepted an unbound first attempt and the retry assertion failed nondeterministically.

Verification

• focused native MariaDB test passed five sequential repetitions
• npm run check passed all 343 commands
• an unrelated fanout event-order assertion failed on the first full run, passed focused, and passed in the complete rerun

AI Assistance

GPT-5.6 Sol via OpenCode diagnosed the host-timing race, implemented the startup-state simplification and deterministic fixture readiness, and ran focused and full verification. I reviewed and orchestrated the work.