pipeline
Automation-bridge and build tooling about the plugin itself.
What it is
The pipeline namespace is a thin surface over the plugin's own automation bridge and build tooling. It covers a handful of introspection and build-plumbing calls — reading bridge status, listing the available automation tool categories, and launching Unreal Build Tool — rather than anything you author inside your game. It exists to support the machinery that runs PinWright, not to shape your project's content.
If you are actually driving the editor — running tests, executing console commands, or invoking subsystem functions — reach for system instead; that is the top-level control surface most work goes through. Almost nothing here is something you call directly during day-to-day editor automation, and there is no game-authoring workflow that depends on it.
system, actor, blueprint, and the asset namespaces long before you ever need anything under pipeline.