sparkengine-editor-scenes-and-reflection

The SceneFile v2 loader requires the version field to appear exactly once and equal SCENE_FILE_VERSION (2); any mismatch, duplication, or missing field rejects the whole file. There is no migration path, so old files must be resaved by a build that wrote them.

Register the type in SparkEngine/Source/Core/ComponentReflection.cpp using the SPARK_REFLECT macros and TypeInfo model defined in Core/Reflection.h. Once registered with TypeRegistry and ComponentFactory, the component's fields appear in the Inspector instead of "(no reflection data registered)".

The World-backed Inspector path calls RenderReflectedFields without a snapshot or CommandHistory command, so those edits are not undoable — this is a known open gap. The legacy SceneFile-backed Inspector path wraps edits in LambdaCommand and is fully undoable.

A code path replaced the World without going through EditorUI::SwapWorld, which clears CommandHistory before freeing the old World. Undo commands capture raw pointers into the old World, so skipping the clear causes use-after-free crashes.

No. Binary scene serialization is deliberately fail-closed: SaveBinary and LoadBinary return errors because the legacy raw-memory format was retired. Use the JSON .sparkscene format; restoring binary scenes is a schema-design task, not a bug fix.

Dialect A is reflected-World JSON with a top-level entities array and version 1 (written but not checked on load). Dialect B is SceneFile JSON v2 with objects, components, and environment, enforced by a fail-closed version and per-component schema gate.