Asset status

The organized tree is populated in two stages:

Existing Hub objects are copied server-side into their setting directories.
Missing common-start or Uniform/Residual artifacts are uploaded directly from the server that owns the authoritative checkpoint.

Expected final entries for every setting are common_start, uniform, residual, keyframe, frameskip, loss_is, configs, and dependencies.

common_start means a resumable training state. The five method directories contain evaluation-ready endpoint weights. Training configs, proposal/cache metadata and environment notes live beside the corresponding setting and point to shared code rather than duplicating the whole source tree four times.