- Shipped
- September 6, 2026 at 1:10 AM UTC
- Author
- Kamo
- Commit
- cf75afe
RestrictedMembershipGuard builds it when the session's member id has not settled, the sign page's back link builds it, and kamo-login now lands a candidate on it after a sign-in that carried a job advert. None of them knows the id. Nothing resolved it. `isSelf` compares the route segment to the session's member id, so `me` failed that test and the page rendered with every self-only tab missing — Careers among them, which is the one the sign-in was aiming at. The failure looked exactly like a rights problem, which is the worst way for it to look: the page loads, it is simply missing the thing you came for. Swapped for the real id rather than special-cased inside `isSelf`, so everything downstream — every child that takes memberID, every link built from it — sees an id and not a word. The query string comes along, or the tab the caller asked for is lost on the way. `replace`, not `push`: `me` is a redirect, and leaving it in history means Back lands on it.