Correct drifted code snippets on the Bevy-Adapter page Audited the moved snippets against current astrodyn_bevy source. Structural content (7 AstrodynSet variants, set ordering, the 21 system names, AstrodynPlugin, the C-suffix/planet-phantom convention) was accurate; the detailed Rust was early-design fiction that had drifted. Fixed: - Component wrappers now wrap the typed siblings actually in src/components/state.rs (TranslationalStateTyped<PlanetInertial<P>>, RotationalStateTyped<SelfRef>, …); dropped the bogus `(T, PhantomData<P>)` shape — the phantom rides inside the typed. - gravity_computation_system / integration_system: replaced fictional signatures that called astrodyn_gravity::compute_all_gravity / astrodyn_dynamics::integrate_step (which also violated the three-layer rule) with the real shape — generic <P: Planet>, *C components, delegating to the gateway astrodyn::run_gravity_stage / astrodyn::integrate_body. The integration skeleton is marked simplified and points to the source file. - Multi-stage integration: removed the non-existent IntegrationState resource / IntegrationMethod enum; documented the real mechanism (IntegratorTypeC component, IntegrationDtR resource, GaussJacksonStateC / LsodeStateC multistep state). - Spawn guidance: corrected the "no bundle struct" claim — PlanetBundle<P> / SunBundle are Bundles; bodies spawn via VehicleConfig::spawn_bevy. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Test User committed May 30, 2026

Split Bevy/ECS material out of Strategy into a Bevy-Adapter page Strategy is now engine-neutral end to end; all Bevy/ECS specifics live on a new Bevy-Adapter page documenting astrodyn_bevy as one host of the astrodyn pipeline. New page (Bevy-Adapter.md): "Why Bevy for the reference adapter", the JEOD->ECS mapping, Bevy component wrappers, the FixedUpdate/AstrodynSet schedule, and AstrodynPlugin composition — moved verbatim from Strategy with host-framing intro. Strategy.md (section numbers kept stable; ECS-titled sections repurposed): - Drop §1 "Why Bevy?" (moved). - §2 "ECS Architecture Mapping" -> "From JEOD's Architecture to the Pipeline": engine-neutral decomposition (managers->stage functions, hierarchies->focused types, pointer trees->arena trees, dispatch->enums, call order->PIPELINE_ORDER); ECS realization pointed to the adapter page. - §3.8 "Bevy Components" -> "Host storage" pointer. - §4 "System Pipeline" -> "Pipeline Stages": engine-neutral stage list + order, with Bevy/runner realizations linked out. - §5 "Plugin Architecture" -> "Workspace Structure and Layering": crate map and three-layer rule stay; plugin composition replaced with a host-wiring pointer. Fixed stale #portability-goal anchor -> #engine-independence. Home.md: add Bevy-Adapter to the nav. Integration-Groups.md: repoint the Strategy §4 link to the new §4 + the adapter's execution-schedule section. All cross-page anchors verified. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Test User committed May 30, 2026