| Create Summer game records | Live | Authenticated creators can create a game record through the Summercraft API. |
Upload and verify a game-only .pck | Live | Direct-to-storage upload, server-side SHA-256 verification, and immutable release records are deployed. |
| Browser submission and static scanner | Live | The signed-in submit page accepts a .pck plus manifest.json and runs pattern-based static analysis before creating a review submission. |
| Manual review queue | Live | A submission can enter human review; there is no automatic approval. |
| Authenticated release download | Live | Owners and admins can retrieve pending releases; published catalog releases follow the documented access rules. |
| Summer SDK gameplay and subsystem interfaces | Scaffold | The GDScript contract and examples exist, but documented interfaces do not prove the hosted runtime path is deployed. |
SummerMultiplayerPeer transport | Scaffold | The compatibility contract is published and implementation is in progress. |
| Browser or desktop-shell play for uploaded games | Planned | A published catalog status does not make an uploaded game playable. |
| Hosted dedicated game servers | Planned | Creators must not promise managed hosting to players. |
| Automatic matchmaking and relay | Planned | No production matchmaking or relay service is available for uploaded Summer games. |
| Automated production runtime sandbox | Planned | Submission review is manual; the production sandbox path is still being built. |
| Production gameplay runtime | Planned | Uploaded and approved packs do not execute in a Summercraft gameplay runtime today. |
| Hosted persistence and economy | Scaffold | Summer.data and Summer.economy are contract surfaces; no hosted backend durably stores player data or runs the economy rail today. |
