Fluxzero 1.156.2

1.156.2 (2026-04-29)

Bug Fixes

• fix(entity): route nested child creation via matching parent (e4180ed)

  When replaying nested aggregate updates, a routed event could be applied
  to the wrong parent if the routing key matched a higher-level entity while
  the payload also contained ids for descendants. In that case empty child
  target resolution could treat the first matching child slot as valid and
  add the new entity under the first sibling instead of the intended parent.

  Prefer explicit parent ids from the payload when resolving empty child
  targets, and only fall back from a routing key to other route candidates
  when the routing key targets the current entity. This keeps normal child
  routing on the existing fast path while allowing aggregate-routed events to
  find the correct nested parent.

  Add regression coverage for nested creation and replay across parent,
  child, alias, typed-id, deep, and fourth-level routing scenarios.