Hey, thanks for the report. This is a known bug. In multi-root workspaces, the agent resolves paths relative to the first workspace folder instead of treating each folder independently.
A similar report was filed here: Code reference links in chat only resolve against the first workspace folder
The team is aware of this. No ETA yet, but your report helps with prioritization.
As a workaround for now, you can try opening the framework folder in a separate Cursor window and using it alongside your module window. Not ideal, but it avoids the path resolution issue entirely.