chore(release): prepare public examples for v0.9.0

[amasiye]

Summary

• publish the standalone example-games repository setup
• document public installation paths
• validate projects in CI
• synchronize engine versions after releases

Validation

• latest example-games CI completed successfully
• develop contains no generated game output

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ffa65426f0

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Synchronize engine releases through develop

When an engine-released dispatch contains a new version, this forces the synchronization job onto main, and the later git push origin HEAD:main writes directly to that branch. This bypasses the newly established develop-first workflow, leaves develop targeting the old engine version, and risks a subsequent develop-to-main merge reverting the synchronized release; check out develop and push with an explicit develop:develop refspec instead.

AGENTS.md reference: AGENTS.md:L18-L21

Useful? React with 👍 / 👎.