Bedrock 26.13: custom block "Unexpected version" error at every schema

Bedrock 26.13 (Windows): every custom block JSON emits [Blocks][error] "Unexpected version for the loaded data" for any format_version. The block still registers and works fully in-game, so the error looks erroneous.

Tested values, all warn identically: "1.26.13", "1.26.10", "1.21.130", "1.21.120", "1.21.80", "1.21.40", "1.21.0", "26.13.0". "1.26.20" instead fails registration: "[Texture][warning] block ... does not exist in the registry".

Repro
- BP/RP manifests: format_version 2, min_engine_version [1,26,13].
- One block at behavior_pack/blocks/glow_block.json:
{"format_version":"1.26.10","minecraft:block":{"description":{"identifier":"demo:glow_block","menu_category":{"category":"construction"}},"components":{"minecraft:geometry":"minecraft:geometry.full_block","minecraft:material_instances":{"*":{"texture":"demo_glow"}}}}}
- RP registers demo:glow_block in blocks.json + terrain_texture.json with a PNG.
- Apply to a fresh world and load.

Expected: no [Blocks][error]. "1.26.10" is the current documented schema on the Bedrock Wiki "Intro to Blocks" page.

Actual:
[Blocks][error]-block_definitions | ... | blocks/glow_block.json | Unexpected version for the loaded data
Fires at every otherwise-valid format_version, so the schema-version check itself looks broken on 26.13.

Impact: Marketplace cert rejects packs emitting [Blocks][error], blocking publishing of any custom-block add-on against 26.13. Also hides real block errors during dev.