feat: add Bevy engine support - #104
Merged
Merged
Conversation
…reaking-changes, deprecated-apis, current-best-practices) Task 2 of Bevy engine support: source-verified reference set for Bevy 0.19.0 (2026-06-18), covering 0.16->0.17, 0.17->0.18, 0.18->0.19 transitions. Every entry cites the official migration guide or release page.
- breaking-changes.md: drop dead 0-17-to-0-18/#bevy-render-reorganization anchor; attribute mesh/image bevy_render re-export removal to 0.17 (per 0-16-to-0-17 guide) - VERSION.md: label Key Theme rows as X-to-X+1 transitions (themes were off-by-one; 0.19 row duplicated 0.18); note 0.19 is latest with no 0.19-to-0.20 guide yet - VERSION.md: Skybox moved to bevy_light in 0.19 (from bevy_core_pipelines), not part of the 0.17 split - deprecated-apis.md: un-garble MergeMeshError 'Don't use' cell (0.16 name; was a struct)
Quick-reference guides for Bevy 0.19.0: ecs, 2d, 3d, ui, asset, input, audio, testing. Every API name verified against docs.rs bevy 0.19.0 pages and the official migration guides; reuses Task 2 verified facts (breaking-changes, deprecated-apis). Documents 0.16->0.19 renames: Message/MessageWriter/MessageReader, WorldAssetRoot, Resources-as- components, removed *Bundle structs, Gamepad-as-component, no PhysicalKey, Touches resource, LoadState, load_builder, FontSource/FontSize.
…wledge gap (Task 5)
…p-engine (Task 6)
Task 7 of the Bevy engine support plan: add Bevy to every user-facing engine enumeration in AGENTS.md (engine choice, note, available modules, setup-engine example, Engine Specialists), README.md and init-template module tables, engine-code.md cross-reference plus Rust/Bevy example pair (delta_secs verified against docs/engine-reference/bevy/modules/2d.md), and agent-roster.md Engine Leads.
- VERSION.md: correct bevy_light 0.17 light-type list (AtmosphereEnvironmentMapLight, not Atmosphere); note Atmosphere added in 0.19 - breaking-changes.md: DespawnOnEnter/DespawnOnExit now trigger on same-state transitions only since 0.19 (0.18 had the bug); remove wrong 0.18 attribution - current-best-practices.md: mirror the same attribution fix
Merged
striderZA
added a commit
that referenced
this pull request
Aug 10, 2026
## Summary Follow-up to #104 (Bevy engine support) plus release prep for v0.13.0. ### Fixed - **Bevy agent frontmatter leak**: removed OpenCode-only `mode`/`model` fields from the canonical `.agents/agents/bevy-specialist.md` (the only one of 52 canonical specialists carrying them) so it matches every sibling engine specialist and the harness-agnostic contract. - **Stale doc counts**: bumped `21 modules -> 22` and `51 agents -> 52` across README.md and AGENTS.md (6 locations) left behind by the Bevy module/agent addition. ### Added - CHANGELOG.md entry for v0.13.0. ### Verification - `node tests/agents/validate.mjs` -> PASS, 207/207, 100% coverage - `npm run test:plugins` -> 158/158 pass
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds Bevy as a first-class engine in the OCGS framework, at parity with SFML 3 / Raylib.
What's included
engine-bevymodule (both.agents/modules/and.opencode/modules/trees) with a singlebevy-specialistagent covering ECS, 2D/3D rendering, bevy_ui, assets, audio, input, Cargo build, and WASM/mobile. Installed in both harnesses.docs/engine-reference/bevy/— VERSION (pinned Bevy 0.19.0, HIGH knowledge-gap risk), breaking-changes, deprecated-apis, current-best-practices, and 8 module guides (ecs, 2d, 3d, ui, asset, input, audio, testing). Every API claim is source-verified against official Bevy 0.19 sources (migration guides, docs.rs) with citations — including 0.19-specific breaks beyond the LLM cutoff (gamepad as component viaQuery<&Gamepad>, MessageWriter/Message split, mesh/material components, resources-as-components,DespawnOnEnter/DespawnOnExitsame-state fix)./setup-engineintegration — Bevy in guided selection, honest tradeoffs, genre guidance, HIGH-risk knowledge-gap baseline, technical-preferences template, specialist routing table, and a Cargo.toml + main.rs scaffold.engine-coderule (Rust/Bevy zero-alloc example), agent roster.Verification
node tests/agents/validate.mjs— PASS, 100% coverage (207 agents)npm run test:plugins— 158/158 pass/setup-engineBevy flow: all 9 checkpoints PASSNotes
docs/superpowers/directory (not committed, per user instruction).docs/engine-reference/bevy/VERSION.mdKey Crates table has no per-row Source column (matches raylib parity; citations in report).