Merge main: the Runs cleanup meets the queue's own idle text

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
WolfandClaude Fable 5.1 committed 2026-09-28 16:24:24 +02:00
commit c63f348dc9
15 files changed
+275 -229

No files matched your search

+19 -24
View File
@@ -1,14 +1,15 @@
{% extends "settings/_layout.html" %}
{% block title %}Sources — roledesk{% endblock %}
{# One page, four sections: the `search` plugin's job board queries, the
`ats` plugin's company boards, the runs that read both, and the message
log. One is shown at a time, the one the URL fragment names (`#runs`), or
Job boards without one; sources.js hides the rest and the rail picks one.
Hidden rather than separate pages, because each section keeps the element
ids it had as a page of its own and its script (sources.js, companies.js,
jobs.js, messages.js) is unchanged: it finds its root or does nothing. The
ids are `SECTIONS` in app/web/pages.py, which the rail links to. #}
{# One page, three sections: the `search` plugin's job board queries, the
`ats` plugin's company boards, and the runs that read both, with the
message log as their last block. One is shown at a time, the one the URL
fragment names (`#runs`) or contains (`#messages`), or Job boards without
one; sources.js hides the rest and the rail picks one. Hidden rather than
separate pages, because each section keeps the element ids it had as a
page of its own and its script (sources.js, companies.js, jobs.js,
messages.js) is unchanged: it finds its root or does nothing. The ids are
`SECTIONS` in app/web/pages.py, which the rail links to. #}
{% block content %}
<h1>Sources</h1>
<p class="lede">Sources are where roles come from: queries on job boards that span companies, and the boards of the companies you follow. Each section is one plugin; the runs read them all.</p>
@@ -109,9 +110,9 @@
<section class="card" id="runs" data-section>
<div class="row-between">
<h2>Runs</h2>
<button type="button" id="pull-now" class="secondary">Pull now</button>
<button type="button" id="pull-now" class="secondary">Run the pull now</button>
</div>
<p class="lede">Every 6 hours the pull reads every board, embed and score rank every role, extract fills in what the best postings say, score runs again with what it filled, and summarise writes the summaries. Change the cadence below.</p>
<p class="lede">On the schedule below the pull reads every board, embed and score rank every role, extract fills in what the best postings say, score runs again with what it filled, and summarise writes the summaries.</p>
<h3>What is running</h3>
{# The element is the queue's own, served by its own router — see
@@ -129,22 +130,16 @@
<script type="module" src="/_jobs/schedules.js"></script>
<desk-schedules add="off"></desk-schedules>
<details class="stage">
<summary>Run one stage</summary>
<div id="kinds" class="buttons">
<span class="muted">loading…</span>
{# The message log, the queue's own through `/api/notices`. `#messages` is
where the old Messages paths and the toasts' "all messages" link land. #}
<div id="messages">
<div class="row-between">
<h3>Problems</h3>
<button type="button" id="clear-all" class="secondary">Clear all</button>
</div>
</details>
</section>
<section class="card" id="messages" data-section>
<div class="row-between">
<h2>Messages</h2>
<button type="button" id="clear-all" class="secondary">Clear all</button>
<p class="lede">What the server said that nobody has cleared, newest first. A message goes when you clear it, or a fortnight after it was last said.</p>
<div id="notices"><span class="muted">loading…</span></div>
</div>
<p class="lede">What the server said that nobody has cleared, newest first. A message goes when you clear it, or a fortnight after it was last said.</p>
<div id="notices"><span class="muted">loading…</span></div>
</section>
{% endblock %}