What problem does it solve? Shipping a Godot game to Windows, Linux, macOS, Android, iOS, or Web involves repetitive export presets, signing credentials, notarization, and CI configuration that are error-prone when done manually through the editor UI. ## Core Features & Use Cases - Headless Export Pipelines: PowerShell and Bash scripts run --headless --export-release builds across multiple presets without opening the editor. - Platform Release Plumbing: Scripts cover Android keystore signing via environment variables, macOS codesign/notarization steps, SteamPipe uploads via steamcmd, and PCK patch loading for delta updates. - CI/CD & Optimization: A GitHub Actions workflow pinned to Godot 4.7 templates, plus build size reports, feature-flag stripping with OS.has_feature, and SCons module stripping for custom templates. - Use Case: A team preparing a Steam release can run the headless pipeline to produce Windows/Linux builds, sync the version string from git tags, and upload depots with the SteamPipe script using credentials from environment variables. ## Quick Start Ask the agent to set up a headless CI export pipeline for your Godot 4.7 project targeting Windows and Web with release templates.