v4.2.0

"Stable World" (LOG #185–#187): 4.1.20's code, the version changed (plan 4.1.20 §12, D34), one Field Kit fix, and
ship preflight-stable reading the reduced verdict below. It
restores strict SemVer: from 4.2.0 a minor adds, a major removes. It ships before the people's passes (D38, the
maintainer's decision): none of the thirteen (#75–#87) was made, so 4.2.0 promises as stable only what needs none,
the content format and its tools, the desktop Chromium PWA and the Bridge on SQLite, and says every other surface
limited or experimental (GO / NO-GO 4.2: GO on a reduced scope). The passes are made on
v4.2.0 itself; promoting a surface in a 4.2.x needs its pass on that 4.2.x. The tag is signed with the maintainer's SSH key
and the release is immutable. npm publishing moves to a later 4.2.x: it needs the maintainer's 2FA at each
step. v4.2.0-rc.1 carried the defect below; v4.2.0-rc.2 was the campaign's candidate, no pass used either.

Fixed

• field:check and field:report work on a folder fresh from field:init (4.2.0): field:init writes the
  candidate's surfaces and site files beside the thirteen reports (4.1.20), and the two read them as reports, so the
  first check of every pass failed and field:report wrote nothing. Found trying the commands on v4.2.0-rc.1's
  candidate before any pass began; the test folder now holds what field:init writes.

Changes

• The README installs from 4.2.0's release archive (4.2.0): releases/download/v4.2.0/web-scumm-4.2.0.tgz.
  docs:truth, quality:baseline and readme-quickstart still accept a v<version>-rc.N release for this
  version's archive and nothing else, for the next campaign that needs one.
• ship preflight-stable reads "GO for 4.2 on a reduced scope" (4.2.0, D38): the maintainer's decision to ship
  before the passes is not a GO, so no report contradicts it; a plain GO the reports contradict still blocks, and
  tests/support-truth.test.ts accepts the reduced verdict only with D38 written.

Manual passes (D12: reported, not blocking)

0 of 13 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