Roblox Release Readiness

Produce an evidence-backed gate, not a generic checklist filled with optimism. Separate local code/Studio evidence from publishing, moderation, policy, and dashboard state.

Audit boundary

This workflow is read-only unless the user also asks to fix findings or write a report file. Do not publish, configure products, spend money, change external dashboards, message users, or mutate production data as part of an audit.

1. Read the applicable AGENTS.md, release scope, design acceptance criteria, known issues, test evidence, and repository state.
2. Read references/gate-matrix.md and references/readiness-report.md.
3. Confirm the exact experience/place, destination owner, candidate version, target audience/devices, and intended release type.
4. Select the correct Studio before inspection. Do not infer current Creator Dashboard state from local configuration.
5. Use $roblox-docs for current policy, monetization, privacy, publishing, moderation, age, localization, and platform requirements.

Evidence statuses

Assign one status to every applicable gate: