Memory5D operations

BETA / DEPLOYED ATOMICALLY. The commands below exist where named; the native beta route is deployed and live in production. available promotion remains gated on the moderated human-learning study and repeated public/docs smoke.

Controlled lifecycle

The historical iframe prototype was withdrawn by keeping the manifest at development. The completed native cutover uses svelte-component integration and frontend/src/lib/Memory5DGame.svelte; its shared package, match handler, progression repository, and generated registration artifacts exist in the repository. /play/memory5d must remain blocked until a deliberate beta promotion.

Only generated tooling writes game registries, Nakama wrappers, and leaderboard manifests. No hand edit is permitted for generated outputs. The registered handler advertises exact Quick/Host modes, ranked Nakama session mode, and manifest-owned leaderboard ids.

Implemented local gates

cd games/memory5d
npm run check
npm run test:core
npm run test:simulation
npm run test:server

The root registry contract uses:

node scripts/validate-game-manifest.mjs memory5d
npm run generate:game-registry
npm run check:game-registry

Nakama wrapper and leaderboard generation run after authoritative-code changes. Leaderboard manifests serialize Nakama runtime wire values (asc/desc, best/set/incr); nkruntime.d.ts mirrors those string unions, and a pod restart must log each Memory5D board as ready before any two-session leaderboard proof:

node scripts/generate-leaderboard-config.mjs
npm --prefix nakama-modules run generate:wrappers

Release discipline

During pre-promotion, local component, automated accessibility audit, balance, persistence, and authoritative-security gates must all pass before a beta canary; the moderated human-learning and accessibility validation is the available gate, not a beta gate. During that pre-promotion phase status remains development through backend smoke. The first real /play/memory5d test occurs only after a beta registry/manifest update and atomic frontend deployment; available follows only after the public canary and every evidence ledger item is observed.

Current state (2026-07-28): the manifest is beta, the native route is live in production, and the beta canary is recorded in the verification ledger. available remains gated on the staged human-learning and accessibility study.

Frontend deployment uses cd frontend && npm run deploy only. The production preflight requires at least 5 GB MemAvailable, no stale Vite dev server, valid built server/client assets, atomic backup preservation, and browser smoke after restart. Raw Vite builds are prohibited on the production host. Rollback restores the atomic build backup rather than improvising a new deployment.

Nakama deployment/restart follows the established platform workflow and is tested with two authenticated sessions before any public promotion.