A care context is linked when the callback says so, not when the call returns
The M2 linking journey showed the link confirmed on the linking call itself. The call
returns 202 and decides nothing. The outcome arrives later as a POST to
/v3/link/on_carecontext on your bridge, carrying status and the REQUEST-ID you sent.
If you marked records as linked on the 202, go back and key that on the callback instead.
M2 Attach, journey 1.