summer-engine 3.3.0 → 3.4.1

package/library/skills/spatial-placement/SKILL.md

@@ -59,7 +59,7 @@ defined relative to a rotated subject; then use `directionSpace="local"`.
 - `grounded: true` means downward support was detected. It does not mean the
   object is centered or otherwise well placed.
 - `contactStatus` and `contacts` identify touching or overlapping colliders.
-  Godot's shape query cannot distinguish touching from penetration here.
+  The physics shape query cannot distinguish touching from penetration here.
 - `directions.<label>.status` is `blocked` when clearance is below the tool's
   threshold; `distance` is measured from the subject bounds.
 - `evidence: "physics"` is exact collider-query evidence.
@@ -93,7 +93,7 @@ defined relative to a rotated subject; then use `directionSpace="local"`.
 5. Check: `summer_measure` plane mode on each facade line (every front on one
    plane), pair mode on joints you doubt, `summer_starcast` with
    `directionSpace: "local"` on mounted pieces, `summer_test_placement` before
-   committing a piece in a tight spot. Starcast's local names follow Godot:
+   committing a piece in a tight spot. Starcast's local names follow the engine:
    `forward` is -Z, `back` is +Z. A piece with a -Z back should read
    `forward` blocked by the wall at about the standoff (or the wall in
    `contacts` when flush) and `back` open.

package/library/skills/spatial-placement/references/kit-placement-tools.md

@@ -30,7 +30,7 @@ Read it before the first call in a task. The workflow that uses them is in
   declared in `truncated: {list: {shown, total}}`.
 - **No silent fallback.** A missing op answers `engine_lacks_op`; a measurement
   that cannot be made answers a named `failure_reason`.
-- **Engine ops.** No new engine op. Reads run one read-only GDScript probe
+- **Engine ops.** Reads run one read-only GDScript probe
   through `RunSceneScript` (the op behind `summer_run_script`: in-process, no
   child editor, `undo: "none"`, no checkpoint). Mutations are ordinary
   `SetProp`, `SnapToSurface` and `InstantiateScene` ops: one undo step per
@@ -52,11 +52,11 @@ Read it before the first call in a task. The workflow that uses them is in
 | Pipe or duct end to end | `summer_connect_ports` |
 | What is in front of this point, and its normal? | `summer_raycast` |
 | Gap or overlap between two pieces; is the facade front flat? | `summer_measure` |
-| What surrounds a placed piece, which side is blocked? | `summer_starcast` (existing) |
-| Will a pose fit before I commit it in a tight spot? | `summer_test_placement` (existing) |
-| Seat a prop on a floor, table or ledge | `summer_snap_to_surface` (existing) |
-| Line up or equally space 2-16 placed pieces on one axis | `summer_align_distribute_3d` (existing) |
-| Did exactly that change, and does it look right? | `summer_world_snapshot` + `summer_snapshot_diff`, then `summer_screenshot` (existing) |
+| What surrounds a placed piece, which side is blocked? | `summer_starcast` |
+| Will a pose fit before I commit it in a tight spot? | `summer_test_placement` |
+| Seat a prop on a floor, table or ledge | `summer_snap_to_surface` |
+| Line up or equally space 2-16 placed pieces on one axis | `summer_align_distribute_3d` |
+| Did exactly that change, and does it look right? | `summer_world_snapshot` + `summer_snapshot_diff`, then `summer_screenshot` |
 
 ## `summer_inspect_asset`
 
@@ -133,20 +133,20 @@ instances it off the scene tree, measures, and frees it.
 
 ## `summer_instantiate_scene` (placed)
 
-- **Arguments added:** `position`, `rotation_degrees`, `scale` (`[x, y, z]`,
+- **Placement arguments:** `position`, `rotation_degrees`, `scale` (`[x, y, z]`,
   parent-local) or `transform` (`"Transform3D(xx, xy, xz, yx, yy, yz, zx, zy,
   zz, ox, oy, oz)"`). Not `transform` with the others; not `scale` or
   `transform` with `target_size`.
 - **Behaviour:** `InstantiateScene` (its own request, as the engine requires),
   then one `SetProp` request on the node path the receipt reports (a name
-  collision rename is followed), then `SaveScene`. Without the new fields it is
-  unchanged.
+  collision rename is followed), then `SaveScene`. Without these fields it only
+  instances the piece.
 - **Result:** the merged receipt (`results` holds every op; the per-request
   `receipts` copies are kept only when something failed) plus
   `placement {nodePath, applied, fields, space: "parent_local"}`.
 - **Ops:** `InstantiateScene`, `SetProp`, `SaveScene`.
 
-## `summer_batch` additions
+## `summer_batch` placement
 
 - `InstantiateScene` ops may carry the same placement fields (arrays or
   `"Vector3(...)"` strings). Each piece is one op; its `SetProp`s are sent right
@@ -161,8 +161,7 @@ instances it off the scene tree, measures, and frees it.
   transforms of a run of `InstantiateScene` ops are held back and sent
   together (up to 200 `SetProp`s per request) just before the next op that is
   not an `InstantiateScene`, riding along with it when it can. A batch of N
-  placed pieces is therefore about N + 2 requests and N + 2 undo steps (it was
-  2N + 1). Every later op in the list (a `SetProp`, `SnapToSurface`, a query,
+  placed pieces is therefore about N + 2 requests and N + 2 undo steps. Every later op in the list (a `SetProp`, `SnapToSurface`, a query,
   the save) runs after the transforms land. If an `InstantiateScene` fails,
   the pieces created before it still get their transforms; nothing is saved.
 
@@ -245,7 +244,7 @@ instances it off the scene tree, measures, and frees it.
   in front of the hit plane); `hit_normal_pointed_away_from_the_ray_flipped`
   (the ray hit a back face; the piece still mounts on the ray's side).
 - **Check after:** `summer_starcast` with `directionSpace: "local"`. Its local
-  names follow Godot (`forward` = -Z, `back` = +Z), so a -Z back reads
+  names follow the engine (`forward` = -Z, `back` = +Z), so a -Z back reads
   `forward` blocked (or the surface in `contacts` when seated flush) and `back`
   open.
 - **Limits:** the back face is the visible-mesh AABB in the piece's own axes;
@@ -353,12 +352,3 @@ instances it off the scene tree, measures, and frees it.
 - **Result, plane:** `{coplanar, plane, spread, off_plane_count, nodes [{path,
   face, deviation, off_plane: proud|recessed}], no_geometry?}`.
 - **Ops:** `RunSceneScript` (read-only).
-
-## What belongs in the engine later
-
-These tools compose existing ops. Natively they would be faster and exact:
-an `InstantiateScene` that takes a transform (one request, one undo step per
-piece), a compact `summer_batch` receipt mode in the ops executor, a raycast and
-a measure op that need no script and do not mark the active tab unsaved, an
-asset-geometry op that reads the import cache without instancing, and an
-oriented-bounds (OBB) query so rotated pieces stop needing `space: "local"`.

package/library/skills/sprite-sheet/SKILL.md

@@ -5,7 +5,7 @@ license: MIT
 compatibility: [Cursor, Claude Code, Windsurf, Codex]
 category: 2d-assets
 user-invocable: true
-allowed-tools: Read Grep Glob Write Edit summer_generate_image summer_slice_asset_sheet summer_get_studio_workflow summer_search_assets summer_import_from_url summer_import_asset_by_id summer_set_resource_property summer_add_node summer_set_prop
+allowed-tools: Read Grep Glob Write Edit summer_generate_image summer_slice_asset_sheet summer_get_studio_workflow summer_search_assets summer_import_from_url summer_import_asset_by_id summer_set_resource_property summer_write_file summer_add_node summer_set_prop summer_save_scene
 paths: ["assets/**", "sprites/**", "art/sprites/**"]
 ---
 
@@ -13,7 +13,7 @@ paths: ["assets/**", "sprites/**", "art/sprites/**"]
 
 This skill produces a grid of animation frames for a 2D character — walk cycle, idle bob, attack swing, death sequence — and wires the result into an `AnimatedSprite2D` via a `SpriteFrames` resource.
 
-**Up-front honesty:** sprite-sheet generation from a single text-to-image call is **unreliable**. Models can render "a sprite sheet of a knight walking" and produce 8 frames, but the inter-frame consistency (same anatomy, same costume, same lighting) is poor. Limbs morph between frames. Pixel sprites get extra fingers in frame 3. The result usually looks worse than the static sprite did.
+Sprite-sheet generation from a single text-to-image call is **unreliable**. Models can render "a sprite sheet of a knight walking" and produce 8 frames, but the inter-frame consistency (same anatomy, same costume, same lighting) is poor. Limbs morph between frames. Pixel sprites get extra fingers in frame 3. The result usually looks worse than the static sprite did.
 
 This skill therefore offers **three paths**, ranked by reliability:
 
@@ -38,7 +38,7 @@ So do not tell the user to cut a generated sheet by hand or in ImageMagick. The
 - The character is 3D — use `generate-motion` for skeletal animation.
 - The user wants a single static sprite → `pixel-art` or `character-portrait`.
 - The user wants UI animation (loading spinner, button hover) — animate via `AnimationPlayer` rotating/tweening a static texture instead. Don't sprite-sheet UI.
-- The user has 12+ frames per animation and 4+ animations — that's hundreds of generations at $0.02 each. Pause and discuss budget.
+- The user has 12+ frames per animation and 4+ animations. That is dozens to hundreds of generations, each using credits. Pause and agree on scope first.
 
 ## Steps
 
@@ -62,7 +62,7 @@ Ask the user (or decide based on context):
 | Higher-res character (128px+), 6-12 frames | **Per-frame img2img** |
 | User wants exact-pixel consistency | **Aseprite manual** — AI cannot deliver exact pixels |
 
-State the path before starting: "I'll do per-frame img2img — 6 generations, ~$0.12. The first frame is the base; each next frame uses the previous as reference. OK?"
+State the path before starting: "I'll do per-frame img2img: 6 generations. The first frame is the base; each next frame uses the previous one as reference. OK?"
 
 ### 3a. Path 1 — Per-frame img2img
 
@@ -74,11 +74,11 @@ summer_generate_image(
   referenceImageUrl="<frame 1 fileUrl>",
   model="nano-banana-2",
   style="<same as base>",
-  options={ removeBackground: true }
+  removeBackground=true
 )
 ```
 
-`summer_generate_image` has no `image_size` and no `negative_prompt` — put negations in the prompt text; there is no size argument at all. `options.removeBackground: true` is real and gives you true alpha instead of a prompted "transparent background" the model may paint as a literal checkerboard. `referenceImageUrl` only works on edit-capable models (`nano-banana-2`, `seedream-5-pro`, `nano-banana-lite`, `gpt-image-2`, `gemini-flash`, `flux-2`); `grok-imagine` has no edit endpoint and returns `edit_not_supported`.
+`summer_generate_image` has no size argument; put negations in the prompt text. `removeBackground: true` gives you real alpha instead of a prompted "transparent background" that the model may paint as a literal checkerboard. `referenceImageUrl` only works on edit-capable models (`nano-banana-2`, `seedream-5-pro`, `nano-banana-lite`, `gpt-image-2`, `gemini-flash`, `flux-2`); `grok-imagine` has no edit endpoint and returns `edit_not_supported`.
 
 Repeat for each frame. Save each as `goblin_walk_01.png`, `goblin_walk_02.png`, etc.
 
@@ -93,11 +93,11 @@ summer_generate_image(
   prompt="goblin warrior walk cycle, sprite sheet, 6 frames in a horizontal row, identical character across frames, side view, frames clearly separated with empty space between them, consistent lighting, consistent palette. No scene background, no varying lighting, not a different character per frame.",
   model="nano-banana-2",
   style="none",
-  options={ removeBackground: true }
+  removeBackground=true
 )
 ```
 
-There is no `"pixel"` style preset (`style` is `realistic | cartoon | anime | none`; anything else is coerced to `none`), no `image_size`, and no `negative_prompt` — the layout and the negations have to be in the prompt.
+There is no `"pixel"` style preset (`style` is `realistic | cartoon | anime | none`; anything else is coerced to `none`) and no size argument; the layout and the negations have to be in the prompt.
 
 Then cut it with the same server-side slicer Studio uses, passing the asset id the generation returned:
 
@@ -113,7 +113,7 @@ Inspect the result. If the frames are coherent and the count matches, proceed. I
 
 Tell the user:
 
-> AI sprite-sheet generation is unreliable — best path for clean pixel animation is to hand-author in Aseprite (or Piskel for free in-browser). Onion-skin frame-by-frame; ~10 minutes for a 4-frame walk cycle. Want me to generate a base reference image you can trace?
+> AI sprite-sheet generation is unreliable. For clean pixel animation, hand-author it in Aseprite (or Piskel, free in the browser). Onion-skin frame-by-frame; ~10 minutes for a 4-frame walk cycle. Want me to generate a base reference image you can trace?
 
 If yes, generate the static base via `pixel-art` and stop here. The user takes it to Aseprite.
 
@@ -223,7 +223,7 @@ Frame 3: summer_generate_image(prompt="<base + delta>", referenceImageUrl="<fram
 ...
 ```
 
-Tell the user to run via the Summer dashboard. Or recommend Aseprite (paid, $20) / Piskel (free in-browser) for hand-authoring — for pixel art under 64×64, it is the faster path even with MCP available.
+Tell the user to run via the Summer dashboard. Or recommend Aseprite (paid) or Piskel (free, in the browser) for hand-authoring — for pixel art under 64×64, it is the faster path even with MCP available.
 
 ## Handoff
 

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

@@ -142,6 +142,6 @@ Every failure is final: none of them asks you to capture again.
 
 ## See also
 
-- `skill/multiplayer` — where the client and the authority run
-- `skill/multiplayer-state` — the authority's Command handlers, where most events happen
-- `skill/summer-match-results` — results and ratings, which Summer records itself
+- `multiplayer` — where the client and the authority run
+- `multiplayer-state` — the authority's Command handlers, where most events happen
+- `summer-match-results` — results and ratings, which Summer records itself

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

@@ -42,7 +42,7 @@ Declining never blocks play. A game must work without these permissions.
 
 **Availability:**
 
-- **Engine release.** This needs an engine that includes Summer Engine PR #508. On engines without it, `Summer.client.friends` does not exist and scripts that use it fail to parse. Check the class reference for `SummerClientFriends` before using this skill.
+- **Engine release.** This needs an engine release that includes `SummerClientFriends`. On older engines, `Summer.client.friends` does not exist and scripts that use it fail to parse. Check the class reference for `SummerClientFriends` before using this skill.
 - **Hosted only.** `is_available()` is `false` in Local Play and editor runs, for guests, for accounts the platform keeps out of social features (`age_restricted`, under 13), and in Summer apps without `player.friends@1` (friends) or `player.messaging@1` (messages).
 - **Overlays.** The screens need the Summer app to offer friends and parties; otherwise they fail with `capability_unavailable` or `ui_unavailable`.
 
@@ -133,8 +133,8 @@ How it behaves:
 - **When the list is read again.** With a handler on `changed`, the engine re-reads the list on every change hint, after a consent decision, on `refresh()`, and about every 60 seconds while the game is in front. Never poll yourself.
 - **Statuses.** Show `in_this_game` friends first. `unknown` means presence couldn't be read; it is not `offline`.
 - **Rows.** Key them by `user_id`; each read replaces the `SummerFriend` objects.
-- **Profiles of other players.** For the people in the current match, use the user ids your authority publishes (the `players` map in `skill/summer-world-chat`, step 1) and call `show_profile(user_id)`. Your own id fails with `invalid_argument`.
-- **Inviting a friend into a match.** Use the party invite sheet (`skill/summer-parties`).
+- **Profiles of other players.** For the people in the current match, use the user ids your authority publishes (the `players` map in `summer-world-chat`, step 1) and call `show_profile(user_id)`. Your own id fails with `invalid_argument`.
+- **Inviting a friend into a match.** Use the party invite sheet (`summer-parties`).
 
 ### 3. Direct messages (only if chat is central)
 
@@ -188,7 +188,7 @@ Local Play has no accounts, so check the hidden path locally:
 - there are no script errors.
 
 ```
-summer_project_setting name="summer/local_play/players" value=2
+summer_project_setting key="summer/local_play/players" value=2
 summer_play
 summer_get_diagnostics
 summer_stop
@@ -199,7 +199,7 @@ and revoke access in the Summer app, and watch `access_changed`.
 
 ## Checklist
 
-- [ ] The engine's class reference lists `SummerClientFriends` (Summer Engine PR #508 or later).
+- [ ] The engine's class reference lists `SummerClientFriends`.
 - [ ] `summer.build.json` declares exactly the permissions the code asks for.
 - [ ] Local Play: friends features are hidden, with no script errors.
 - [ ] Declining consent leaves the game fully playable, and the button can ask again later.
@@ -216,11 +216,11 @@ and revoke access in the Summer app, and watch `access_changed`.
 | Treat `unknown` as `offline` | Show it as unknown | It means presence couldn't be read |
 | Poll `refresh()` on a timer | Connect `changed` | The engine already re-reads while a handler is connected |
 | Declare every permission "just in case" | Declare only what you use | The consent sheet lists each declared permission |
-| Use friends to put players in one match | `skill/summer-parties` | Parties are how players play together |
+| Use friends to put players in one match | `summer-parties` | Parties are how players play together |
 
 ## See also
 
-- `skill/summer-parties`: playing together, the invite sheet
-- `skill/summer-world-chat`: chat inside a match
-- `skill/multiplayer-publish`: `summer.build.json` and publishing a Build
-- `skill/multiplayer-testing`: what Local Play can and can't test
+- `summer-parties`: playing together, the invite sheet
+- `summer-world-chat`: chat inside a match
+- `multiplayer-publish`: `summer.build.json` and publishing a Build
+- `multiplayer-testing`: what Local Play can and can't test

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

@@ -31,7 +31,7 @@ Under Local Play they fail with a typed code (step 5); the authority's
 degrade gracefully, and check the real numbers on a hosted staging build.
 
 This skill extends the Courtyard game: its authority concludes matches as in
-`skill/summer-match-results`.
+`summer-match-results`.
 
 ## Steps
 
@@ -104,7 +104,7 @@ func show_queue_board(queue: StringName) -> void:
   pending returns the same operation.
 
 After a match, `Summer.client.ratings.rating_committed` delivers the
-player's own before-and-after rating (see `skill/summer-match-results`).
+player's own before-and-after rating (see `summer-match-results`).
 
 ### 3. Write a Game ranking from the authority
 
@@ -136,7 +136,7 @@ func _add_score(ranking: StringName, player_id: String, points: int) -> void:
 ```
 
 `sessions` maps each `session_id` to the `SummerSession` the authority keeps
-in `_on_session_joined` (`skill/summer-match-results`, step 1). The engine never
+in `_on_session_joined` (`summer-match-results`, step 1). The engine never
 retries a write. After a failure other than a conflict, read the score before
 deciding to write again: the first write may have committed.
 
@@ -226,6 +226,6 @@ on them.
 
 ## See also
 
-- `skill/summer-match-results` — concluding matches, which moves ratings
-- `skill/summer-matchmaking` — declaring rated queues and teams
-- `skill/summer-player-data` — saving per-player progress that isn't a ranking
+- `summer-match-results` — concluding matches, which moves ratings
+- `summer-matchmaking` — declaring rated queues and teams
+- `summer-player-data` — saving per-player progress that isn't a ranking

package/library/skills/summer-match-results/SKILL.md

@@ -29,9 +29,9 @@ Where it works: all of this runs under Local Play with a deterministic
 settlement, so the whole flow is testable locally. Rating values are real only
 when hosted.
 
-This skill extends the Courtyard game (`skill/multiplayer-project` and
-`skill/multiplayer-state`): the first player to collect `WIN_COINS` coins wins.
-With a team queue (`skill/summer-matchmaking`), their whole team wins.
+This skill extends the Courtyard game (`multiplayer-project` and
+`multiplayer-state`): the first player to collect `WIN_COINS` coins wins.
+With a team queue (`summer-matchmaking`), their whole team wins.
 
 ## Steps
 
@@ -48,7 +48,7 @@ var sessions := {}      # session_id -> SummerSession
 ```
 
 In `_ready()`, next to the other World signals (skip this line if
-`skill/summer-player-data` already connected it):
+`summer-player-data` already connected it):
 
 ```gdscript
 	world.session_joined.connect(_on_session_joined)
@@ -61,7 +61,7 @@ func _on_session_joined(session: SummerSession) -> void:
 	sessions[session.session_id] = session
 ```
 
-If the game already has `_on_session_joined` (`skill/summer-player-data`
+If the game already has `_on_session_joined` (`summer-player-data`
 adds one), put the line at its start instead of defining it twice.
 
 At the top of `_on_session_left`:
@@ -159,7 +159,7 @@ The rules `conclude` enforces:
   refused. A rejected conclusion (`invalid_request`) commits nothing, so you
   may conclude again with corrected arguments.
 - `rating_deltas`, the third argument, is only for `authority_v1` queues
-  (`skill/summer-leaderboards`).
+  (`summer-leaderboards`).
 
 The settlement lists each player's committed rating changes:
 
@@ -205,7 +205,7 @@ func _on_server_disconnected(code: String, _detail: String) -> void:
 	show_status("The match has ended.")
 ```
 
-`show_status` and the `Hud/Status` label come from `skill/summer-matchmaking`.
+`show_status` and the `Hud/Status` label come from `summer-matchmaking`.
 
 - `match_result` arrives when the authority concludes. Its `rating_state` is
   `RATING_STATE_PENDING` on a rated queue, or `RATING_STATE_NONE`.
@@ -232,7 +232,7 @@ func _on_server_disconnected(code: String, _detail: String) -> void:
   `world.complete()` on a World that should keep running.
 - `draining(deadline_unix)` on the World means Summer is shutting the server
   down (maintenance). Conclude or save before the deadline
-  (`skill/summer-world-saves`).
+  (`summer-world-saves`).
 
 A match that never concludes holds its players until the World is stopped;
 every match needs an ending, including "everyone else left".
@@ -240,7 +240,7 @@ every match needs an ending, including "everyone else left".
 ### 5. Test it with Local Play
 
 ```
-summer_project_setting name="summer/local_play/players" value=2
+summer_project_setting key="summer/local_play/players" value=2
 summer_play
 summer_get_diagnostics
 summer_stop
@@ -280,7 +280,7 @@ clients stay connected until they leave.
 
 ## See also
 
-- `skill/summer-matchmaking` — queues and teams that the outcome refers to
-- `skill/summer-leaderboards` — ratings and `authority_v1` rating moves
-- `skill/summer-world-saves` — persistent Worlds that outlive a match
-- `skill/multiplayer-testing` — running bots through a whole match
+- `summer-matchmaking` — queues and teams that the outcome refers to
+- `summer-leaderboards` — ratings and `authority_v1` rating moves
+- `summer-world-saves` — persistent Worlds that outlive a match
+- `multiplayer-testing` — running bots through a whole match

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

@@ -20,7 +20,7 @@ groups searching players, reserves a server for them, and every player's
 The authority then reads each player's team from the verified Session.
 
 There is no lobby object, invite code or server browser. Friends who want to
-play together use a party (`skill/summer-parties`), which enters a queue as one group.
+play together use a party (`summer-parties`), which enters a queue as one group.
 
 Where it works:
 
@@ -31,8 +31,8 @@ Where it works:
 | Accept/Decline prompt | No: no proposal happens | Yes, when the queue declares `acceptance` |
 | Rating-based grouping | No | Yes |
 
-This skill extends the Courtyard game from `skill/multiplayer-project` and
-`skill/multiplayer-state`. Its client already joins `Game.QUEUE` and sends a
+This skill extends the Courtyard game from `multiplayer-project` and
+`multiplayer-state`. Its client already joins `Game.QUEUE` and sends a
 `join` Command; its authority publishes `match_doc`.
 
 ## Steps
@@ -64,7 +64,7 @@ The fields Summer accepts, and their rules:
 | `minPlayers` / `maxPlayers` | Players per match | `minPlayers` ≥ 1, `maxPlayers` ≥ `minPlayers`. Measured support is up to 16 per match |
 | `worldDefinition` | The WorldDefinition's `definition_id` | Required; every WorldDefinition must be used by a queue |
 | `policy` | `fifo` (first come) or `rating` (group by skill) | `rating` needs `ratingSystemRef`; `fifo` must not declare one |
-| `ratingSystemRef` | `elo_v1` (Summer rates two sides) or `authority_v1` (your authority reports rating moves) | See `skill/summer-leaderboards` |
+| `ratingSystemRef` | `elo_v1` (Summer rates two sides) or `authority_v1` (your authority reports rating moves) | See `summer-leaderboards` |
 | `teams` | `{count, size}`: fixed sides, such as 2v2 = `{2, 2}` | `count` 2..64, `size` 1..16, `minPlayers` = `maxPlayers` = count × size; `elo_v1` needs exactly 2 teams |
 | `acceptance` | `{"mode": "all", "ttl": "20s"}` asks every player to accept; `{"mode": "none"}` skips it | `ttl` required with `all`, forbidden with `none` |
 | `searchTtl` | `{min, default, max}` search lifetime | Go durations (`30s`, `2m`); min ≤ default ≤ max |
@@ -249,8 +249,8 @@ one you name. In the editor and with `summer_play`, name it with the
 `summer/local_play/queue` project setting:
 
 ```
-summer_project_setting name="summer/local_play/queue" value="duel"
-summer_project_setting name="summer/local_play/players" value=2
+summer_project_setting key="summer/local_play/queue" value="duel"
+summer_project_setting key="summer/local_play/players" value=2
 summer_play
 summer_get_diagnostics
 summer_stop
@@ -294,8 +294,8 @@ Test the accept prompt and rating-based grouping on a hosted staging build.
 
 ## See also
 
-- `skill/multiplayer` — how Summer multiplayer fits together
-- `skill/summer-match-results` — ending a match and reporting who won
-- `skill/summer-leaderboards` — ratings and leaderboards for rated queues
-- `skill/summer-parties` — friends entering a queue together
-- `skill/multiplayer-testing` — Local Play options and bots
+- `multiplayer` — how Summer multiplayer fits together
+- `summer-match-results` — ending a match and reporting who won
+- `summer-leaderboards` — ratings and leaderboards for rated queues
+- `summer-parties` — friends entering a queue together
+- `multiplayer-testing` — Local Play options and bots

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

@@ -39,7 +39,7 @@ Outside a party, or when parties are unavailable, getters are empty and
 `is_in_party()` is `false`. So the same Play button works everywhere: no party
 means an ordinary `SummerJoinTarget.queue(...)` join. Build that path first.
 
-This skill extends the Courtyard game from `skill/multiplayer-project`
+This skill extends the Courtyard game from `multiplayer-project`
 (`network/game.gd` as `Game`, `client/main.gd` with `command()`).
 
 ## Steps
@@ -48,7 +48,7 @@ This skill extends the Courtyard game from `skill/multiplayer-project`
 
 A party member must not join on their own the moment the game starts. Move the
 join out of `client/main.gd`'s `_ready` into `enter(target)`, and keep every
-signal connection from `skill/multiplayer-movement` and `skill/multiplayer-state`:
+signal connection from `multiplayer-movement` and `multiplayer-state`:
 
 ```gdscript
 func _ready() -> void:
@@ -87,7 +87,7 @@ func enter(target: SummerJoinTarget) -> bool:
 	return true
 ```
 
-Move the Local Play bot hook from `skill/multiplayer-testing` into `enter()`,
+Move the Local Play bot hook from `multiplayer-testing` into `enter()`,
 after the joined line.
 
 ### 2. Add the party node
@@ -193,7 +193,7 @@ fails with retryable `party_version_conflict`. React to `data_changed(key)` and
 `member_data_changed(member, key)`, or just re-render on `changed`.
 
 Party data is a lobby convenience, not game state. Once the match starts, the
-authority owns everything (`skill/multiplayer-state`). It never sees party data;
+authority owns everything (`multiplayer-state`). It never sees party data;
 send choices that matter in your `join` Command and validate them there.
 
 ### 4. Handle join failures
@@ -217,7 +217,7 @@ client joins solo from `_ready`. Test that path locally, then the party path
 on Summer staging with real accounts.
 
 ```
-summer_project_setting name="summer/local_play/players" value=2
+summer_project_setting key="summer/local_play/players" value=2
 summer_play
 summer_get_diagnostics
 summer_stop
@@ -247,7 +247,7 @@ summer_stop
 
 ## See also
 
-- `skill/summer-matchmaking`: queues, sizes, teams and the accept prompt
-- `skill/summer-friends`: friends list, profiles and messages
-- `skill/multiplayer-project`: the client entry scene this extends
-- `skill/multiplayer-testing`: Local Play, and what needs staging
+- `summer-matchmaking`: queues, sizes, teams and the accept prompt
+- `summer-friends`: friends list, profiles and messages
+- `multiplayer-project`: the client entry scene this extends
+- `multiplayer-testing`: Local Play, and what needs staging

package/library/skills/summer-player-data/SKILL.md

@@ -39,8 +39,8 @@ Local Play's store keeps the latest value plus five earlier revisions, with
 the same validation and `save_id` rules as hosted. Delete a persona's folder
 to start that player fresh. Only hosted play proves durability.
 
-This skill extends the game from `skill/multiplayer-project` and
-`skill/multiplayer-state`: the authority's `_join` Command handler, the
+This skill extends the game from `multiplayer-project` and
+`multiplayer-state`: the authority's `_join` Command handler, the
 private `mine` State group, and the `wallets` it keeps.
 
 ## Steps
@@ -70,7 +70,7 @@ var profiles := {}
 ```
 
 In `_ready()`, next to the other `world` signals, before `Summer.initialize`
-(connect `session_joined` only once if `skill/summer-match-results` already
+(connect `session_joined` only once if `summer-match-results` already
 did):
 
 ```gdscript
@@ -83,7 +83,7 @@ did):
 	autosave.start()
 ```
 
-If `_on_session_joined` already exists (`skill/summer-match-results` adds
+If `_on_session_joined` already exists (`summer-match-results` adds
 one), put this body at its end instead of defining it twice.
 
 ```gdscript
@@ -254,7 +254,7 @@ func _show_saved_progress() -> void:
 
 ### 6. Keep the publish checks passing
 
-The source-graph check in `skill/multiplayer-publish` (step 4b) flags every
+The source-graph check in `multiplayer-publish` (step 4b) flags every
 call ending in `load(` without a string literal inside, so
 `Summer.authority.player_data.load(session)` and
 `Summer.client.player_data.load()` report
@@ -274,7 +274,7 @@ Run the same session twice. Local Play personas (`player-1`, `player-2`)
 keep their files between runs, so run 2 must start where run 1 ended.
 
 ```
-summer_project_setting name="summer/local_play/players" value=2
+summer_project_setting key="summer/local_play/players" value=2
 summer_play
 summer_get_diagnostics
 summer_stop
@@ -284,7 +284,7 @@ summer_stop
 ```
 
 From a terminal: `<summer> --path . --summer-local-play 2 --summer-local-play-headless --summer-local-play-timeout 20 -- --bot={client}`,
-twice (see `skill/multiplayer-testing` for bot mode). Print markers such as
+twice (see `multiplayer-testing` for bot mode). Print markers such as
 `print("PROFILE_LOADED coins=", ...)` and `print("SAVED ", save_id, " revision=", commit.revision)` while testing, then check them.
 
 Files: `~/Library/Application Support/Godot/app_userdata/<project name>/summer_local_player_data/<game id>/<persona>/public.json`
@@ -311,12 +311,12 @@ folder to start over.
 | Start a second commit while one is pending | One commit per player and slot at a time | The second fails with `operation_in_progress` |
 | Keep retrying after `player_data_superseded` | Stop saving through that Session | A newer World owns the player now |
 | Store `Vector3`, `Color` or `null` | Plain JSON: numbers, strings, arrays, dictionaries | Unsupported types fail with `player_data_unsupported_type` |
-| Save the match (positions, round score) | Save only what outlives the match | The World ends; `skill/summer-world-saves` covers Worlds that persist |
+| Save the match (positions, round score) | Save only what outlives the match | The World ends; `summer-world-saves` covers Worlds that persist |
 | Truncate data that grew past 64 KiB | Refuse to grow; test the maximum size | `player_data_too_large` rejects the whole commit |
 
 ## See also
 
-- `skill/multiplayer-state` — the wallet and private State group this skill saves
-- `skill/summer-world-saves` — saving a whole persistent World instead of one player
-- `skill/multiplayer-testing` — bots and repeated Local Play runs
-- `skill/summer-leaderboards` — scores other players can see
+- `multiplayer-state` — the wallet and private State group this skill saves
+- `summer-world-saves` — saving a whole persistent World instead of one player
+- `multiplayer-testing` — bots and repeated Local Play runs
+- `summer-leaderboards` — scores other players can see

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

@@ -45,8 +45,8 @@ proves nothing.
 Items and offers are created in your game's Studio pages (`summer_open` target
 `game`). Code never creates items.
 
-This skill extends the Courtyard game from `skill/multiplayer-project` and
-`skill/multiplayer-state`.
+This skill extends the Courtyard game from `multiplayer-project` and
+`multiplayer-state`.
 
 ## Steps
 
@@ -265,7 +265,7 @@ Walk through every outcome:
 
 ## See also
 
-- `skill/multiplayer-state`: Commands and the match document used for equipped items
-- `skill/multiplayer-testing`: Local Play fixtures and personas
-- `skill/summer-player-data`: saving a player's loadout between matches
-- `skill/summer-analytics`: measuring the shop
+- `multiplayer-state`: Commands and the match document used for equipped items
+- `multiplayer-testing`: Local Play fixtures and personas
+- `summer-player-data`: saving a player's loadout between matches
+- `summer-analytics`: measuring the shop

package/library/skills/summer-world-chat/SKILL.md

@@ -32,7 +32,7 @@ composition, and the authority neither sees nor writes them.
 | Channel keys | 1–64 of `A-Z a-z 0-9 _ . -`, starting with a letter or digit; at most 64 channels per World |
 | History | Best effort, not a full log. A new handle shows the newest 2 messages; `load_older()` grows the window to at most 16 |
 | Lifetime | A handle belongs to one World admission. After leaving or joining another World, open a new one |
-| Not included | Direct messages (`skill/summer-friends`), party chat (the Summer app) and messages written by your server |
+| Not included | Direct messages (`summer-friends`), party chat (the Summer app) and messages written by your server |
 
 **Hosted only.** Chat needs a joined hosted World and a Summer app whose Player
 Host offers `player.channels`. A queue reservation is not enough: open the
@@ -40,8 +40,8 @@ channel after `enter()` succeeds. In Local Play and editor runs,
 `check_open_readiness()` and `open_world_channel()` fail with `unavailable`.
 Build the "chat hidden" path first.
 
-This skill extends the Courtyard game from `skill/multiplayer-project` and
-`skill/multiplayer-state`.
+This skill extends the Courtyard game from `multiplayer-project` and
+`multiplayer-state`.
 
 ## Steps
 
@@ -49,7 +49,7 @@ This skill extends the Courtyard game from `skill/multiplayer-project` and
 
 Messages carry the author's Summer user id (`player_id`), not a name. The
 authority already knows every verified name. Publish them in the shared match
-document (`skill/multiplayer-state`): in `authority/main.gd`'s `_join`, before
+document (`multiplayer-state`): in `authority/main.gd`'s `_join`, before
 accepting, add
 
 ```gdscript
@@ -158,7 +158,7 @@ Call `$Chat.open()` after `enter()` returns `true`. Wire it into the UI:
 Locally, check that the hidden path works and nothing errors:
 
 ```
-summer_project_setting name="summer/local_play/players" value=2
+summer_project_setting key="summer/local_play/players" value=2
 summer_play
 summer_get_diagnostics
 summer_stop
@@ -189,7 +189,7 @@ Then test real chat on Summer staging with two accounts in one match.
 
 ## See also
 
-- `skill/multiplayer-state`: the match document that carries player names
-- `skill/summer-friends`: direct messages with friends
-- `skill/summer-parties`: party chat lives in the Summer app
-- `skill/multiplayer-testing`: what Local Play can and can't test
+- `multiplayer-state`: the match document that carries player names
+- `summer-friends`: direct messages with friends
+- `summer-parties`: party chat lives in the Summer app
+- `multiplayer-testing`: what Local Play can and can't test