Read a publication, its progress and its exported client pack checks
Requires builds.read.
Authorizations
Your Summer account token. An agent gets it by signing in with OAuth: summer login --store in the Summer CLI, or the Summer connector in an AI app. Agent tokens can call only the operations on these pages. Publishing needs an approval from the game's owner first.
Path Parameters
^game_[A-Za-z0-9_-]{8,123}$Response
Current publication
hosted, standalone uploading, draft, orchestrating, pending, queued, materializing, building, packaging, publishing, verifying, preview_ready, published, succeeded, failed, cancelled checkpoint and phase; an exported game is inspecting between sealing and its outcome.
An exported game's client version.
The exact inspected pack attached from this exported game; absent before Build completion. Later client-only uploads do not change it. Read verifications for platform readiness.
The summer.build.json schema; empty for an exported game without a host.
The project's or pack's Summer version that selected the template set.
Why the publication failed. Exported-game intake uses bundle_invalid (the bytes are not an admissible bundle or stamped pack), declaration_mismatch, template_set_unavailable, client_version_conflict, artifact_exists, approval_denied and capacity_limit_reached.

