Bedrock resource pack bug

Summary: On Bedrock Dedicated Server 1.26.36.1 (also seen on 1.26.33.2), resource packs listed in world_resource_packs.json never load. No console log entry, no client download prompt, and the pack never appears as Active under Global Resources. Behavior packs, using the identical setup pattern (world_behavior_packs.json, matching UUID/version, matching folder structure), load correctly every time and are confirmed working in-game (e.g. a redstone add-on's mechanics function correctly).

Reproduced across two separate machines, two separate networks (Virgin Media and Starlink), a brand-new minimal test world, and a completely fresh BDS install. No configuration or environment cause found after extensive testing (details below).

Steps to reproduce:

1. Fresh BDS 1.26.36.1 install, empty folder.

2. Add a valid resource pack (correct manifest.json) to resource_packs/.

3. Start once to generate a fresh world.

4. Add world_resource_packs.json to the world folder:

[{"pack_id":"8a1e8987-5738-42db-a2ed-413355e46f41","version":[2,1,0]}]

(UUID/version exactly matches the pack's manifest header.) 5. Start server again. 6. Console never logs a "Pack Stack" entry for the resource pack (behavior packs always log correctly, e.g. Pack Stack - [00] ... @ behavior_packs/luckyblockbv10). 7. Join with matching-version client — no download prompt appears despite texturepack-required=true; Global Resources shows only vanilla.

Expected: Resource pack logs in console Pack Stack, client is prompted to download it, and it appears Active under Global Resources.

Actual: Complete silence — no log entry, no prompt, not listed as active, and no error of any kind even with verbose logging enabled.

Troubleshooting already completed (all ruled out):

• Valid JSON confirmed (no syntax errors, no trailing commas)

• Exact filename confirmed, no double extension (dir -Force)

• No UTF-8 BOM in either world_resource_packs.json or the pack's own manifest.json (verified via Format-Hex)

• Rewrote file from scratch with explicit BOM-less UTF-8 — no change

• UUID in pack manifest matches pack_id in world_resource_packs.json exactly

• Folder structure matches working behavior pack layout

• No Zone.Identifier / Mark-of-the-Web flag on manifest files

• Identical icacls permissions between working BP folder and failing RP folder

• Tested on original world and a brand-new minimal test world — same failure on both, ruling out stale/corrupted level.dat pack cache

• Fresh BDS install in a new folder (not overwrite) — same failure

• Confirmed level-name in server.properties matches world folder name exactly

• Same pack files tested on a second Windows 10 laptop, fresh install, separate network (Starlink vs. Virgin Media on primary machine) — same failure, ruling out router/firewall/network-specific blocking

• Client and server versions confirmed matching (1.26.36.1)

• Verbose content logging enabled throughout — never shows any resource pack entry, success or failure

Possible related issue: Bedrock 26.0 changelog notes a fix for "global resource packs did not apply after leaving the settings screen (MCPE-233214)." This may be a regression of that issue, or a related but distinct bug specific to BDS's world_resource_packs.json handling.