Pulls: Pull now on top, one stage at a time tucked away

Pull now moves from the Sources page's own button to Pulls, wired the same
way (POST /api/jobs {kind: "pull"}), sitting beside what is running. The
schedule follows, then extract, embed and score move under a "Run one
stage" details -- jobs.js still draws them from /api/jobs/kinds, minus
pull, which gets the dedicated button instead of appearing twice.

Messages' lede drops the file's own vocabulary (a "fix", "cleared yet") for
the reader's: a fortnight, not a job kind or a config key.

Found but not fixed: at 375px the refreshed desk-schedules still squeezes
its name and cadence columns to a sliver, because kind/next/last size to
their untruncated content instead of the width their own ellipsis implies.
No page-level horizontal scroll comes of it, so overflow-x: auto stays as
the safety net, with a comment pointing at the cause. The fix belongs in
../boilerplate, ahead of the next refresh -- out of reach from this
worktree.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
WolfandClaude Fable 5.1 committed 2026-09-25 21:52:31 +02:00
1 parent c74546d959
commit a5af47349f
4 files changed
+48 -24

No files matched your search

+14 -2
View File
@@ -192,6 +192,13 @@ button.secondary {
font-size: 0.8rem; font-size: 0.8rem;
} }
/* -- pulls ------------------------------------------------------------------ */
/* "Run one stage" on the Pulls page: extract, embed and score on their own,
under the schedule rather than beside Pull now. */
details.stage summary { cursor: pointer; color: var(--dim); font-size: 0.95rem; font-weight: 600; }
details.stage[open] summary { margin-bottom: 0.75rem; }
/* -- the notice log ------------------------------------------------------- */ /* -- the notice log ------------------------------------------------------- */
.notice { .notice {
@@ -277,8 +284,13 @@ desk-jobs, desk-schedules, auth-account {
--desk-jobs-gap: var(--gap); --desk-jobs-gap: var(--gap);
--desk-jobs-radius: var(--radius); --desk-jobs-radius: var(--radius);
} }
/* The schedule table has no narrow layout of its own yet, and what overflows /* pipeline 21c5faa gave the schedule table a narrow layout, but its
a shadow root widens the page. It scrolls inside its own box instead. */ kind/next/last columns are sized to their untruncated content rather than
the width their own ellipsis implies, which still squeezes the name and
cadence columns to a sliver at 375px -- a fix that has to land in
../boilerplate first, or the next refresh reverts it (see CLAUDE.md). Kept
until then so the odd pixel that still overflows scrolls inside its own
box rather than widening the page. */
desk-schedules { overflow-x: auto; } desk-schedules { overflow-x: auto; }
/* -- roledesk's tabs ------------------------------------------------------ */ /* -- roledesk's tabs ------------------------------------------------------ */
+14 -4
View File
@@ -1,8 +1,11 @@
/* The Pulls page: a button per kind. /* The Pulls page: Pull now on top, one button per remaining kind under
* "Run one stage".
* *
* The list comes from `/api/jobs/kinds`, which is the registry, so a new * The list comes from `/api/jobs/kinds`, which is the registry, so a new
* `@job` in `app/jobs.py` is a new button and this file is not edited. What * `@job` in `app/jobs.py` is a new button and this file is not edited --
* the queue is doing is `<desk-jobs>`'s business, and it draws itself. * except that `pull` itself is pulled out of the list and wired to the
* dedicated button instead of appearing twice. What the queue is doing is
* `<desk-jobs>`'s business, and it draws itself.
* *
* Failures are the server's sentence through `api()`, which toasts it -- so * Failures are the server's sentence through `api()`, which toasts it -- so
* there is no error handling here beyond keeping the button usable. * there is no error handling here beyond keeping the button usable.
@@ -12,7 +15,7 @@
"use strict"; "use strict";
const host = document.getElementById("kinds"); const host = document.getElementById("kinds");
if (!host) return; const pullButton = document.getElementById("pull-now");
async function start(kind, button) { async function start(kind, button) {
button.disabled = true; button.disabled = true;
@@ -26,7 +29,12 @@
} }
} }
if (pullButton) {
pullButton.addEventListener("click", () => start("pull", pullButton));
}
async function draw() { async function draw() {
if (!host) return;
let kinds; let kinds;
try { try {
kinds = await window.api("/api/jobs/kinds"); kinds = await window.api("/api/jobs/kinds");
@@ -34,6 +42,7 @@
host.innerHTML = '<span class="muted">could not read the job kinds</span>'; host.innerHTML = '<span class="muted">could not read the job kinds</span>';
return; return;
} }
kinds = kinds.filter((k) => k.kind !== "pull");
if (!kinds.length) { if (!kinds.length) {
host.innerHTML = '<span class="muted">nothing is registered</span>'; host.innerHTML = '<span class="muted">nothing is registered</span>';
return; return;
@@ -42,6 +51,7 @@
kinds.forEach((k) => { kinds.forEach((k) => {
const button = document.createElement("button"); const button = document.createElement("button");
button.type = "button"; button.type = "button";
button.className = "secondary";
button.textContent = k.label || k.kind; button.textContent = k.label || k.kind;
button.title = k.solo ? `${k.kind} -- one at a time` : k.kind; button.title = k.solo ? `${k.kind} -- one at a time` : k.kind;
button.dataset.kind = k.kind; button.dataset.kind = k.kind;
+1 -1
View File
@@ -5,7 +5,7 @@
<h1>Settings</h1> <h1>Settings</h1>
{% include "settings/_tabs.html" %} {% include "settings/_tabs.html" %}
<p class="lede">What the server said that nobody has cleared yet, newest first, with the fix when there is one. A message goes when you clear it, or two weeks after it was last said.</p> <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>
<section class="card"> <section class="card">
<div class="row-between"> <div class="row-between">
+19 -17
View File
@@ -8,21 +8,16 @@
<p class="lede">Every 6 hours roledesk reads every board and search, then fills in what each posting says, embeds and scores. Change the cadence below.</p> <p class="lede">Every 6 hours roledesk reads every board and search, then fills in what each posting says, embeds and scores. Change the cadence below.</p>
<section class="card"> <section class="card">
<h2>Start something</h2> <div class="row-between">
<div id="kinds" class="buttons"> <h2>What is running</h2>
<span class="muted">loading…</span> <button type="button" id="pull-now" class="secondary">Pull now</button>
</div> </div>
</section> {# The heading and the idle line are the app's: the element takes up no
space while the queue is idle — that is its `idle="hide"` default, and a
<section class="card"> strip that is always there is furniture — and a card with nothing in it
{# The queue's own element, served by its own router. Two lines, and the and nothing above it reads as something that failed to load. The element
module owns what they draw — see pipeline/web/static/jobs.js. and its script are the queue's own, served by its own router — see
pipeline/web/static/jobs.js. #}
The heading is the app's, because the element takes up no space while
nothing is running — that is its `idle="hide"` default, and a strip that
is always there is furniture — and a card with nothing in it and nothing
above it reads as something that failed to load. #}
<h2>What is running</h2>
<p class="muted small" id="idle">Nothing at the moment.</p> <p class="muted small" id="idle">Nothing at the moment.</p>
<script type="module" src="/_jobs/jobs.js"></script> <script type="module" src="/_jobs/jobs.js"></script>
<desk-jobs></desk-jobs> <desk-jobs></desk-jobs>
@@ -30,13 +25,20 @@
<section class="card"> <section class="card">
{# The element and its script are the scheduler's own, served by its own {# The element and its script are the scheduler's own, served by its own
router — see pipeline/web/static/schedules.js. Two lines, as with jobs. router — see pipeline/web/static/schedules.js. A cadence is typed as
A cadence is typed as `every 15m`, `every 6h`, `daily at 06:00` or `every 15m`, `every 6h`, `daily at 06:00` or `weekly mon 07:00`; its add
`weekly mon 07:00`; its add row's placeholder shows two. #} row's placeholder shows two. #}
<h2>Schedule</h2> <h2>Schedule</h2>
<script type="module" src="/_jobs/schedules.js"></script> <script type="module" src="/_jobs/schedules.js"></script>
<desk-schedules></desk-schedules> <desk-schedules></desk-schedules>
</section> </section>
<details class="stage">
<summary>Run one stage</summary>
<div id="kinds" class="buttons">
<span class="muted">loading…</span>
</div>
</details>
{% endblock %} {% endblock %}
{% block scripts %} {% block scripts %}