Votes on roles and company affinity move to role_votes and agent_companies,
one row per search agent, so two agents rank the same roles differently. The
score gains taste, the cosine to mean(liked) - mean(passed) of the agent's
votes, as newsdesk ranks articles. The API takes agent on roles, votes and
companies and falls back to the default agent, the enabled one with the
lowest id.
Settings become Search agents (a list again, with New and Delete), Sources
(job boards, company boards and runs with the message log, one section per
plugin) and Account. Old paths answer 301 to their section.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
One migration for the columns the phone UI's votes, summaries and read page
need, so the packages that build those never both touch the schema. The
columns sit before created_at in SCHEMA: SQLite cannot drop a last column
whose preceding comment would then swallow the closing parenthesis, which
the v1 migration test does.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The boilerplate's rule: the deploy kit's Dockerfile, the APP_CONFIG,
APP_PASSWORD and APP_DATA variables and its commands all assume a package
called app, so a project renames its display title and nothing else. The
console script is `app`, and the launch entry runs `uv run app serve --port
8790`. The domain noun stays `role`.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>