importers

See and drive the importer system — the pipeline that turns a raw source file written into the world (.fbx, .glb, .png, …) into its engine asset (.bundle, .texture, …).

Imports run asynchronously off the write signal, so this toolbox is the observability and control surface: status lists recent import jobs with their state (running / imported / failed / skipped / unclaimed) and errors, explain dry-runs the dispatch gates for a path and names exactly what would block an import right now, run imports a path synchronously and returns the produced asset, await blocks until an in-flight import for a path settles, and list enumerates the registered importers.

Start with status when "I wrote a file and nothing happened" — the job record carries the state, the winning importer, the produced output, or the error. If the path has no job at all, explain tells you which gate stopped it before a claimant ran.