Pipeline surface for diagnosis, validation, and controlled automation in the jobs teams already run.
Same commands and output shape operators use locally. Structured output that fits pipeline steps and logs. Dry-run, preflight, and gated execution stay visible. Useful when build and validation need repo-aware context
Runtime entries
24
Runtime entries
Canonical product actions spanning diagnosis, project reads, workflows, auth, and governance.
MCP tool routes
20
MCP tool routes
Machine-facing routes for Unreal-aware reads, diagnosis, and governed workflow access.
VSCode actions
29
VSCode actions
Editor-native command coverage with the same runtime and trust model underneath.
Surface types
5
Surface types
CLI, MCP, VSCode, CI, and the optional UE bridge.
Pipelines can run steps. Unreal teams still need diagnosis, parity, and clear execution posture.
Local versus pipeline drift
Build and validation flows lose trust when CI behaves like a separate product from local work.
Unreadable failure logs
Raw pipeline output is still noisy Unreal build output unless the product adds structure around it.
Blind automation
Pipelines need the same explicit modes and safety posture as human operators.
Fragmented validation
Diagnosis, preflight, and workflow routing are harder to trust when they are scattered across separate scripts.
CI that keeps the same operating contract teams see locally
Pipeline-ready behavior
The runtime behaves consistently in automation without inventing a separate CI-only path.
Structured diagnosis
Make pipeline failures easier to understand than raw Unreal logs alone.
Visible execution posture
Dry-run, preflight, and gated depth still matter when the operator is a workflow job.
Parity with local work
Teams move between shell and pipeline without losing the shared product model.