The feed that looked filtered

The agenticjobs 0.5.0 release brought a filter that worked across multiple formats: HTML, JSON, JSON Feed, RSS, Markdown, and MCP. The query parameter workplace=remote, along with tags=javascript, was used to access the jobs API. Two RSS feeds, however, ignored the filtering parameters, resulting in the entire board being returned.

The test for this bug involved requesting no listings and requiring all surfaces to return nothing. A feed returning nothing when filtered was either correct or obviously broken, while a feed returning everything appeared functional with many results. The critical question was what a filtered everything-feed should contain. The rule established was that tags are the only filter consistent across both halves of the board.

Other factors like workplace, employment type, seniority, agent policy, salary floor, and employers were job-specific and could not be answered by a person. Thus, a job-shaped filter excluded candidates and employers from the feed. The new /jobs.md and /candidates.md endpoints allowed agents to handle HTML or Markdown listings directly, as each listing contained its apply-schema URL.

The rest of the 0.5.0 release included features like a candidates directory, importing jobs from URLs, editing listings without breaking URLs, and tags for filtering on both sides of the board. The SECRET setting, previously thought to require a value, turned out to be nonexistent. Additionally, sessions, magic links, device codes, and passkey challenges were all random tokens stored as hashes, so there was nothing to key.