Merge main: read state and tags meet per-agent votes and affinity

The per-agent migration becomes v6 behind main's v5. A vote still stamps
the role's read_at, tag counts hide the agent's hidden companies, and
/api/filters takes the agent like /api/roles.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
WolfandClaude Fable 5.1 committed 2026-09-28 12:59:41 +02:00
commit c69fb0b6c4
23 files changed
+2270 -717

No files matched your search

+2 -2
View File
@@ -34,7 +34,7 @@ Two tabs, and a cog for settings.
| | |
|---|---|
| **Roles** | open roles, newest or by Best match for one search agent, with filters, votes (▲ like ● neither way ▼ pass) and a Save button. A title opens the role's own read page |
| **Roles** | newsdesk's feed: a filter rail (Show read, Best first or Newest first, first seen, tags, more filters), the open roles with company, place, age, tags and a summary, votes (▲ like ● neither way ▼ pass) and a Save button. A title opens the reader beside the list; on a phone it takes the screen. `j`/`k` move, `Enter` opens, `/` searches |
| **Applications** | the saved roles and their status, each change recorded as an event |
The cog opens `/settings`, one shell with three sub-tabs:
@@ -47,7 +47,7 @@ The cog opens `/settings`, one shell with three sub-tabs:
Likes, hidden companies and votes belong to a search agent, not to the account: two agents rank the same roles differently, and one may hide a company the other favours. An agent also learns from votes: its `taste` weight scores a role by how close it is to the roles the agent liked minus the ones it passed.
A role's read page, `/roles/{uid}`, shows the full posting: the same vote and Save controls, the company's own affinity, and the summary when there is one. A search role's posting is a teaser; its page offers a Fetch button that scrapes the original listing once and stores the text. A Summarise button asks for a short summary of that one role; `config.yaml`'s `summarise:` block turns summarising on for the pull itself, bounded to the top `per_agent` roles of each agent so the cost stays flat.
The reader, `/roles/{uid}`, shows the full posting: the same vote and Save controls, the company's own affinity, the tags and the summary when there is one. Opening a role marks it read, and so does a vote. A search role's posting is a teaser; the reader offers a Fetch button that scrapes the original listing once and stores the text. A Summarise button asks for a short summary of that one role; `config.yaml`'s `summarise:` block turns summarising on for the pull itself, bounded to the top `per_agent` roles of each agent so the cost stays flat.
## Docs