BatchNode and SimpleBatchNode serialization do not restore correct runtime state after deserialization

After serializing and deserializing a BatchNode or a SimpleBatchNode using the standard jME Node read/write mechanisms, the internal runtime state is not correctly restored.

Specifically:

If BatchNode.batch() was called before serialization, the deserialized node may contain duplicated children (both the original geometries and previously generated batch geometries).

Internal structures such as batches, batchesByGeom, and related runtime data are not consistent with the scene graph.

The root cause is that batched geometries are runtime-generated and are serialized along with the original subtree, but the internal structures are not reconstructed during read().

Start by locating BatchNode and SimpleBatchNode and reading their batch(), read(), and write() paths alongside the standard jME Node serialization mechanisms. Reproduce serialization after batching, then inspect whether the deserialized scene graph and runtime structures agree. Done means no duplicated children and consistent batches and batchesByGeom state after deserialization.