Crate mz_clusterd_test_driver 

Headless frontend to clusterd for scripted compute tests.

See doc/developer/design/20260612_headless_clusterd_test_driver.md.

Modules

ctp

Compute CTP connection and the Hello step of the controller handshake. Generic: it sends any ComputeCommand and receives any ComputeResponse.

data

Synthetic data generation and direct persist writes. This supports the direct-write use case; the mechanism does not depend on it.

dataflow

Assembly of compute DataflowDescriptions for the headless test driver.

driver

The headless Driver: the mechanism’s top-level API. Use cases call it.

persist_host

Hosts the persist PubSub server and a PersistClientCache wired to it. This is the mechanism’s persist access layer; it embeds no workload.

responses

Owns the receive side of the CTP connection: a background task that pumps ComputeResponses into per-id frontier watches, per-uuid peek channels, and a raw broadcast. The mechanism does not curate which responses or which frontier fields a use case may observe: frontier watches keep the full merged FrontiersResponse, and the raw broadcast carries every response.

script

Executes a text command script against clusterd.

target

Resolves the clusterd compute controller address. The driver connects to an externally-managed clusterd (mzcompose or a manually-launched process); it never spawns one.

text

The text script format: a hand-writable, datadriven-style command file.