Viewing as leads the Roles rail; settings get a rail, agent cards, one Sources section at a time

A search agent is a persona, and every like or pass belongs to the one
being viewed. The rail now opens on Viewing as: a full-width chooser,
the name alone with one agent, a note with none, remembered in the URL
and localStorage. The vote buttons, the reader's affinity control, the
feed, the tag counts and the reader fetch all carry that agent; before,
votes sent none and every one landed on the default agent. Best first
and Newest first are back as the segmented control under Order,
independent of the agent. The rail selects no longer clip descenders:
Chrome ignores line-height on a select, so the fixed box is gone in
favour of padding and a min-height.

Settings render inside a sticky rail (Search agents; Sources with Job
boards, Company boards, Runs, Messages; Account), a strip under the
header on a phone, so Runs is one click away however long the company
list gets. Sources shows one section at a time, chosen by the fragment,
so the old redirects still land. Search agents are cards, newest first:
name, an On/Off switch with its word, the intent in full, the weights,
Edit in place, New agent on top, and a link to Roles as that agent.
Switching one on rescores it.

replace_scores writes nothing for an agent deleted while score was
running, instead of failing the run on the foreign key.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
WolfandClaude Fable 5.1 committed 2026-09-28 15:05:55 +02:00
1 parent 063771d617
commit c4f2bcc0c9
20 files changed
+836 -326

No files matched your search

+8 -7
View File
@@ -1,12 +1,13 @@
{# The frame every page is in. The top bar is `TABS` from app/web/pages.py
plus the cog, and the cog's sub-tabs are `SETTINGS` there: adding a page is
one entry in one of those lists, never a link here.
plus the cog, and the cog's pages are `SETTINGS` there, in the rail
settings/_rail.html draws: adding a page is one entry in one of those
lists, never a link here.
Three blocks let a page go past the default frame, which only the Roles
page does: `body_attrs` for attributes on `<body>`, `header_tools` for
controls between the brand and the tabs (its burger and search box), and
`page` to replace the centred `<main>` with a layout of its own (its rail,
feed and reader). A page setting `active_path` lights the tab for that path
Three blocks let a page go past the default frame: `body_attrs` for
attributes on `<body>`, `header_tools` for controls between the brand and
the tabs (the Roles page's burger and search box), and `page` to replace
the centred `<main>` with a layout of its own (the Roles page's rail, feed
and reader, and the settings rail in settings/_layout.html). A page setting `active_path` lights the tab for that path
rather than its own, which is how `/roles/{uid}` keeps Roles lit. #}
<!doctype html>
<html lang="en">