- Shipped
- September 4, 2026 at 12:34 AM UTC
- Author
- Kamo
- Commit
- a2e2227
Three changes, all in service of the new public job board at careers.<apex>. The posting editor gains "list on our public careers site". It sits with status and the dates rather than with compensation because it belongs to the same question they do — who can reach this advert, and until when — and an org turning it off is making a hiring decision, not a formatting one. Defaults on. /setup/dns gains the careers card. DomainAliasContractTest pins this catalogue against SecurityService's KnownAliases: a label the studio requires but that list omits gets no verify-dns status at all, and the studio renders a missing status as "pending", so the card sits at "awaiting DNS" forever with nothing anywhere reporting an error. That is what happened to media for four months. And the Careers tab finishes the loop the public site starts. A candidate who found a role there is sent to **************** which parks the uid in an apex-scoped cookie; several redirects and a different host later they land here, and without this they are dropped on a board and have to find the advert again — which is where a hiring funnel loses people. The cookie is cleared whether or not it matched, with the Domain it was written with, because a cookie's identity is (name, domain, path) and an expiry sent without it removes nothing and reports nothing.