MetricTapConfig

the rendezvous pattern the host opens and a client joins. A single stable name is fine — extraction is point-to-point (one host, one or more pullers).

how often the host re-reads the device's metric buffer and offers its current converged state for replication. New state also flows on demand via MetricTapHost.sync.

the upper bound on a single MetricTapClient.pull — how long it waits for the host to connect and its metrics to replicate in before giving up. A pull that exceeds it throws rather than returning a partial result.

after the first state arrives, how long MetricTapClient.pull waits for the replicated state to stop advancing before treating the snapshot as complete.

replication tuning passed through to the underlying replicator. Tests set expectVirtualTime = true to silence the test-dispatcher diagnostic.

Field-for-field identical to LogTapConfig except the default pattern (kuilt-metric-tap vs kuilt-log-tap). The two are deliberately not unified into one type: a typealias cannot carry a per-alias default argument, so collapsing them would erase the distinct default rendezvous names — a silent wire-name change. They stay separate so each keeps its own default pattern.