juicyjuicy 0.15.0 → 0.16.0

package/dist/index.js

@@ -19807,7 +19807,7 @@ function date4(params) {
 }
 
 // ../shared/src/cli.ts
-var CLI_RELEASE = "0.15.0";
+var CLI_RELEASE = "0.16.0";
 function cliCommand(args) {
   return `npx -y juicyjuicy@${CLI_RELEASE} ${args}`;
 }
@@ -19924,7 +19924,7 @@ var LIMITS = {
 var PUBLISH_LIMIT_WINDOW_HOURS = 24;
 var RATE_LIMITS = {
   /** New accounts, site-wide. */
-  signUp: { limit: 30, windowSeconds: 60 * 60 },
+  signUp: { limit: 60, windowSeconds: 60 * 60 },
   /** New accounts per client IP (hashed). */
   signUpNetwork: { limit: 3, windowSeconds: 24 * 60 * 60 },
   /** Verification and password-reset mails per address (D88), keyed by a hash of it. */
@@ -20012,6 +20012,16 @@ var UPLOAD_BUDGET = {
   /** Files one member may upload in the last 24 hours: 5 publishes at `LIMITS.maxFiles`. */
   memberFilesPerDay: 15e3
 };
+var PROVIDER_ALLOWANCES = {
+  /** Neon Free: past it the compute is suspended until the next billing period. */
+  neonComputeHoursPerMonth: 100,
+  /** Neon Free: past it writes fail. */
+  neonStorageBytes: 1024 * MB,
+  /** Neon Free: past it the compute is suspended, as for CU-hours. */
+  neonEgressBytesPerMonth: 5 * 1024 * MB,
+  /** Cloudflare Email Service on Workers Paid; past it $0.35 per 1,000. */
+  mailIncludedPerMonth: 3e3
+};
 var THUMBNAIL_EXTENSIONS = ["png", "jpg", "jpeg", "webp"];
 
 // ../shared/src/genres.ts
@@ -20774,14 +20784,14 @@ var GAME_FEATURES = [
   },
   {
     id: "touch",
-    name: "Touch controls",
-    summary: "The game plays on phones and tablets, with on-screen controls or taps and swipes.",
-    adds: "On-screen controls, or taps and swipes, so the game plays on phones and tablets.",
-    why: "Many players open links on their phone; without touch they can only watch.",
-    detection: { kind: "declared", input: "touch" },
+    name: "Mobile optimization",
+    summary: "The game plays well on phones and tablets: touch controls, screen fit, sound, speed.",
+    adds: "Touch controls that fit the game, a layout that fits a phone screen in either orientation and survives rotating, menus that work by tap, and sound and speed that work on phones.",
+    why: "Many players open links on their phone; without this they may only be able to watch, or get a game that's cut off, tiny or silent.",
+    detection: { kind: "declared", input: "touch", addUntilDeclared: true },
     status: "available",
     recipe: "reference/touch.md",
-    task: "add touch controls so the game plays on phones and tablets",
+    task: "optimize the game for mobile so it plays well on phones and tablets: touch controls, screen fit in both orientations, sound and speed",
     docs: "/docs/publish#touch"
   },
   {
@@ -20796,18 +20806,6 @@ var GAME_FEATURES = [
     task: "add gamepad support so the game plays with a controller",
     docs: "/docs/publish#gamepad"
   },
-  {
-    id: "mouse-lock",
-    name: "Mouse lock",
-    summary: "Aiming or steering with the mouse keeps the cursor in the game.",
-    adds: "Games that aim or steer with the mouse lock the cursor (Pointer Lock), so it can't leave the game.",
-    why: "Without it, turning fast drags the cursor out of the frame or onto another screen, and the game stops responding.",
-    detection: { kind: "declared" },
-    status: "available",
-    recipe: "reference/mouse-lock.md",
-    task: "add mouse lock so aiming or steering with the mouse keeps the cursor in the game",
-    docs: "/docs/publish#mouse-lock"
-  },
   {
     id: "auto-pause",
     name: "Auto-pause",
@@ -20821,6 +20819,7 @@ var GAME_FEATURES = [
     docs: "/docs/publish#auto-pause"
   }
 ];
+var RETIRED_FEATURES = ["mouse-lock"];
 function gameFeature(id) {
   return GAME_FEATURES.find((feature) => feature.id === id);
 }
@@ -20850,9 +20849,9 @@ function featureState(feature, input2) {
       };
     }
     case "declared": {
-      const { input: inputKind } = feature.detection;
+      const { input: inputKind, addUntilDeclared } = feature.detection;
       if (inputKind && input2.input?.includes(inputKind)) {
-        return { feature, status: "on", canAdd: false };
+        return { feature, status: "on", canAdd: Boolean(addUntilDeclared) && !declared };
       }
       if (input2.declared === null) return { feature, status: "unknown", canAdd: false };
       return { feature, status: declared ? "on" : "off", canAdd: !declared };
@@ -20867,6 +20866,7 @@ function featureState(feature, input2) {
 function featureFindings(input2) {
   const findings = [];
   for (const id of input2.declared) {
+    if (RETIRED_FEATURES.includes(id)) continue;
     const feature = gameFeature(id);
     if (!feature) {
       findings.push({
@@ -27792,7 +27792,7 @@ var program = new Command();
 // package.json
 var package_default = {
   name: "juicyjuicy",
-  version: "0.15.0",
+  version: "0.16.0",
   description: "Publish AI-made browser games to juicyjuicy.games",
   type: "module",
   license: "MIT",
@@ -27882,6 +27882,14 @@ The sign-in page says why and how to contest it.`;
 It won't be shown. Upload a different image to replace it.`;
     case "profile_moderated":
       return `JuicyJuicy's moderators removed ${note.subject ?? "something from your profile"}:${quoted(note.comment)}`;
+    // Only the site's banner shows these (D108); a publish never sends them.
+    case "version_held":
+    case "report_held":
+    case "image_held":
+    case "score_removed":
+    case "account_changed":
+    case "game_edited":
+      return `A notice about ${game} is waiting on the JuicyJuicy site:${quoted(note.comment ?? "see the banner there")}`;
   }
 }
 function noteMessages(moderation, warnings, slug) {

package/dist/skill/SKILL.md

@@ -9,22 +9,22 @@ JuicyJuicy hosts **static browser games** (HTML/JS/CSS/assets, WebAssembly) and
 
 Run every CLI command with `--json`. Each output line is a JSON object; the **last** line is the result, either `{"ok": true, …}` or `{"ok": false, "error": {"code", "message", "details"?, "hint"?}}`. The exit code is `0` (ok), `1` (fix the game or `juicy.json`), `2` (log in) or `3` (network or server problem, so retry).
 
-Run the CLI exactly as written here, `npx -y juicyjuicy@0.15.0 …`: this skill is made for that release. If JuicyJuicy answers that the CLI is out of date, run the command its message gives. It updates the CLI and this skill together; read this skill again afterwards and use the release it names from then on.
+Run the CLI exactly as written here, `npx -y juicyjuicy@0.16.0 …`: this skill is made for that release. If JuicyJuicy answers that the CLI is out of date, run the command its message gives. It updates the CLI and this skill together; read this skill again afterwards and use the release it names from then on.
 
 ## Procedure
 
 ### 1. Make sure the CLI is logged in
 
 ```bash
-npx -y juicyjuicy@0.15.0 whoami --json
+npx -y juicyjuicy@0.16.0 whoami --json
 ```
 
 If it exits with `2`, log in. `login` opens the user's browser and **waits up to 10 minutes** for them to approve:
 
-- Run `npx -y juicyjuicy@0.15.0 login --json` in the background if your shell can, and read its first output line (`{"event": "device_code", "userCode", "verificationUrl"}`) right away, and show the user the code and link without waiting for them to ask: the page shows the same code, and that's how they know the login is theirs.
+- Run `npx -y juicyjuicy@0.16.0 login --json` in the background if your shell can, and read its first output line (`{"event": "device_code", "userCode", "verificationUrl"}`) right away, and show the user the code and link without waiting for them to ask: the page shows the same code, and that's how they know the login is theirs.
 - Then tell the user, with the real code and link: *"A JuicyJuicy page opened in your browser. Check it shows the code **WXTZ-BCDF** and click **Approve**. If no page opened, go to <verificationUrl>."*
 - If your shell can't run commands in the background, say that first (without a code: it doesn't exist yet), then run it in the foreground with a timeout of at least 10 minutes. The code is also printed as `Your code: …`.
-- The user needs a JuicyJuicy account (it's invite-only for now). If the page says they can't sign in, they need an invite link from a friend who's a member.
+- The user needs a JuicyJuicy account. If they don't have one yet, they can make one on the sign-in page that opens.
 
 In CI there's no browser: the `JUICY_TOKEN` environment variable holds a token instead.
 
@@ -45,7 +45,7 @@ Files and folders starting with `.` (`.env`, `.git/`, …) and `node_modules/` a
 `juicy.json` sits in the project folder and describes the game. Create or update it with `init`, filling in what you know from the game you built:
 
 ```bash
-npx -y juicyjuicy@0.15.0 init --yes --json \
+npx -y juicyjuicy@0.16.0 init --yes --json \
   --title "Snake Deluxe" \
   --description "Eat the apples, don't bite your tail. Arrow keys or swipe." \
   --made-with "<your model name>, <the tool you run in>" \
@@ -127,7 +127,7 @@ To replace it, the user saves a screenshot as `thumbnail.png` in the project fol
 
 Do this **every time**, also for updates. It protects the user and their players; JuicyJuicy's server runs its own checks as well, so this is help, not a formality to get past.
 
-1. **Check.** Run `npx -y juicyjuicy@0.15.0 check --json`. Errors (a failed result) must be fixed: explain each one (`details` has a `rule` and a `path`), and offer to fix it. If the user says no, **stop and don't publish**: the server would refuse it anyway. Warnings in the result (`findings`) go into step 2.
+1. **Check.** Run `npx -y juicyjuicy@0.16.0 check --json`. Errors (a failed result) must be fixed: explain each one (`details` has a `rule` and a `path`), and offer to fix it. If the user says no, **stop and don't publish**: the server would refuse it anyway. Warnings in the result (`findings`) go into step 2.
    Every file in the result's `files` will be public. If `unusualFiles` isn't empty (names that look like keys or private data, project files like `package.json`, notes and other files a web game doesn't load), **show the user that list and ask whether those files should be public** before publishing; offer to move them out of the build folder or set `buildDir` to a folder with just the game.
 2. **Security review.** Follow [reference/review.md](reference/review.md): keys and tokens, `innerHTML`/`eval` on network or multiplayer data, `http://` loads, trackers, login or payment forms, anything that leaves the page. Same rule: for what it marks as must-fix, fix it or don't publish.
 3. **Standards.** Check the game against these and tell the user, in a sentence or two, what falls short; offer to fix it. A "no" still publishes: not every game can have touch controls.
@@ -142,7 +142,7 @@ Do this **every time**, also for updates. It protects the user and their players
    - Saves progress with JuicyJuicy's window.juicy snippet, if it saves at all, so it follows signed-in players to any browser (not cookies: the play domain clears them).
    - A Quit or Exit button, if it has one, sends JuicyJuicy's quit message instead of calling window.close().
 
-   The game runs in a frame on JuicyJuicy, inside a page. The frame can start at 0×0 or be hidden: when `innerWidth` or `innerHeight` is 0, pause and wait for a `resize` instead of restarting, and give every loop that searches (a free cell for food, a spawn point) a way out. A game stuck in a loop stops every other game in the player's tab from loading. Mouse events stop when the cursor leaves the frame: call `canvas.setPointerCapture(event.pointerId)` on `pointerdown` so a drag keeps getting `pointermove` and `pointerup` outside it. A game that aims or steers with the mouse (a shooter, a camera, a racer) calls `canvas.requestPointerLock()` on a click and reads `event.movementX`/`movementY`: the cursor hides and can't leave the game, not even onto a second screen in fullscreen, and Esc gives it back. Ask for the lock again on the next click.
+   The game runs in a frame on JuicyJuicy, inside a page. The frame can start at 0×0 or be hidden: when `innerWidth` or `innerHeight` is 0, pause and wait for a `resize` instead of restarting, and give every loop that searches (a free cell for food, a spawn point) a way out. A game stuck in a loop stops every other game in the player's tab from loading. Mouse events stop when the cursor leaves the frame: call `canvas.setPointerCapture(event.pointerId)` on `pointerdown` so a drag keeps getting `pointermove` and `pointerup` outside it. A game that aims or steers with the mouse (a shooter, a camera, a racer) calls `canvas.requestPointerLock()` on a click and reads `event.movementX`/`movementY`: the cursor hides and can't leave the game, not even onto a second screen in fullscreen, and Esc gives it back. Ask for the lock again on the next click. [reference/mouse-lock.md](reference/mouse-lock.md) has the whole recipe (pausing when the lock ends, menus, engines).
 
    Esc belongs to the browser: it leaves fullscreen and Pointer Lock before the game sees it. `navigator.keyboard.lock()`, which hands Esc to a page in fullscreen, fails inside a frame, so don't rely on Esc alone: give pause or the menu another key too (like P).
 
@@ -156,7 +156,7 @@ Keep it short when there's nothing to say: "Checked: no problems found" is enoug
 ### 6. Publish
 
 ```bash
-npx -y juicyjuicy@0.15.0 publish --json --message "<what changed, in a few words>"
+npx -y juicyjuicy@0.16.0 publish --json --message "<what changed, in a few words>"
 ```
 
 This makes the new version live: when the user says "publish", that's what they want. Don't add `--draft` (see "Other commands") unless they asked in words for it not to go live yet. Not for a first publish, a big game or one you're unsure of either: the user would have to find the dashboard and make it live themselves.
@@ -186,14 +186,13 @@ The game's page under My games on JuicyJuicy has an **Upgrades** panel; its Add
 | Cloud saves | [reference/cloud-saves.md](reference/cloud-saves.md) | `"features": ["cloud-saves"]` |
 | Gamepad support | [reference/gamepad.md](reference/gamepad.md) | `"input": [… "gamepad"]` and `"features": ["gamepad"]` |
 | Global highscores | [reference/highscores.md](reference/highscores.md) | `"features": ["highscores"]` |
-| Mouse lock | [reference/mouse-lock.md](reference/mouse-lock.md) | `"features": ["mouse-lock"]` |
+| Mobile optimization | [reference/touch.md](reference/touch.md) | `"input": [… "touch"]` and `"features": ["touch"]` |
 | Multi-language | [reference/languages.md](reference/languages.md) | `"languages": ["en", …]` |
 | Multiplayer | [reference/multiplayer.md](reference/multiplayer.md) | `"features": ["multiplayer"]` |
-| Touch controls | [reference/touch.md](reference/touch.md) | `"input": [… "touch"]` and `"features": ["touch"]` |
 
 An upgrade that doesn't fit the game (mouse lock for a game played by clicking, auto-pause for a turn-based one) is the recipe's to say: tell the user why, and change nothing unless they still want it.
 
-1. **Find the project.** Log in first (step 1). The project is the folder whose `juicy.json` has the game's `slug`: the current folder, or one the user points you to. **If it isn't on this computer** (or you're in a chat app or sandbox), download the live version: `npx -y juicyjuicy@0.15.0 pull <slug> --json` writes it into a new folder named after the slug (`dir` in the result) with its `juicy.json`, and you work there. Read the result's `next`: the download is the built game, so for a bundled one (minified code), ask whether the user has the source somewhere, or use `sourceUrl`, before changing the bundle itself. `pull` only works for the user's own games (`NOT_FOUND` otherwise).
+1. **Find the project.** Log in first (step 1). The project is the folder whose `juicy.json` has the game's `slug`: the current folder, or one the user points you to. **If it isn't on this computer** (or you're in a chat app or sandbox), download the live version: `npx -y juicyjuicy@0.16.0 pull <slug> --json` writes it into a new folder named after the slug (`dir` in the result) with its `juicy.json`, and you work there. Read the result's `next`: the download is the built game, so for a bundled one (minified code), ask whether the user has the source somewhere, or use `sourceUrl`, before changing the bundle itself. `pull` only works for the user's own games (`NOT_FOUND` otherwise).
 2. **Read the recipe** for the upgrade and make the change. Keep everything else about the game as it is.
 3. **Build and try it** (step 2), then **declare it** in `juicy.json` as the table says, adding to what's already listed.
 4. **Review and publish** as steps 5–7 say, with `--message "Add <upgrade>"`. In step 5's `check` result, `features.detected` lists what JuicyJuicy found in the files; a `feature-missing` warning means a declared upgrade isn't there yet: fix it before publishing.
@@ -201,14 +200,14 @@ An upgrade that doesn't fit the game (mouse lock for a game played by clicking,
 
 ## Bring all my games up to date
 
-When the user asks to bring their JuicyJuicy games up to date or fix a **Needs update** badge, when `check` or `publish` warns `requirement-missing`, or after updating the CLI: follow [reference/update-all-games.md](reference/update-all-games.md). It starts with `npx -y juicyjuicy@0.15.0 check-games --json`, which checks every game of the user's at once and settles what a script can; the rest are code changes, one game at a time.
+When the user asks to bring their JuicyJuicy games up to date or fix a **Needs update** badge, when `check` or `publish` warns `requirement-missing`, or after updating the CLI: follow [reference/update-all-games.md](reference/update-all-games.md). It starts with `npx -y juicyjuicy@0.16.0 check-games --json`, which checks every game of the user's at once and settles what a script can; the rest are code changes, one game at a time.
 
 ## Remix a game
 
 A game marked remixable on JuicyJuicy can be downloaded, changed and published as a new game that links back to it. Log in first (step 1), then:
 
 ```bash
-npx -y juicyjuicy@0.15.0 remix <slug> --json
+npx -y juicyjuicy@0.16.0 remix <slug> --json
 ```
 
 - The first line is `{"event": "license", "name", "text"}`: the remix license. Tell the user in a sentence what it says. In short: the remix may be published **on JuicyJuicy only**, never anywhere else, and the files aren't to be passed on. The full text is:
@@ -244,10 +243,10 @@ Everything else is in [reference/troubleshooting.md](reference/troubleshooting.m
 
 ## Other commands
 
-- `npx -y juicyjuicy@0.15.0 list --json`: the user's games; `list <slug>` shows one game's versions. `--all` lists every game on JuicyJuicy instead (60 a page, `--page 2` and on; `nextPage` in the result), `--owner <username>` another creator's. Narrow and order any list with `--search <title text>`, `--genre` (one of the genre ids above, or several: `board,cards-casino`), `--tag` (a theme), `--engine`, `--remixes`, `--multiplayer` (games with rooms), `--highscores` (games with a leaderboard), `--sort newest|upvoted|downvoted|played` and `--period 24h|week|month|all`, e.g. to find a game to remix.
-- `npx -y juicyjuicy@0.15.0 publish --draft --json`: uploads a new version without making it live (players keep the current one). Only when the user asks for that in words (e.g. "upload it but don't put it live yet"), never on your own judgment. The result has `draft: true`; when they say so, make it live with `go-live`, or they can on the dashboard. Only the newest draft can go live.
-- `npx -y juicyjuicy@0.15.0 go-live --slug <slug> --json`: makes the game's newest draft live, only when the user says so. Pass the draft's number (`go-live <version>`) when they named one, so a newer draft never goes live by surprise. A draft waiting for an admin's review can't go live yet (`FORBIDDEN`), and nor can one a moderator rejected (`VERSION_REJECTED`) or asked changes to (`CHANGES_REQUESTED`). There's no command to go back to an earlier version: when the user asks for one, explain that JuicyJuicy doesn't keep version history, and offer to fix the game or publish their own earlier files as a new version.
-- `npx -y juicyjuicy@0.15.0 recheck <slug> --reply "<what changed>" --json`: asks JuicyJuicy's moderators for another look at a game they blocked, once the user fixed it (see [reference/moderation.md](reference/moderation.md)). Only with the user's OK.
-- `npx -y juicyjuicy@0.15.0 pull <slug> --json`: downloads the live version of one of the user's own games into a new folder with its `juicy.json`, to change it when the project isn't on this computer (see "Add a JuicyJuicy upgrade").
-- `npx -y juicyjuicy@0.15.0 check-games --json`: checks all the user's games against JuicyJuicy's features and required updates, declares the features it finds where a game never declared them, and lists what still needs a change (see "Bring all my games up to date").
-- `npx -y juicyjuicy@0.15.0 open <slug>`: opens the game page in the browser.
+- `npx -y juicyjuicy@0.16.0 list --json`: the user's games; `list <slug>` shows one game's versions. `--all` lists every game on JuicyJuicy instead (60 a page, `--page 2` and on; `nextPage` in the result), `--owner <username>` another creator's. Narrow and order any list with `--search <title text>`, `--genre` (one of the genre ids above, or several: `board,cards-casino`), `--tag` (a theme), `--engine`, `--remixes`, `--multiplayer` (games with rooms), `--highscores` (games with a leaderboard), `--sort newest|upvoted|downvoted|played` and `--period 24h|week|month|all`, e.g. to find a game to remix.
+- `npx -y juicyjuicy@0.16.0 publish --draft --json`: uploads a new version without making it live (players keep the current one). Only when the user asks for that in words (e.g. "upload it but don't put it live yet"), never on your own judgment. The result has `draft: true`; when they say so, make it live with `go-live`, or they can on the dashboard. Only the newest draft can go live.
+- `npx -y juicyjuicy@0.16.0 go-live --slug <slug> --json`: makes the game's newest draft live, only when the user says so. Pass the draft's number (`go-live <version>`) when they named one, so a newer draft never goes live by surprise. A draft waiting for an admin's review can't go live yet (`FORBIDDEN`), and nor can one a moderator rejected (`VERSION_REJECTED`) or asked changes to (`CHANGES_REQUESTED`). There's no command to go back to an earlier version: when the user asks for one, explain that JuicyJuicy doesn't keep version history, and offer to fix the game or publish their own earlier files as a new version.
+- `npx -y juicyjuicy@0.16.0 recheck <slug> --reply "<what changed>" --json`: asks JuicyJuicy's moderators for another look at a game they blocked, once the user fixed it (see [reference/moderation.md](reference/moderation.md)). Only with the user's OK.
+- `npx -y juicyjuicy@0.16.0 pull <slug> --json`: downloads the live version of one of the user's own games into a new folder with its `juicy.json`, to change it when the project isn't on this computer (see "Add a JuicyJuicy upgrade").
+- `npx -y juicyjuicy@0.16.0 check-games --json`: checks all the user's games against JuicyJuicy's features and required updates, declares the features it finds where a game never declared them, and lists what still needs a change (see "Bring all my games up to date").
+- `npx -y juicyjuicy@0.16.0 open <slug>`: opens the game page in the browser.

package/dist/skill/reference/languages.md

@@ -16,4 +16,4 @@ JuicyJuicy offers English, French, Italian, German, Spanish and Polish (`en`, `f
 Run the game, switch to each language and go through the menus and the first minute of play: no missing keys (an untranslated key shows up as the key's name), no clipped text, and the choice is still there after a reload.
 
 ## Declare it
-Set `languages` in `juicy.json` to every language the game now has, English first, e.g. `"languages": ["en", "fr", "pl"]` (or `npx -y juicyjuicy@0.15.0 init --yes --json --languages en,fr,pl`). Don't add it to `features`: JuicyJuicy reads `languages`, and shows the game in each language's filter.
+Set `languages` in `juicy.json` to every language the game now has, English first, e.g. `"languages": ["en", "fr", "pl"]` (or `npx -y juicyjuicy@0.16.0 init --yes --json --languages en,fr,pl`). Don't add it to `features`: JuicyJuicy reads `languages`, and shows the game in each language's filter.

package/dist/skill/reference/manifest.md

@@ -40,7 +40,7 @@ The manifest in the project folder. `juicyjuicy init` writes it; edit it by hand
 | `tags` | | Themes: up to 3 lowercase words or `word-word` for the setting or subject, e.g. `space`, `pirates`, `blackjack`. Not genres or features (touch, remixable: JuicyJuicy shows those by itself), except `multiplayer`, not counted among the 3, for a game players play together without JuicyJuicy's rooms (its own netcode, or one screen). JuicyJuicy cleans them up when saving (spellings fixed, `co-op`, `pvp` and the like saved as `multiplayer`, genre and other feature words moved out, at most 3 themes kept; `check` warns with what it will save). | `--tags a,b` |
 | `ageRating` | | Who the game is for: `everyone`, `12+` or `16+`, from its content (SKILL.md step 3 says how to pick). Rate every game you publish. Left out, a publish keeps the game's rating; a rating set by JuicyJuicy's moderators wins over this one, and `publish` writes it here. | `--age-rating` |
 | `languages` | | Up to 10 language codes a player can switch between, English first, e.g. `["en", "pl"]`. Default `["en"]`. Shown as a language filter on JuicyJuicy. | `--languages a,b` |
-| `features` | yes | The JuicyJuicy upgrades the game has, by id: `auto-pause`, `browser-menu`, `cloud-saves`, `gamepad`, `highscores`, `mouse-lock`, `multiplayer`, `touch`; `[]` for none. Required: `check` and `publish` stop without it, and `init` adds `[]`. Add an id only once the game has the feature (see SKILL.md, "Add a JuicyJuicy upgrade"); `check` warns when one is listed but missing. Multi-language is `languages`, not a feature id; `touch` and `gamepad` go in `input` too. | |
+| `features` | yes | The JuicyJuicy upgrades the game has, by id: `auto-pause`, `browser-menu`, `cloud-saves`, `gamepad`, `highscores`, `multiplayer`, `touch`; `[]` for none. Required: `check` and `publish` stop without it, and `init` adds `[]`. Add an id only once the game has the feature (see SKILL.md, "Add a JuicyJuicy upgrade"); `check` warns when one is listed but missing. Multi-language is `languages`, not a feature id; `touch` and `gamepad` go in `input` too. | |
 | `input` | | Any of `keyboard`, `mouse`, `touch`, `gamepad`. | `--input a,b` |
 | `orientation` | | `landscape`, `portrait` or `any` (default). | `--orientation` |
 | `aspectRatio` | | `"W:H"` like `"16:9"` or `"4:3"`, or `"fill"` to fill the player. Default `16:9`. | `--aspect-ratio` |

package/dist/skill/reference/moderation.md

@@ -25,7 +25,7 @@ JuicyJuicy's moderators (its admins) can leave the user a written comment about
    - after a change request or a rejection: run the review steps and publish a new version (`publish --json`, with a `--message` that says what changed). Tell the user it goes through the safety check again and may wait for a moderator.
    - after a block: publish if the game's files changed (a new title or description in `juicy.json` also goes out with a publish), then ask for another look:
      ```bash
-     npx -y juicyjuicy@0.15.0 recheck <slug> --reply "<what the user changed, in their words>" --json
+     npx -y juicyjuicy@0.16.0 recheck <slug> --reply "<what the user changed, in their words>" --json
      ```
      The game stays unlisted until an admin lists it again; tell the user that. Write the reply with the user, and keep it to what was changed.
 4. **If the user doesn't want to change it**, stop. A version with changes requested or rejected never goes live, and a blocked game stays unlisted. Don't try to get around the note: don't republish the same thing to clear it, rename the game, or publish it under a new slug.

package/dist/skill/reference/mouse-lock.md

@@ -1,6 +1,6 @@
 # Upgrade: mouse lock
 
-Aiming or steering with the mouse keeps the cursor in the game. Read this when the user asks for mouse lock (the JuicyJuicy Upgrades panel's prompt names this file), then follow "Add a JuicyJuicy upgrade" in SKILL.md to publish it.
+Aiming or steering with the mouse keeps the cursor in the game. Read this when the publish standards in SKILL.md find a game that aims or steers with the mouse without locking it, or when the user asks for mouse lock. JuicyJuicy doesn't lock the mouse for a game: the frame only allows it, and the game has to ask. If the user's game needs it, follow "Add a JuicyJuicy upgrade" in SKILL.md to publish the change.
 
 ## Why
 In a game that turns a camera or aims with the mouse, turning fast drags the cursor out of the game's frame, onto the page or another screen, and the game stops getting the movement. Pointer Lock hides the cursor and keeps sending movement however far the mouse goes. JuicyJuicy's frame allows it.
@@ -19,4 +19,4 @@ In a game that turns a camera or aims with the mouse, turning fast drags the cur
 Run the game: a click locks the cursor and turning works far past the frame's edges; Esc gives the mouse back and the game pauses with "Click to play"; a click resumes; menus can be clicked.
 
 ## Declare it
-Add `"mouse-lock"` to `features` in `juicy.json` (create the list if it isn't there, adding to what's listed). JuicyJuicy can't detect this one from the files, so the declaration is what turns it On in the panel; only add it once the lock works this way.
+Nothing to declare: mouse lock isn't a row in the Upgrades panel, so leave `features` as it is. A `juicy.json` that already lists `mouse-lock` is fine as it is too.

package/dist/skill/reference/touch.md

@@ -1,23 +1,44 @@
-# Upgrade: touch controls
+# Upgrade: mobile optimization
 
-The game plays on phones and tablets. Read this when the user asks for touch controls (the JuicyJuicy Upgrades panel's prompt names this file), then follow "Add a JuicyJuicy upgrade" in SKILL.md to publish it.
+The game plays well on phones and tablets: controls, screen, sound and speed. Read this when the user asks for mobile optimization or touch controls (the JuicyJuicy Upgrades panel's prompt names this file), then follow "Add a JuicyJuicy upgrade" in SKILL.md to publish it.
 
 ## Why
-Many players open a shared link on their phone. JuicyJuicy shows the game there full width, and players without a keyboard or mouse can only watch unless the game takes touches. Games with touch also get the **Touch controls** chip and filter on JuicyJuicy.
+Many players open a shared link on their phone. JuicyJuicy shows the game there in a frame that fills the screen below a slim bar. Players without a keyboard or mouse can only watch unless the game takes touches, and a game laid out for a desktop window ends up cut off or tiny. Games with touch also get the **Touch controls** chip and filter on JuicyJuicy.
 
 ## What to change
+Go through every part, also when the game already takes touches: fix what falls short and leave what's already right. Keyboard and mouse players keep the game as it was.
+
+### Controls
 1. **Pick the controls that fit the game**, and say which to the user before building, in a sentence:
    - **Taps and drags** for games already played with the mouse (clicks, aiming, dragging pieces): make the pointer code work for touch. Use Pointer Events (`pointerdown`, `pointermove`, `pointerup`) instead of mouse events, so one handler takes both; for multi-touch, track each `pointerId`.
    - **Swipes** for games with four directions (snake, 2048, tile puzzles): a swipe longer than about 30 CSS pixels in its main direction is the arrow key.
-   - **On-screen buttons** for games with keys held down (platformers, shooters, racing): a d-pad or a virtual stick on the left, action buttons on the right. Each button is at least 44×44 CSS pixels with space between, semi-transparent over the game, and holding it acts like holding the key (press on `pointerdown`, release on `pointerup`, `pointercancel` and `pointerleave`).
+   - **On-screen buttons** for games with keys held down (platformers, shooters, racing): a d-pad or a virtual stick on the left, action buttons on the right. Each button is at least 44×44 CSS pixels with space between, semi-transparent over the game, and holding it acts like holding the key (press on `pointerdown`, release on `pointerup`, `pointercancel` and `pointerleave`). Moving and jumping at once must work: track each `pointerId`.
    Engines: Phaser has `this.input.on("pointerdown", …)` and `this.input.addPointer()` for more fingers; Godot has `InputEventScreenTouch`/`ScreenDrag` and a `TouchScreenButton` node that triggers an input action; Unity uses its Input System's on-screen controls.
-2. **Show on-screen buttons only on touch screens**: when `matchMedia("(pointer: coarse)").matches`, or from the first `touchstart`/`pointerdown` with `pointerType === "touch"`. Keyboard players keep the screen as it was.
-3. **Stop the browser taking the gestures.** On the game's canvas or container, set the CSS `touch-action: none` and `user-select: none; -webkit-user-select: none; -webkit-touch-callout: none`, so drags don't scroll or zoom the page and a long press doesn't select or open a menu. Keep `<meta name="viewport" content="width=device-width, initial-scale=1">`.
-4. **Fit a phone screen.** The game scales to its frame (no fixed 1280×720 page with scrollbars); text and buttons stay readable in a narrow window. If the game only works one way round, set `orientation` in `juicy.json` (`landscape` or `portrait`).
-5. **Menus and dialogs work by tap**: every key-only action ("press Enter to start", "Space to restart") gets a tap target too, and the help text says "tap" on touch screens.
+2. **Show on-screen buttons only on touch screens**: when `matchMedia("(pointer: coarse)").matches`, or from the first `touchstart`/`pointerdown` with `pointerType === "touch"`.
+3. **Stop the browser taking the gestures.** On the game's canvas or container, set the CSS `touch-action: none` and `user-select: none; -webkit-user-select: none; -webkit-touch-callout: none`, so drags don't scroll or zoom the page and a long press doesn't select or open a menu. On `html, body` set `overscroll-behavior: none; overflow: hidden`, unless the game is a page meant to scroll. Keep `<meta name="viewport" content="width=device-width, initial-scale=1">`.
+4. **Menus and dialogs work by tap**: every key-only action ("press Enter to start", "Space to restart") gets a tap target too, and the help text says "tap" on touch screens. Anything shown only on hover also needs a tap.
+
+### Screen
+5. **Fit the frame.** Size the game from the frame (`innerWidth` and `innerHeight`, or CSS `100%`): no fixed 1280×720 page with scrollbars, and nothing important cut off at a narrow width.
+6. **Survive every resize.** Rotating the phone, the browser's address bar sliding away and the on-screen keyboard all resize the frame. Listen for `resize`, lay the game out again and keep playing: never restart the level or lose the score because of it.
+7. **Stay readable.** Size text and buttons in CSS pixels from the frame, not from the game's internal resolution, so a 1920-wide canvas shrunk to a phone doesn't shrink its text with it: body text at least 14 CSS pixels, tap targets at least 44.
+8. **Work both ways round if you can**, with a layout for tall and for wide frames, as the shapes are very different. If the game only works one way, set `orientation` in `juicy.json` (`landscape` or `portrait`) and, when the frame is the other way round, pause and show "Rotate your phone" over the game until a `resize` puts it right. Nothing rotates the game for you: `screen.orientation.lock()` doesn't work on iPhones.
+9. **Keep controls clear.** On-screen controls sit at least 16 CSS pixels from the frame's edges, under the thumbs, and don't cover the player or the action. In a tall frame, put them below the play area when there's room.
+10. **Never need fullscreen.** iPhone Safari can't put a game in fullscreen: hide the game's own fullscreen button when `document.fullscreenEnabled` is false.
+
+### Phone browsers
+11. **Sound starts on a tap.** Phones keep audio silent until the player touches the game: create or `resume()` the `AudioContext` in a `pointerup` or `click` handler (iPhones don't accept `pointerdown`), and `resume()` again when the page becomes visible, since a call or switching apps suspends it.
+12. **Nothing depends on the mouse or keyboard being there.** Phones have no Pointer Lock: when `requestPointerLock` is missing or fails, aim by dragging or with a stick. Only a real `<input>` brings up the on-screen keyboard: focus it inside the tap's handler and give it `font-size: 16px`, or iPhones zoom the page.
+13. **Run smoothly.** Cap the drawing resolution on touch screens at `Math.min(devicePixelRatio, 2)`, and use fewer particles or effects there if a round drops frames. Desktop keeps its full quality.
+14. **Stop when hidden.** Phones switch apps often: on `visibilitychange` to hidden, pause a real-time game and stop its sound.
 
 ## Check it
-Run the game in the browser's device mode (a phone size, touch on) and play a full round with touch only: start, play, pause, game over, restart. Then check the keyboard and mouse still work as before.
+Run the game in the browser's device mode (a phone size, touch on), upright and on its side (about 390×844 and 844×390), and play a full round with touch only: start, play, pause, game over, restart. Rotate in the middle of a round and check it carries on. Check the page never scrolls or zooms and nothing is cut off. Then check the keyboard and mouse still work as before.
+
+Device mode can't show everything, sound on iPhones above all: tell the user, in a sentence, to try the game on a real phone after publishing.
+
+## When it doesn't fit
+Some games can't work on a phone, such as one that needs a full keyboard all the time. Tell the user why, do what still helps (screen fit, readable text) if they want it, and don't declare it.
 
 ## Declare it
-Add `"touch"` to `input` in `juicy.json` (`"input": ["keyboard", "touch"]`, keeping what's there), and `"touch"` to `features` (`"features": ["touch"]`, adding to the list). JuicyJuicy can't detect this one from the files: `input` is what the site's chip and the Upgrades panel read, so only add it once a full round plays by touch.
+Add `"touch"` to `input` in `juicy.json` (`"input": ["keyboard", "touch"]`, keeping what's there), and `"touch"` to `features` (`"features": ["touch"]`, adding to the list). JuicyJuicy can't detect this one from the files: `input` is what the site's chip reads and `features` is what ends the Upgrades panel's offer, so only add them once a full round plays by touch.

package/dist/skill/reference/troubleshooting.md

@@ -6,7 +6,7 @@ With `--json`, a failed command's last line is `{"ok": false, "error": {"code",
 
 | Code | Meaning | Fix |
 |---|---|---|
-| `UNAUTHORIZED` | No saved login, or the token was revoked. | `npx -y juicyjuicy@0.15.0 login --json` (the user approves in the browser). In CI, set `JUICY_TOKEN`. |
+| `UNAUTHORIZED` | No saved login, or the token was revoked. | `npx -y juicyjuicy@0.16.0 login --json` (the user approves in the browser). In CI, set `JUICY_TOKEN`. |
 | `EXPIRED_TOKEN` | The login code expired (10 minutes) or was used. | Run `login` again. |
 | `ACCESS_DENIED` | The user clicked Deny. | Ask them, then run `login` again. |
 

package/dist/skill/reference/update-all-games.md

@@ -2,12 +2,12 @@
 
 For "bring my JuicyJuicy games up to date", "fix the required updates", a **Needs update** badge on My games, or a `check` or `publish` that warns `requirement-missing`. Sometimes JuicyJuicy makes a rule every game must follow (say, `juicy.json` listing its `features`). A game that doesn't follow it, or that JuicyJuicy hasn't checked yet, leaves the public lists after the deadline; its link keeps working.
 
-To only say which games need an update, without checking or changing anything: `npx -y juicyjuicy@0.15.0 list --json` gives each of the user's games `needsUpdate`, one entry per required update (`title`, `deadline`, `phase` `enforced` once it's past the deadline, `notChecked` when JuicyJuicy hasn't checked the game yet, which step 1 settles); `[]` means none.
+To only say which games need an update, without checking or changing anything: `npx -y juicyjuicy@0.16.0 list --json` gives each of the user's games `needsUpdate`, one entry per required update (`title`, `deadline`, `phase` `enforced` once it's past the deadline, `notChecked` when JuicyJuicy hasn't checked the game yet, which step 1 settles); `[]` means none.
 
 1. **Check every game at once.** Log in first (SKILL.md step 1), then run:
 
    ```bash
-   npx -y juicyjuicy@0.15.0 check-games --json
+   npx -y juicyjuicy@0.16.0 check-games --json
    ```
 
    JuicyJuicy checks the live version of each of the user's games on its side. It records which features each one has and, for a game whose `juicy.json` never listed its `features`, declares what it finds in the files (like cloud saves). Nothing is uploaded and no new version is made. The result has one entry per game in `games` (`features` with `on`/`off`/`unknown`, `requirements` with `passed`), `toFix` (the games that still need a code change, each with its `prompts`), `notReached` and `next`.
@@ -15,7 +15,7 @@ To only say which games need an update, without checking or changing anything: `
 2. **If `notReached` isn't empty**, run `check-games` again: it had no time for those games.
 
 3. **For each game in `toFix`**, one at a time:
-   - Find its project, or download the live version with `npx -y juicyjuicy@0.15.0 pull <slug> --json` (SKILL.md, "Add a JuicyJuicy upgrade", step 1).
+   - Find its project, or download the live version with `npx -y juicyjuicy@0.16.0 pull <slug> --json` (SKILL.md, "Add a JuicyJuicy upgrade", step 1).
    - Do what each prompt says, with the recipe it names when it names one.
    - Make sure `juicy.json` has `features` (`[]` if the game has none of the upgrades).
    - Check and publish an update as SKILL.md steps 5–7 say, with `--message "Required update: <what>"`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "juicyjuicy",
-  "version": "0.15.0",
+  "version": "0.16.0",
   "description": "Publish AI-made browser games to juicyjuicy.games",
   "type": "module",
   "license": "MIT",