Invalid relation created when importing a requirement inside a requirement

[pcdavid]

Steps to reproduce

1. Open a General View diagram
2. Create a requirement usage
3. In the Explorer, select it and disable the "Hide memberships" filter
4. From the diagram, open the requirement's palette and invoke Requirements > New Requirement
5. A sub-requirement is created (and displayed).
6. In the Explorer, note that the new requirement is owned through a Feature Membership (OK)
7. Select the parent requirement in the Explorer, and invoke Import as text.
8. Enter requirement child; as text and proceed with the import.
9. A sub-requirement is created, but the parent requirement's node now shows parentReq = requirement child; in its label (KO). In the explorer, note that the newly created sub-requirement is owned through a Feature Value instead of a Feature Membership.

Capture.video.du.2026-07-02.08-57-03.mp4

[pcdavid]

This was introduced between 2026.5.0 (but not present) and 2026.5.1 (bug present).