ENG2-P9-07: Example games refresh: 2–3 games validating the v2 API (consolidates #333/#336/#340/#342/#345/#348/#139)

[aram-devdocs]

Parent

• Program: ENG2 — GoudEngine v2 Rebuild (see the pinned master tracking issue)
• Phase / Milestone: Phase 9 — Authoring, Platforms, Examples & Polish (eng2-p9-authoring)
• Batch / Group: Batch 9.2 — Examples, docs, agent configs (4 groups, parallel), Group B
• Runbook spec: docs/src/runbook/phases/phase-9.md (committed with the roadmap)

Summary

Refresh 2-3 example games to validate the v2 API end-to-end, consolidating seven existing open example-game issues (#333, #336, #340, #342, #345, #348, #139) into one piece of work against the post-rebuild API.

Architecture Context

Layer: Apps — examples/ sits outside goud_engine/src/, connects via SDK/FFI only per .agents/rules/dependency-hierarchy.md. (see tools/lint_layers.rs — downward-only deps).
Modules/types touched:

• examples/csharp/, examples/python/, and/or other language directories under examples/ — refresh 2-3 games (e.g. Flappy Goud parity pair, a 3D example) to exercise the v2 API surface produced by Phases 1-8.
• examples/shared/ — shared assets across SDKs, update if the refreshed games need new/changed shared assets.

Boundary constraints (only those that apply):

• Examples MUST use the SDK API only, never internal engine types (.agents/rules/examples.md).
• Python Flappy Bird and C# Flappy Goud must stay in parity per .agents/rules/examples.md.

Pattern to follow: .agents/rules/examples.md's existing structure and the parity requirement between the Python and C# Flappy Bird/Goud examples — this issue is a refresh onto the v2 API, not a new example architecture.

Scope

• Refresh 2-3 example games to build and run against the v2 API surface produced by the earlier phases (render core v2, FFI v2, sprite core v2, etc.).
• Consolidate and close F24-01: Flappy Bird in ALL SDK languages #333, F24-02: Platformer game #336, F24-03: Top-down RPG #340, F24-04: 3D showcase #342, F24-05: Multiplayer game example #345, F24-06: Mobile-optimized game #348, and F24: Example Games #139 as covered by this refresh.
• Verify each refreshed example end-to-end with ./dev.sh per .agents/rules/examples.md.
• Keep Python Flappy Bird and C# Flappy Goud in parity if both are among the refreshed set.
• Tests: spec test at goud_engine/tests/spec/ + unit/isolation coverage for the new code paths.
• Docs/rules updates if this invalidates .agents/rules/* or docs/src/*.

Acceptance Criteria

• 2-3 example games build and run successfully against the v2 API in required CI (direct Phase 9 gate item).
• F24-01: Flappy Bird in ALL SDK languages #333, F24-02: Platformer game #336, F24-03: Top-down RPG #340, F24-04: 3D showcase #342, F24-05: Multiplayer game example #345, F24-06: Mobile-optimized game #348, F24: Example Games #139 all closed with a reference back to this issue.
• Any refreshed game exercising SDKs kept in parity (per .agents/rules/examples.md) is verified end-to-end via ./dev.sh.
• cargo check && cargo fmt --all -- --check && cargo clippy -- -D warnings clean; cargo test green; ./codegen.sh && git diff --exit-code (drift gate)

Breaking Change & Throne Follow-up

None from this issue directly — it adapts examples to whatever breaking changes earlier phases already introduced; no new breaking surface of its own.

Blocked By

ENG2-P9-06 (native Rust reference example should exist before the broader example-games refresh).

Files Likely Touched

• New/Modified/Generated: examples/csharp/**, examples/python/** (and/or other refreshed language dirs), examples/shared/** as needed

Agent Notes

• Consolidation list per design-technical.md section 12's disposition map: F24-06: Mobile-optimized game #348/F24-05: Multiplayer game example #345/F24-04: 3D showcase #342/F24-03: Top-down RPG #340/F24-02: Platformer game #336/F24-01: Flappy Bird in ALL SDK languages #333/F24: Example Games #139 example games → ENG2-P9-07. Close each of these seven with a reference to this issue once its scope covers them — do not leave them open as separate untracked work.
• This issue necessarily runs late in Phase 9 because it validates the cumulative v2 API surface from Phases 1-8; do not start it before the API it's validating has landed.

Verification

cargo check && cargo fmt --all -- --check && cargo clippy -- -D warnings
cargo test
./codegen.sh && git diff --exit-code