Module progress 

Structured startup-progress events for the Atlas TUI.

Call sites next to the existing human-readable log lines emit ADDITIONAL debug!-level events under the dedicated TARGET. They are invisible on the plain-log path at the default info filter — the grepped output the benchmark rigs depend on does not change by a byte — while the TUI’s capture layer enables this target unconditionally and decodes the typed fields.

Discriminated by the ev field: phase — phase (0..=11), name preflight — disk_gb, free_gb shard_start — shard (1-based), total, name shard_done — shard, total, used_gb, free_gb layer — layer (0-based highest loaded), total ready — port

Constants

TARGET

Tracing target the TUI capture layer filters on. Keep in sync with spark-server/src/tui/capture_layer.rs.

Functions

layer

Layer-build progress (sampled by the weight loaders).

phase

A named startup phase has begun. phase is the serve() phase index.

preflight

Weight-load preflight: total on-disk GB (the overall-bar denominator).

ready

The server is listening; startup is complete.

shard_done

A shard finished; GPU memory snapshot alongside.

shard_start

A safetensors shard load has started.