Send the link with the result context
After a completed run, the sharing flow prepares a score card and a message. The message identifies the score and companion and includes the daily date for a daily run. Keep the generated link with that context when inviting a friend. An image alone can communicate the achievement, but a recipient cannot use pixels in a screenshot to select the same course automatically.
Know what the recipient needs
The recipient’s browser still needs the requested gameplay discoveries. If Daily is locked, the game falls back to Classic; if the companion is locked, it falls back to Pip. In those cases the original target is removed because the movement or course no longer matches. An unavailable forest can fall back to Wildwood without changing the underlying course and companion comparison.
Keep the date and version distinct
An older calendar date is not automatically invalid. A compatible dated invitation can hold that course even after the normal daily selection moves forward. Version compatibility is a separate question: links identify a particular rules and course version, and incompatible versions are not accepted as the same challenge. Explicitly changing the selected course or companion clears the incoming target. If a challenge seems not to apply, check the complete link, the recipient’s unlocks and any later companion or course selection. There is no separate incoming challenge prompt; exceeding a retained target is acknowledged on the result screen. Each player still completes a local run; the invitation is a shared target rather than a synchronized session.