How release notes work

Outcome: Release notes summarize verified user-facing changes. Unfinished features stay out of stable Help Center guidance until verified.

Principles

• Only document committed, user-visible behavior
• Call out plan, permission, or Credits impact when verified
• Keep App Windows, Orbit, Admin Backoffice, and unfinished Games details in draft until ready
• Link to Help Center task articles instead of repeating full procedures

Future dated release-note entries will live in this category as they are published.

What users should expect

• Clear descriptions of user-visible behavior changes
• Links to Help Center task articles for full procedures
• Honest Beta or limited-availability labels when needed

What release notes will not do

• Announce unfinished internal drafts as stable product behavior
• Document private implementation details or worktree names
• Replace Wallet pricing configuration with guessed numbers

Related articles

• Documentation status labels