Answer
This is a documented, known technical limitation rather than a configuration mistake — navigation from a reference-type custom attribute is confirmed to open the correct target page but not apply a filter for the specific record being navigated from; there's currently no configuration workaround for this specific gap, so plan any workflow relying on reference-attribute navigation around users needing to locate the specific record themselves once the target page opens.