OriginAgentClusterDefaultEnabled policy is broken on all current Edge builds

Hi! During testing the changes the document.domain setter deprecation brings, we found the following bug. The OriginAgentClusterDefaultEnabled policy is broken on all current Edge builds. 

Basically what should happen when the policy is set (demoed via the developer flag):

What actually happens when its set: 

The policy kind of works, because when its set to "disabled" the developer flag doesn't work anymore and you get the same output as in second picture.

Also the change to remove document.domain setter was supposed to come in 116 (and many different major versions before that, but then Chromium and Chrome moved the timeline up), but it has now been moved to 118 and beyond without any kind of explanation as to why. Me, and by extension the organization I work in, would love some transparency to the site impacting changes process on Microsofts side.

Hopefully someone from the Edge sees this!