When a parent entity is created on a base branch and references a child entity in the same repo on the default/same branch, we currently omit the child entity’s branch from the parent YAML.

If the parent is later saved to a new branch, that omitted value becomes a problem: at runtime the child can be resolved from the parent’s new branch instead of the child’s own default/feature branch.

Request: Let users optionally force-save the referenced child entity’s branch in the parent YAML, so the child continues to resolve from its intended branch even after the parent moves to a different branch.