Moved object remains linked to original habitat

When an object is relocated from Habitat A to Habitat B using the Habitat Builder, the object visually appears and functions in Habitat B, but the game continues to treat it as though it belongs to Habitat A.

Because the object is still associated with Habitat A internally, Habitat A cannot be fully deconstructed. The game behaves as if a component is still attached, even though the object has been physically moved elsewhere.

As a workaround, using the Early Access refund feature on Habitat A removes the habitat. However, the refund process also refunds the moved object, despite the object being located inside Habitat B and no longer visually connected to Habitat A.

Steps to Reproduce:

1. Build Habitat A.
2. Place an object inside Habitat A.
3. Build Habitat B some distance away.
4. Use the Habitat Builder to move the object from Habitat A to Habitat B.
5. Attempt to deconstruct Habitat A.
6. If deconstruction is blocked, use the refund feature on Habitat A.

Expected Result:

• The moved object should become associated with Habitat B.
• Habitat A should deconstruct normally.
• Refunding Habitat A should only refund components that actually belong to Habitat A.

Actual Result:

• The moved object remains internally linked to Habitat A.
• Habitat A cannot be deconstructed.
• Refunding Habitat A also refunds the moved object, even though it is located in Habitat B.

Additional Notes:
The issue appears to be with ownership/association data not updating when an object is moved between habitats. The object’s visual location updates correctly, but its habitat reference remains attached to the original habitat.

This sounds more like a bug report than a suggestion, but being able to freely move things between habitats could be a useful addition. Although maybe a bit niche, I feel like usually people just deconstruct the things and then rebuild them elsewhere in most cases?