Call the period select Posted, the date it filters on and rows show, and point the rail's comments at the ADR and the order's name

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
WolfandClaude Fable 5.1 committed 2026-10-05 09:29:07 +02:00
1 parent 8be59a7ee4
commit 92ad8c2c1b
3 files changed
+23 -9

No files matched your search

+3 -3
View File
@@ -130,9 +130,9 @@
const TRACKS = { "": "Both", ic: "Individual", people: "People" };
// What the list is in the order of. What I'm looking for is the viewing
// agent's want feed score, moved by its votes; Newest is first seen; What
// fits me is the agent's `judge` total, the roles not judged after by CV
// closeness.
// agent's want feed score, moved by its votes; Newest is the posting date;
// What fits me is the agent's `judge` total, the roles not judged after by
// CV closeness.
const SORTS = { score: "What I\u2019m looking for", cv: "What fits me", time: "Newest" };
// The route's `order` for each.
const ORDERS = { score: "score", time: "newest", cv: "cv" };
+9 -6
View File
@@ -46,8 +46,9 @@
<h3 id="viewing-as">Viewing as <a class="linky" href="/settings/agents">agents</a></h3>
<select id="agent" class="rail-select agent-pick" aria-labelledby="viewing-as" hidden></select>
<p id="agent-none" class="rail-note" hidden></p>
{# Every order keeps to the agent's fetch gate (docs/architecture.md,
"5 Feed"), so the filters below only narrow what it passed. #}
{# Every order keeps to the agent's fetch gate (documentation/ADR Fetch
prep and score.md, "5 Feed"), so the filters below only narrow what
it passed. #}
<p id="agent-gate" class="rail-note" hidden></p>
</section>
{# The agent's saved filters (`/api/agents/{id}/filters`), newsdesk's
@@ -74,11 +75,13 @@
</section>
<section>
<h3>Order</h3>
{# Agent match is the viewing agent's final score, Newest is first
seen, CV match the agent's `judge` total against its CV; all carry
that agent's votes and keep to its fetch gate. #}
{# What I'm looking for is the viewing agent's want feed score, Newest
the posting date, What fits me the agent's `judge` total against its
CV; all carry that agent's votes and keep to its fetch gate. The
period counts back over the posting date too, the date a row shows
as its age. #}
<div class="seg" id="sort" role="group" aria-label="Order"></div>
<label class="rail-field" for="period">First seen</label>
<label class="rail-field" for="period">Posted</label>
<select id="period" class="rail-select"></select>
</section>
<section>
+11
View File
@@ -133,3 +133,14 @@ def test_the_reader_excerpt_falls_back_in_the_servers_order() -> None:
description, then teaser, or a teaser-only role's row blanks after Fetch."""
text = (STATIC / "roles.js").read_text("utf-8")
assert "role.summary || role.description || role.teaser" in text
def test_the_period_is_called_posted_as_the_date_it_counts_back_over(
client: TestClient) -> None:
"""`days` keeps `posted_at` within the window, the date a row shows as its
age, so the select is not called First seen."""
rail = client.get("/").text.split('<aside id="rail"', 1)[1].split("</aside>", 1)[0]
assert '<label class="rail-field" for="period">Posted</label>' in rail
assert "First seen" not in rail
template = (STATIC.parent / "templates" / "roles.html").read_text("utf-8")
assert "docs/architecture.md" not in template and "Agent match" not in template