Harden gameplay timing and map loading

README.md

@@ -20,6 +20,13 @@ npm run build
 npm start
 ```
 
+Before public deployment, follow the [production launch guide](docs/production.md).
+`npm run check` runs unit tests, TypeScript checking and the production build.
+With the compiled site running, `npm run test:production -- http://localhost:3000`
+checks HTTP routes, privacy, signed images and five-round gameplay against the
+configured Supabase project. It creates and removes one temporary guest game;
+at least one map must be published.
+
 `npm start` and `npm run dev` supervise both the website and processing worker. The worker is required to turn an upload into a previewable draft. `npm run worker` also loads `.env.local` when run separately. Setup downloads the pinned vanilla rendering assets and the Chromium runtime used by the existing terrain-rendering worker. Browser UI checks are separate from this worker.
 
 Missing vanilla assets are also prepared automatically when a plugin export is rendered. For an existing failed or empty draft, stop the worker and use `npm run reprocess -- <dataset UUID>` before restarting. This retains the raw upload. See [empty-render recovery](docs/server-plugin.md#recover-an-empty-render).