Doubting "remote", and triaging only what's missing a vote · Job Scout devlog

A job listing tagged remote isn't always remote. Many listings arrive tagged remote by their source while naming only a city, and some mention office days further down the description. Job Scout now marks those listings with an amber "may not be remote" chip that gives the reason: the office days it found, or the city-only location. It's a flag, not a penalty. The ranking is unchanged until a few flagged listings have been checked by hand. On a real day's list, about two thirds of the remote-tagged matches carried the flag.
Triage untriaged. Triage asks several AI models to vote on each job listing. A new button beside "Triage this tab" copies only the listings still in play (not skipped, not applied for) that at least one model hasn't voted on yet, from every tab. Its count updates as listings are marked, so once every model has voted on everything still open, it reads zero. Later the same day, once looser filters had grown the backlog to hundreds, it began copying 100 listings at a time. The same batch comes back until every model has voted on it, then the next moves up.
Federal agencies' own openings aren't ranked as contractors. Government contractors stay ranked below equivalent roles. A federal agency's own remote opening (from USAJOBS) no longer carries that penalty. It already has to pass the same remote filter as everything else.