- Shipped
- September 6, 2026 at 1:08 AM UTC
- Author
- Kamo
- Commit
- 10a8d81
Registration already wrote recentlyAppliedForId when an account was CREATED. This is the other half of the same funnel: plenty of people who press Apply on the public careers board already have an account, reach the register page, and follow the sign-in link. Nothing was created, so nothing recorded the advert, and they arrived in the workspace with no sign of the thing they had just clicked. AppliedJobStamp records it against the membership of the organization actually entered, from both sign-in completion paths — the direct one and the workspace picker. Both, because somebody who belongs to several organizations only ever arrives through the second, and a hiring funnel that worked exclusively for people with one workspace would fail silently for everybody else. The flag is RAISED, not merely set, even for someone who dismissed a previous prompt. That is the point of this path: pressing Apply on a specific advert is a fresh answer, and a flag lowered for a different job last month is not a reply to it. The cost is that whatever carries the uid must be spent once — kamo-login clears its cookie on success for exactly that reason. appliedJobId is bound on the FORM endpoint as well as the JSON one. Omitting it there is how `org` was once left readable only over JSON, which nothing sends: kamo-login posts form-encoded, so that is the endpoint every browser sign-in actually reaches. Parsed leniently and never fatal, and the stamp runs after the session is minted with every failure swallowed. A sign-in that succeeded must not be reported as a failure because a convenience did not record.