- Shipped
- 5 செப்டம்பர், 2026 அன்று 11:49 PM UTC
- Author
- Kamo
- Commit
- 97cd41f
The careers board sends candidates to /team?jobId=<uid>. That uid is parked in an apex cookie as before, but it is now READ BACK at submit and sent in the registration body as appliedJobId, so SecurityService can write it onto the new team member as recentlyAppliedForId. The cookie was always the carrier, never the destination — it only ever existed because registration is several steps and bounces through email verification, and nothing held in this flow's own state survives that. What changes is where it ends up: the workspace now reads the uid off the member's own record instead of off a cookie the browser is still holding, so the prompt is spent by an answer rather than by a page load. Read at submit rather than captured at mount, for the same reason: the flow is remounted on the way back from verification. The claim-token half goes away with applying-without-an-account. There is no longer an anonymous application row for a new account to adopt.