---- the run policy ----
One process takes `coppeliusRunSteps` AdamW steps, step s on context
c0 + s of the token stream the request names (c0 the contexts its
checkpoint has consumed: 0 fresh), and publishes its checkpoint after
every `coppeliusRunCheckpointInterval` steps -- the last publication at
its end. A checkpoint goes to the request's checkpoint path through its
temporary: written whole, digested, synced, then renamed over the path,
so the path always holds a complete checkpoint (Platform.Linux.Nvidia.
PlanHostRequest). The loop is compiled: the host issues one update
submission of the plan per step (Coppelius.Build.NativeHost).
The compiler supplied declaration spans and resolved links from this source snapshot. This page does not assert that this file belongs to a checked closure.