summer-engine 3.5.0 → 3.5.2

package/library/skills/release-readiness/SKILL.md

@@ -0,0 +1,298 @@
+---
+name: release-readiness
+description: "Before releasing a Summer game version, prove players can play it: server scene, online join, saved progress, no fixed Game ID, a released Summer compiles it."
+license: MIT
+compatibility: [Cursor, Claude Code, Windsurf, Codex]
+category: deployment
+user-invocable: true
+allowed-tools: Read Grep Glob Bash summer_read_file summer_get_diagnostics
+paths: ["export_presets.cfg", "project.godot", "summer.build.json", "world.json", "**/*.gd"]
+---
+
+# /release-readiness: prove players can play it
+
+Summer checks every upload: platforms, packs, and the files they name. Those
+checks prove the export is well formed. They can't prove that a player who
+presses **Play online** gets into a game. Each check below exists because a
+real release passed every upload check and still failed for its players.
+
+The creator docs have the same checklist, with the same numbers:
+https://docs.summerengine.com/publishing/release-readiness (fetch it as `.md`).
+
+## When to run it
+
+- Before you upload a new Build of a game that will go to players.
+- Before you promote or release a version.
+- After a release fails for players, to find the cause, and then to add the
+  check that would have caught it (see the last section).
+
+For a jam build or a prototype nobody else plays, skip it.
+
+## How to report
+
+Run every check that applies. Each check needs **evidence**: a command's
+output or something you saw in the running game. Reading the project and
+deciding it looks right is not evidence.
+
+Report one line per check:
+
+- **pass**, with the evidence;
+- **fail**, with what you saw;
+- **not applicable**, with the reason (for example, no server);
+- **not run**, with what is still needed (for example, "needs a real online
+  join after publishing").
+
+A check that was not run is not a pass. Show the list to the user before you
+change anything; the user decides what to fix and whether to release with a
+check still open.
+
+## Test the file you upload
+
+Run the checks on the summer.games `.zip`, not on something close to it.
+Export the bundle (in the editor: **Project > Export**, preset
+**summer.games**, **Export Project**; from an agent: `summer_export_game`; or
+from a terminal), then take the server pack and the packaged build file out
+of it:
+
+```sh
+<summer> --headless --path . --import
+<summer> --headless --path . --export-release "summer.games" build/<game>.summer.zip
+mkdir -p build/bundle
+unzip -o build/<game>.summer.zip server.pck client.pck summer-bundle.json config/summer.build.json -d build/bundle
+```
+
+A game without a server has no `server.pck` or `config/`; `unzip` then
+warns about the missing names and extracts the rest.
+
+`<summer>` is the Summer Engine executable. Two look-alikes hide real
+failures:
+
+- **A server pack exported on its own** with your server preset
+  (`--export-pack`) is not the bundle's `server.pck`. For example, it keeps
+  `gameId`, which the bundle leaves out, so it can pass check 6 while the
+  uploaded `.zip` fails it.
+- **Local Play** always starts the authority scene by name, so it can't catch
+  check 1. It also runs without a hosted identity, so it can't catch check 6.
+
+## The checks
+
+Checks 1 and 2 apply to every game with a server (`summer.build.json` names
+a `server.exportPreset`). Checks 3 and 4 apply to every game with online
+play. Checks 5, 6 and 7 apply to every game.
+
+### 1. The server pack starts the authority scene
+
+**Why.** Summer starts a hosted World's `server.pck` with no scene argument,
+so the pack's own main scene decides what runs. The server preset must carry
+the custom feature `summer_authority`, and `project.godot` must set that
+feature's main scene:
+
+```ini
+[application]
+
+run/main_scene="res://client/main.tscn"
+run/main_scene.summer_client="res://client/main.tscn"
+run/main_scene.summer_authority="res://authority/main.tscn"
+```
+
+```ini
+# export_presets.cfg, the server preset
+platform="Linux"
+dedicated_server=true
+custom_features="summer_authority"
+```
+
+Without the feature, `run/main_scene.summer_authority` never applies and
+the server starts the players' main scene, usually the title screen. That
+scene never restores the World or tells Summer it is ready, so **every
+online join fails with `world_start_timeout`**. The bundle manifest still
+names the authority scene as the server's main scene, so reading the
+manifest proves nothing.
+
+**Check it.** Start the bundle's `server.pck` the way Summer does, with no
+scene argument, and stop it after a few seconds:
+
+```sh
+perl -e 'alarm shift; exec @ARGV' 15 <summer> --headless --verbose --main-pack build/bundle/server.pck
+```
+
+Find the first `Completed load for: 'res://….tscn'` line. It must be the
+authority scene: the `entry_point` of the `headless_engine` component in
+`world.json`. Later lines may complain that there is no hosted World; that
+is expected in a local run. Then confirm the source too: the server preset in
+`export_presets.cfg` has `summer_authority` in `custom_features`, and
+`project.godot` sets `run/main_scene.summer_authority`.
+
+**Fix.** Add `summer_authority` to the server preset's **Features > Custom**,
+set `application/run/main_scene.summer_authority` to the authority scene,
+export again and rerun the check. If your Summer version's export refuses a
+server pack that starts the wrong scene, that refusal is this check failing;
+run the check anyway, because older versions don't refuse it.
+
+### 2. Join online with the version you release
+
+**Why.** Check 1 runs on your computer. Players use a hosted server, and some
+failures, such as check 6, only show up there.
+
+**Check it.** Right after you publish or promote the version, open the game
+in a Summer Games app as a player, join online and play until you are in the
+game. Do it before you tell players about the update. An agent can't do this
+step; report it as **not run** and ask the user to do it, then record what
+they saw. If the join fails, see [Troubleshooting](#troubleshooting).
+
+### 3. Players can find online play
+
+**Why.** If nobody, including you, reaches online play, nobody notices when
+it breaks. A game hid online play behind a grown-ups setting, so its hosted
+join was never tried before release, and it failed for every player who
+found it.
+
+**Check it.** Start the client as a new player and follow the default path
+to online play. List every gate on that path: settings, parental or age
+gates, debug toggles. A new player should reach online play without
+changing a setting. If online play is off by default on purpose, the user
+must confirm that decision, and then check 2 must run before every release.
+
+### 4. The server saves online progress
+
+**Why.** Progress kept only in the player's local files is lost on
+reinstall or a new device, and players can edit it.
+
+**Check it.** In code, the authority loads each player's progress when they
+join (`Summer.authority.player_data.load(session)`) and saves it with
+`commit_public` or `commit_secret` (`summer-player-data`). Then play online,
+earn something, leave, and join again from a fresh install or another
+device. The progress must still be there. Local Play stores player data on
+disk; only hosted play proves it lasts.
+
+### 5. Players can get back to the title
+
+**Why.** A player with no way out of a session has to kill the app.
+
+**Check it.** Play into a session, online and offline, and find the way
+back: a pause menu or a **Leave** button. Use it, then start a new session
+from the title. In online play, leaving should call
+`Summer.client.leave()` before the title loads.
+
+### 6. The game doesn't hard-code its Game ID
+
+**Why.** The summer.games export is portable: the bundle's
+`summer.build.json` has no `gameId`. Summer takes the game's identity from
+wherever it runs: the Summer Games app, the hosted server or Local Play.
+Any other ID fails on the hosted server with `game_identity_mismatch`, "The
+initialized Game ID does not match hosted runtime context." The authority
+then stops before it restores the World or reports ready, and every online
+join ends in `world_start_timeout`, even though check 1 passes. The Summer
+Games app refuses a mismatched ID the same way.
+
+**Check it.**
+
+1. Find every call: `grep -rn "Summer.initialize" --include=*.gd .`
+2. For each, trace the argument back to where it comes from. It must be
+   nothing (`Summer.initialize()`) or an ID the game got from Summer. It must
+   never be a literal, a placeholder, or a fallback such as
+   `"game.my-game"` used when `gameId` is missing.
+3. `cat build/bundle/config/summer.build.json`: it has no `gameId`, so
+   anything the game reads from this file at run time comes back empty.
+
+Local Play and the local run in check 1 have no hosted identity, so a wrong
+ID passes there. Only check 2 proves this one.
+
+**Fix.** Call `Summer.initialize()` with no ID (Summer 0.7.1 and later), on
+the client and on the authority.
+
+### 7. Export with a released Summer, and its scripts compile on the players' runtime
+
+**Why.** The export records which Summer made it, in the client pack's
+`.summer/export.json` and under `export` in the bundle's
+`summer-bundle.json`: `summerVersion` and `engineSha`. Players' apps run the
+game on a released Summer runtime with the same MAJOR.MINOR and a patch at
+least the stamped one. A development build of Summer
+can stamp a version that is already released while it has APIs that release
+lacks. Scripts that use them then fail to compile on every player's device,
+and the game opens to an empty or black window. Summer doesn't compile
+scripts when you upload, so every upload check passes.
+
+**Check it.**
+
+1. Read the stamp: `cat build/bundle/summer-bundle.json`. The export log
+   shows it too: `Exported by Summer <version> (engine <sha>)`.
+2. `summerVersion` must be a released Summer version, and `engineSha` must
+   equal that release's `engineSha` in
+   `downloads.summer.games/engine-templates/<summerVersion>/manifest.json`
+   (published for Summer 0.7.1 and later). If it differs, or that address has
+   nothing for the version, a development build made the export.
+3. Run the client pack on that released Summer, and fail on any compile
+   error. The run exits normally even when a script fails, so the grep is the
+   check:
+
+   ```sh
+   perl -e 'alarm shift; exec @ARGV' 60 <released-summer> --headless --verbose --main-pack build/bundle/client.pck --quit-after 600 > build/client-run.log 2>&1
+   grep -E 'SCRIPT ERROR|Parse Error|Failed to load script' build/client-run.log
+   ```
+
+   `<released-summer>` is the Summer executable of the stamped version from
+   the download page, not the development build that made the export. The
+   grep must print nothing. The run compiles the scripts that the main
+   scene and autoloads load; a script that loads only later in play compiles
+   when play reaches it, so check 2 still matters for online games.
+
+**Fix.** Ask the user to install the current Summer release from
+https://summerengine.com/download (or, with their OK, run
+`summer install --yes`). Export again with it, and rerun this check on the
+new `.zip` before you upload it.
+
+## Troubleshooting
+
+### Every online join fails with `world_start_timeout`, but Local Play works
+
+Most likely, in this order:
+
+1. The server pack starts the wrong scene. Run check 1.
+2. The game passes a fixed Game ID. Run check 6.
+
+After the fix, export a new `.zip`, upload it, promote it and run check 2.
+
+### The game opens to a blank window for every player
+
+The game works in your editor, but every player sees an empty or black
+window. Running the client pack as in check 7 prints
+`Parse Error: Static function "…" not found` and
+`Failed to load script "res://…"`. A development build of Summer made the
+export, and the scripts use something the released version doesn't have.
+Re-export with the current Summer release, upload the new version and
+promote it.
+
+### The game server's log is empty
+
+An empty server log is not proof that the server hung or never started. A
+release server holds back what the game prints until it exits when it isn't
+attached to a terminal, so its log can look empty while the title scene
+runs. Don't debug from the empty log; run check 1 on your own computer to
+see which scene starts.
+
+## Add a check after every incident
+
+The list grows from real failures. When a release fails in a way no check
+here would have caught:
+
+1. Fix the game, and record the cause in the project's `.summer/memory/`.
+2. Write the check that would have caught it: **Why**, **Check it** (a
+   command to run or something to observe, against the real summer.games
+   `.zip`), and **Fix**.
+3. Propose it for this skill and for the docs page
+   (`/publishing/release-readiness`), with the same number in both, through
+   a pull request to summerengine/summer and to the docs. Until it lands,
+   keep it in the project's memory so the next release runs it.
+
+## Checklist
+
+- [ ] Ran the checks on the summer.games `.zip` you upload, not a separately exported pack.
+- [ ] 1. The bundle's `server.pck`, run with no scene, loads the authority scene first.
+- [ ] 2. A real online join with the released version reaches the game (or is reported as not run).
+- [ ] 3. A new player reaches online play without changing a setting, or the user confirmed it is off on purpose.
+- [ ] 4. Online progress is loaded and committed through authority player data, and survives a fresh install.
+- [ ] 5. Players can get back to the title from inside a session, online and offline.
+- [ ] 6. Every `Summer.initialize` passes no ID, or an ID the game got from Summer.
+- [ ] 7. The export stamp names a released Summer and its `engineSha`, and `client.pck` run on that released Summer prints no `SCRIPT ERROR`, `Parse Error` or `Failed to load script`.
+- [ ] One line per check reported to the user before anything is changed.

package/library/skills/release-readiness/resource.yaml

@@ -0,0 +1,41 @@
+id: skill/release-readiness
+kind: skill
+version: 1.0.0
+summary: "Before releasing a Summer game version, prove players can play it: server scene, online join, saved progress, no fixed Game ID, a released Summer compiles it."
+use_when:
+  - "before uploading, promoting or releasing a new version to players: is it ready to release"
+  - "every online join fails with world_start_timeout, or the hosted server's log is empty, while Local Play works"
+  - "Summer.initialize fails with game_identity_mismatch: the initialized Game ID does not match hosted runtime context"
+  - "checking that a hosted game's server.pck starts the authority scene and not the title screen"
+  - "players get a blank or black screen when they open the released game, but it runs in the editor: client scripts fail with Parse Error or Failed to load script"
+  - "a game release failed for players and the check that would have caught it needs adding"
+do_not_use_when:
+  - "only producing a local export for a jam or prototype nobody else plays — skill/export-and-ship"
+facets:
+  lifecycle:
+    - launch
+    - support
+  domains:
+    - deployment
+    - multiplayer
+    - playtest
+  modalities:
+    - project
+    - docs
+compatibility:
+  engine: ">=4.6"
+related:
+  skills:
+    - skill/multiplayer
+    - skill/multiplayer-publish
+    - skill/multiplayer-testing
+    - skill/multiplayer-project
+    - skill/summer-player-data
+    - skill/publish-your-game
+    - skill/export-and-ship
+    - skill/make-game
+    - skill/bounded-engine-runs
+source: official
+license: MIT
+status: preview
+recommended: false

package/library/skills/summer-parties/SKILL.md

@@ -57,7 +57,7 @@ func _ready() -> void:
 	spawner.state_group_created.connect(_on_group_created)
 	spawner.entity_spawned.connect(_on_entity_spawned)
 	spawner.event_received.connect(_on_event)
-	var initialized: SummerResult = await Summer.initialize(Game.GAME_ID).get_result_or_completed_signal()
+	var initialized: SummerResult = await Summer.initialize().get_result_or_completed_signal()
 	if not initialized.ok:
 		push_error(initialized.message)
 		return

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "summer-engine",
-  "version": "3.5.0",
+  "version": "3.5.2",
   "description": "Local Summer CLI and MCP server for Summer Engine. Install and run the engine, connect Claude Code, Cursor, Codex, Gemini, and other agents, and build real games with bundled skills, hooks, and plugins.",
   "keywords": [
     "summer-engine",

package/registry/generated/counts.json

@@ -4,9 +4,9 @@
     "collection": 0,
     "example": 0,
     "reference": 9,
-    "skill": 122,
+    "skill": 123,
     "template": 19,
     "tool": 105
   },
-  "total": 255
+  "total": 256
 }

package/registry/generated/gemini-extension.json

@@ -1,7 +1,7 @@
 {
   "_generated": "GENERATED from integrations/gemini — do not edit; npm run generate:registry",
   "name": "summer",
-  "version": "3.5.0",
+  "version": "3.5.2",
   "description": "Agent tooling for Summer Engine: MCP bridge, context primer, and game-dev skills. Use with the npm CLI for skill files on disk.",
   "contextFileName": "GEMINI.md",
   "mcpServers": {
@@ -93,6 +93,7 @@
     "./library/skills/psx-retro-rendering/",
     "./library/skills/publish-your-game/",
     "./library/skills/realtime-wet-surfaces/",
+    "./library/skills/release-readiness/",
     "./library/skills/remote-deploy/",
     "./library/skills/retarget/",
     "./library/skills/running-in-the-cloud/",

package/registry/generated/index.json

@@ -1599,7 +1599,7 @@
       "id": "skill/export-and-ship",
       "kind": "skill",
       "version": "1.0.3",
-      "content_hash": "6d8551fc18fd82ae6c71df61ca5798c0f0753a89b83e45824e3b87828b871d93",
+      "content_hash": "d255ed8ed7d74ed8f8b8a67dde9e774fd877135392758e706ba34242e2453715",
       "summary": "Assess and prepare a game export: inventory installed templates and targets, validate release assets and config, produce supported builds after approval.",
       "use_when": [
         "the user wants to assess or prepare a Summer game export — Steam, itch, HTML5, iOS, Android targets as available in the installed build",
@@ -2146,7 +2146,7 @@
       "id": "skill/make-game",
       "kind": "skill",
       "version": "1.1.0",
-      "content_hash": "eba4e2b75b685fa814b218d8fd6c4cac0e4f4f692030645ab7e37d36c1caf83d",
+      "content_hash": "6b254b93c236527ecf7d7a3128aa9daa3fe264e533a011ce7cb829df4fd90a32",
       "summary": "Orchestration spine for 'make me a game': brainstorm, plan, scaffold, mechanics, art, audio, polish, verify, ship — delegates to specialist skills.",
       "use_when": [
         "the user says 'make me a game', 'build me a game', 'I want to make a [genre] game', or 'let's build something' — running the full game-dev pipeline",
@@ -2173,6 +2173,7 @@
         "skills": [
           "skill/audio-direction",
           "skill/export-and-ship",
+          "skill/release-readiness",
           "skill/design-mechanic",
           "skill/tune-performance",
           "skill/art-direction",
@@ -2193,7 +2194,7 @@
       "id": "skill/multiplayer",
       "kind": "skill",
       "version": "1.0.0",
-      "content_hash": "7a7212fba4b1aee4d9c9e5649b2ade77836829e6d9409e010b9731d79232305b",
+      "content_hash": "06771fb6465e2ed96bb03900d98e1b53bb79e36cda4f5540d8371fc4308274d5",
       "summary": "Start here for Summer multiplayer: how the authority, clients, Worlds and Sessions fit, and which skill comes next.",
       "use_when": [
         "the user wants multiplayer, co-op, PvP, online play over the internet, or to play with friends in a Summer game",
@@ -2224,6 +2225,7 @@
           "skill/multiplayer-state",
           "skill/multiplayer-testing",
           "skill/multiplayer-publish",
+          "skill/release-readiness",
           "skill/summer-matchmaking",
           "skill/summer-player-data"
         ]
@@ -2235,7 +2237,7 @@
       "id": "skill/multiplayer-movement",
       "kind": "skill",
       "version": "1.0.0",
-      "content_hash": "ab68306636a6916030e4c1a6c3e06fb41cefb13bb1b47a5c2f0fa08e24067508",
+      "content_hash": "b48c1aa09e885071d5007ecd8863a38f9bd467fa216314bac329a6bbc8df6e68",
       "summary": "Client-side movement in Summer multiplayer: owners move instantly, others glide, the authority checks each pose.",
       "use_when": [
         "moving players in a Summer multiplayer game: each player's own character, other players drawn smoothly",
@@ -2274,7 +2276,7 @@
       "id": "skill/multiplayer-project",
       "kind": "skill",
       "version": "1.0.0",
-      "content_hash": "801ded4cdd3cff6ca060fa920c6738ffe26eff3e8cff63ea88dfe3d185931886",
+      "content_hash": "c730c94e08e9807ad9404f4104eb1ad389c1a73e47a804929b31db29c8497b17",
       "summary": "Set up a Summer multiplayer project: both entry scenes, World and queue files, joining, and a first Local Play run.",
       "use_when": [
         "making a Summer game playable online or co-op: the first multiplayer setup",
@@ -2319,7 +2321,7 @@
       "id": "skill/multiplayer-publish",
       "kind": "skill",
       "version": "1.0.0",
-      "content_hash": "52117117e661cbd898d4faece8f72ef2304118999c80bce55a709619e8cec289",
+      "content_hash": "9b716c90273e17b261123d2ee828bc7eadc1d7ca73ed040bf007cd20a2fbae96",
       "summary": "Ship a hosted Summer multiplayer game: the summer.games bundle, server preset, pre-upload checks, and a new Build.",
       "use_when": [
         "publishing a hosted Summer multiplayer game online so other players can join it",
@@ -2346,7 +2348,8 @@
         "skills": [
           "skill/multiplayer",
           "skill/multiplayer-project",
-          "skill/multiplayer-testing"
+          "skill/multiplayer-testing",
+          "skill/release-readiness"
         ]
       },
       "status": "preview",
@@ -2356,7 +2359,7 @@
       "id": "skill/multiplayer-state",
       "kind": "skill",
       "version": "1.0.0",
-      "content_hash": "64c1639093e7d51a39125236270278799fcddc42dab98cdf3d2649deec09d912",
+      "content_hash": "38e79fe70609234ad717f00685b6165e2dd41ee860ce0b721a07ac2f56ad80f4",
       "summary": "Authority-owned game state in Summer multiplayer: shared and private State groups, validated Commands, and Events.",
       "use_when": [
         "score, health, doors, rounds, inventories or wallets in a Summer multiplayer game, and who owns them",
@@ -2400,7 +2403,7 @@
       "id": "skill/multiplayer-testing",
       "kind": "skill",
       "version": "1.0.0",
-      "content_hash": "dd727ec7384785d9515dd7e906c46d4229e600a752aef81f5a645e908470a536",
+      "content_hash": "115c160d7e42a95589bac14a572811b0c9c3b26b37c5386b6eb647f2889ef162",
       "summary": "Test a Summer multiplayer game with Local Play: several players, a bad network, bots, and what a passing run shows.",
       "use_when": [
         "running or testing a Summer multiplayer game locally with several players (Local Play)",
@@ -2432,6 +2435,7 @@
           "skill/multiplayer-movement",
           "skill/multiplayer-state",
           "skill/multiplayer-publish",
+          "skill/release-readiness",
           "skill/summer-friends",
           "skill/summer-match-results",
           "skill/summer-matchmaking",
@@ -2824,7 +2828,7 @@
       "id": "skill/publish-your-game",
       "kind": "skill",
       "version": "1.0.0",
-      "content_hash": "b39692641d859b1d5a9d9b2e990bed521b0aba52319d336b4e3633c253a07a60",
+      "content_hash": "0328c6d71f662059cc2514864e005c2e71cf90811553ef2a2ecabbbf9cb4305f",
       "summary": "Publish a Summer game on Summer Games through MCP: store page, art, build upload, submit, and one approval link for the owner.",
       "use_when": [
         "the user says 'publish my game', 'put it on summer.games', 'launch it on the store' or 'submit it for review'",
@@ -2892,6 +2896,54 @@
       "status": "preview",
       "recommended": false
     },
+    {
+      "id": "skill/release-readiness",
+      "kind": "skill",
+      "version": "1.0.0",
+      "content_hash": "f6336bb2d8c2b5915a397d5a49341d142e8988ee3091d557950da0307f47761d",
+      "summary": "Before releasing a Summer game version, prove players can play it: server scene, online join, saved progress, no fixed Game ID, a released Summer compiles it.",
+      "use_when": [
+        "before uploading, promoting or releasing a new version to players: is it ready to release",
+        "every online join fails with world_start_timeout, or the hosted server's log is empty, while Local Play works",
+        "Summer.initialize fails with game_identity_mismatch: the initialized Game ID does not match hosted runtime context",
+        "checking that a hosted game's server.pck starts the authority scene and not the title screen",
+        "players get a blank or black screen when they open the released game, but it runs in the editor: client scripts fail with Parse Error or Failed to load script",
+        "a game release failed for players and the check that would have caught it needs adding"
+      ],
+      "facets": {
+        "lifecycle": [
+          "launch",
+          "support"
+        ],
+        "domains": [
+          "deployment",
+          "multiplayer",
+          "playtest"
+        ],
+        "modalities": [
+          "project",
+          "docs"
+        ]
+      },
+      "compatibility": {
+        "engine": ">=4.6"
+      },
+      "related": {
+        "skills": [
+          "skill/multiplayer",
+          "skill/multiplayer-publish",
+          "skill/multiplayer-testing",
+          "skill/multiplayer-project",
+          "skill/summer-player-data",
+          "skill/publish-your-game",
+          "skill/export-and-ship",
+          "skill/make-game",
+          "skill/bounded-engine-runs"
+        ]
+      },
+      "status": "preview",
+      "recommended": false
+    },
     {
       "id": "skill/remote-deploy",
       "kind": "skill",
@@ -3786,7 +3838,7 @@
       "id": "skill/summer-parties",
       "kind": "skill",
       "version": "1.0.0",
-      "content_hash": "f32352dafa1077cf124a7ef4136041333bc8c73110fe37545e393ec6d862f4cd",
+      "content_hash": "3e306760574435b38fa0d0aefddf9569ea733a1dce0f279bed1c1e7fc072a7c8",
       "summary": "Let a Summer party play together: the leader presses Play, members follow into the same match. Hosted only.",
       "use_when": [
         "friends in a Summer party should land in the same multiplayer match: party play, play with friends, squad up",

package/registry/generated/marketplace.claude.json

@@ -11,7 +11,7 @@
     {
       "name": "summer",
       "source": "./",
-      "version": "3.5.0",
+      "version": "3.5.2",
       "description": "Agent tooling for Summer Engine: game-dev skills, lifecycle hooks, and a 105-tool MCP bridge to the local desktop app.",
       "author": {
         "name": "Summer Engine",

package/registry/generated/plugin.claude.json

@@ -2,7 +2,7 @@
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "_generated": "GENERATED from integrations/claude — do not edit; npm run generate:registry",
   "name": "summer",
-  "version": "3.5.0",
+  "version": "3.5.2",
   "description": "Agent tooling for Summer Engine: game-dev skills, lifecycle hooks, and a 105-tool MCP bridge to the local desktop app.",
   "author": {
     "name": "Summer Engine",
@@ -96,6 +96,7 @@
     "./library/skills/psx-retro-rendering/",
     "./library/skills/publish-your-game/",
     "./library/skills/realtime-wet-surfaces/",
+    "./library/skills/release-readiness/",
     "./library/skills/remote-deploy/",
     "./library/skills/retarget/",
     "./library/skills/running-in-the-cloud/",

package/registry/generated/plugin.codex.json

@@ -1,7 +1,7 @@
 {
   "_generated": "GENERATED from integrations/codex — do not edit; npm run generate:registry",
   "name": "summer",
-  "version": "3.5.0",
+  "version": "3.5.2",
   "description": "Agent tooling for Summer Engine: game-dev skills, lifecycle hooks, and a 105-tool MCP bridge. Build games by talking.",
   "author": {
     "name": "Summer Engine",
@@ -91,6 +91,7 @@
     "./library/skills/psx-retro-rendering/",
     "./library/skills/publish-your-game/",
     "./library/skills/realtime-wet-surfaces/",
+    "./library/skills/release-readiness/",
     "./library/skills/remote-deploy/",
     "./library/skills/retarget/",
     "./library/skills/running-in-the-cloud/",

package/registry/generated/plugin.cursor.json

@@ -3,7 +3,7 @@
   "_generated": "GENERATED from integrations/cursor — do not edit; npm run generate:registry",
   "name": "summer",
   "displayName": "Summer",
-  "version": "3.5.0",
+  "version": "3.5.2",
   "description": "Agent tooling for Summer Engine: game-dev skills, lifecycle hooks, and a 105-tool MCP bridge to the local desktop app.",
   "author": {
     "name": "Summer Engine",
@@ -103,6 +103,7 @@
     "./library/skills/psx-retro-rendering/",
     "./library/skills/publish-your-game/",
     "./library/skills/realtime-wet-surfaces/",
+    "./library/skills/release-readiness/",
     "./library/skills/remote-deploy/",
     "./library/skills/retarget/",
     "./library/skills/running-in-the-cloud/",

package/registry/generated/plugin.factory.json

@@ -2,7 +2,7 @@
   "_generated": "GENERATED from integrations/factory — do not edit; npm run generate:registry",
   "name": "summer",
   "description": "Agent tooling for Summer Engine: game-dev skills, lifecycle hooks, and a 105-tool MCP bridge to the local desktop app.",
-  "version": "3.5.0",
+  "version": "3.5.2",
   "author": {
     "name": "Summer Engine",
     "email": "founders@summerengine.com",
@@ -88,6 +88,7 @@
     "./library/skills/psx-retro-rendering/",
     "./library/skills/publish-your-game/",
     "./library/skills/realtime-wet-surfaces/",
+    "./library/skills/release-readiness/",
     "./library/skills/remote-deploy/",
     "./library/skills/retarget/",
     "./library/skills/running-in-the-cloud/",