v4.2.5

LOG #244–#245: the project is now called quest'n'click. It was web-scumm, named in homage to SCUMM, the LucasArts
engine whose spirit it follows, and is renamed so its name sparks no needless debate. Nothing changes for a
game: the formats keep their identifiers, so saves, runs and sessions load as before, and a game made for 4.2.4
installs, builds and plays under its old names. The old names (web-scumm, create-web-scumm, web-scumm-bridge,
web-scumm-connectors, web-scumm-studio-server, the web-scumm/… imports) work until 4.3: each 4.2.x release also
ships them as full copies. A release's files are named quest-n-click-… from this one, and its attestations name the
repository wanoo/quest-n-click. The tag is signed with the maintainer's SSH key on their yes of 20 October,
« Yes, sign v4.2.5 », the yes for v4.2.5 only.

Changes

• web-scumm becomes quest'n'click (4.2.5, D47): the project, its repository (github.com/wanoo/quest-n-click, the
  old links redirect) and its Pages site (wanoo.github.io/quest-n-click; the old address redirects there through
  wanoo.github.io) take the name quest'n'click. The packages and commands are now quest-n-click, create-quest-n-click,
  quest-n-click-bridge, quest-n-click-connectors (command quest-n-click-connector) and
  quest-n-click-studio-server (commands quest-n-click-studio-server, quest-n-click-studio-worker); a game imports
  quest-n-click/content, /player, /minigames, /testing, /reality; a release's files are named
  quest-n-click-<version>.tgz and quest-n-click-<tag>-…. Nothing to change in a game: through 4.2.x each release
  also ships web-scumm-<version>.tgz and the other old archives (the same files, the old package name), the old
  commands run after a one-line notice, and web-scumm/content and the other old imports still resolve; the aliases go
  in 4.3. The formats keep their identifiers (web-scumm-save, web-scumm-session, .wsrun, web-scumm-remix-1, the
  IndexedDB and localStorage names, the X-Web-Scumm-* headers, WEB_SCUMM_*), so saves, runs, sessions and
  deployments load and run as before. Releases up to v4.2.4 keep their files' names and their attestations' repository,
  wanoo/web-scumm. The READMEs open on the new logo and a short "Formerly web-scumm" note; UPGRADING §38 says how to
  switch, when you like.

• The sample games' credits say quest'n'click (4.2.5): the Pantry Key's credits ("A quest'n'click sample game",
  "Sound effects: generated by quest'n'click") and the Night Market's credits and title-screen line ("The reference
  chapter of quest'n'click"), in English and French. Their presentation fingerprint moves with them, so the reference
  run is recorded again; their rules, saves and proofs do not change.

Manual passes (D12: reported, not blocking)

0 of 19 done.

Pass	Status	Who, when	Device, OS, browser, versions	What failed
A multi-instance Bridge behind HTTPS on Postgres, a worker killed mid-verification (bridge-postgres-https)	not-run
Story, Remix and Daily runs submitted by real people (runs-real-players)	not-run
A run resumed after the machine was stopped and started again (run-resume-power-cycle)	not-run
The code wheel printed and used at the table; the text alternative by a screen-reader user (code-wheel-human)	not-run
A Mystery world played from the Remix menu against a deployed Bridge (mystery-deployed)	not-run
Safari offline on an iPhone, and its update (safari-ios-offline-update)	not-run
Firefox offline on a real machine (firefox-real-offline)	not-run
A real phone on both painters (phone-both-renderers)	not-run
A real LiveSplit and OBS session (livesplit-obs)	not-run
Real connectors and a person's security pass (connectors-real-security)	not-run
Playtesters who do not know the puzzles (blind-playtesters)	not-run
The voices listened to (voices-listening)	not-run
The published archive installed by a person (archive-human-install)	not-run
The Studio Server deployed on Clever Cloud (Node, PostgreSQL, Cellar, Keycloak, a TLS domain), from its archive, by its guide; a real Safari on macOS and iOS (studio-hosted)	not-run
Three people on one hosted Studio, a network cut and a redeploy while they edit (studio-collab)	not-run
On a hosted Studio, people play the shared revision without a dev server, a save carried across revisions, the health chip, their own undo, a published build (studio-preview)	not-run
A hosted Studio's prepare on the worker (Python, ffmpeg), its prepared set played in the Play tab (studio-assets-hosted)	not-run
An AI agent on a hosted Studio through its remote MCP (/mcp): a real MCP client, a member's token, a write in the journal as the member, a span another holds refused (studio-mcp-remote)	not-run
The Studio Server behind a second OpenID Connect provider (GitLab, D44): login, roles, a revoked member refused, verified by a person (studio-oidc-generic)	not-run