dashboard: move queued reminders into SCH3DUL3S tab (closes #460)
mara wanted one place for everything that fires at a future time. The QU3U3D R3M1ND3RS section moves out of the SYST3M tab and lands at the bottom of the SCH3DUL3S tab, below QU3U3D SCH3DUL3S. Pure layout change — refreshReminders() and /api/reminders unchanged; the section just lives under a different parent now. Reminders don't contribute to the SCH3DUL3S pill count (kept as "active schedules" only — reminders are self-scheduled and high cardinality; adding them would make the pill noisy). docs/web-ui.md picks up a SCH3DUL3S tab section (the previous docs lumped the schedules subsection under SYST3M, but the tab has been separate since #459); reminders subsection follows schedules in the same tab.
This commit is contained in:
parent
0b92d597f8
commit
4fdc061c9d
2 changed files with 53 additions and 35 deletions
|
|
@ -104,10 +104,12 @@
|
|||
</section>
|
||||
|
||||
<!-- SYST3M: passive / rare-interaction state. Meta inputs (lock
|
||||
bumps), rebuild queue (watch only), queued reminders, kept
|
||||
state from previous tombstoned agents. Headings stay; the
|
||||
per-section content auto-compresses to a one-line summary
|
||||
when empty (separate JS toggle). -->
|
||||
bumps), rebuild queue (watch only), kept state from previous
|
||||
tombstoned agents. Queued reminders moved to the SCH3DUL3S
|
||||
tab in #460 — they're conceptually "fire X at time Y" too,
|
||||
just self-scheduled by agents instead of operator-set.
|
||||
Headings stay; the per-section content auto-compresses to a
|
||||
one-line summary when empty (separate JS toggle). -->
|
||||
<section class="tab-pane" id="tab-pane-system"
|
||||
role="tabpanel" aria-labelledby="tab-system">
|
||||
<h2>◆ M3T4 1NPUTS ◆</h2>
|
||||
|
|
@ -124,13 +126,6 @@
|
|||
<p class="meta">loading…</p>
|
||||
</div>
|
||||
|
||||
<h2>◆ QU3U3D R3M1ND3RS ◆</h2>
|
||||
<div class="divider">══════════════════════════════════════════════════════════════</div>
|
||||
<p class="meta">reminders agents have queued for themselves but not yet delivered. cancel to drop a stuck or unwanted entry.</p>
|
||||
<div id="reminders-section">
|
||||
<p class="meta">loading…</p>
|
||||
</div>
|
||||
|
||||
<h2>◆ K3PT ST4T3 ◆</h2>
|
||||
<div class="divider">══════════════════════════════════════════════════════════════</div>
|
||||
<div id="tombstones-section">
|
||||
|
|
@ -161,6 +156,19 @@
|
|||
<div id="schedules-section">
|
||||
<p class="meta">loading…</p>
|
||||
</div>
|
||||
|
||||
<!-- QU3U3D R3M1ND3RS (#460): self-scheduled agent reminders.
|
||||
Moved here from the SYST3M tab so the operator has one
|
||||
place for everything that fires at a future time —
|
||||
operator-set schedules above, agent-self reminders here.
|
||||
Backed by GET /api/reminders; refresh handled by
|
||||
refreshReminders() (called from refreshState). -->
|
||||
<h2>◆ QU3U3D R3M1ND3RS ◆</h2>
|
||||
<div class="divider">══════════════════════════════════════════════════════════════</div>
|
||||
<p class="meta">reminders agents have queued for themselves but not yet delivered. cancel to drop a stuck or unwanted entry.</p>
|
||||
<div id="reminders-section">
|
||||
<p class="meta">loading…</p>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
<!-- FL0W: lives on its own page now (`/flow.html`). The
|
||||
|
|
|
|||
Loading…
Reference in a new issue