Aeldrion

item and block fields have been changed to arrays in the pre release, so criteria like consumed_item and inventory_changed need to be updated, for example:

{
  "criteria": {
    "example": {
      "trigger": "minecraft:inventory_changed",
      "conditions": {
        "items": [{
          "items": [
            "minecraft:stone_sword",
            "minecraft:iron_sword"
          ],
          "nbt": "{Enchantments: [{id: 'minecraft:sharpness'}]}"
        }]
      }
    }
  }
}

I think this is intended. For features to generate randomly within the chunk, use the minecraft:square feature decorator.
If I recall correctly, the issue with MC-194200 was that the Birch Forest and Birch Forest Hills biomes referenced the `minecraft:birch` feature directly rather than the `minecraft:trees_birch` feature which itself indirectly references the `minecraft:birch` feature with `minecraft:square` and `minecraft:count_extra` decorators.

More generally, it looks like features that belong in a certain biome are cut off when generating near the edge of a biome, because they cannot generate in neighbouring biomes. This happens for custom worldgen features in the latest snapshots as well.
It is incredibly common for end cities because they are quite big and end biomes are quite small, if you open the F3 menu you can tell that the structure is often cut along the frontier between end midlands and end highlands. I've seen it happen for end ships too (See the end ship at [-3130, 100, -1290] in seed 1888182844041881602).

From Bartosz Bok in a Discord message on the Minecraft Commands server:

For example, category in creative menu was prefixed with §l§9 (bold+blue). Apparently colors cleared styling, so that was never visible

So it seems to be intended.

I can confirm this bug also occurs while using advancements command rewards.

Which is annoying.

They do take relative coordinates. You just have to use dx, dy and dz and not x, y and z.