phase: 08_events_paging_and_copy

All green. Final report:

**Verified (phase 08 — both task files already in `complete/`; this was the final verification pass)**
- `Dash.eventsPager()` in `app.js` (50/page, `1–50 of N` strip, aria-labelled `‹ prev`/`next ›` disabled at the ends, `WeakMap` page state, reset only when the event *set* changes, `EVENT_FEED_LIMIT`=200) with three call sites; `ul.events` bounded to 320px + `overflow-y:auto`; `/api/events` untouched (`le=500`, no silent clamp).
- Live browser against the real fleet: `/system` `1–50 of 121`, `/llm` `1–50 of 200`, `/ups` `1–50 of 200`; container 320px vs scrollHeight 1543/2368; page 2 → `51–100 of 200` and survived two polls; no empty `.sub`/`.faint` container visible on any page; footers carry only measurements (`rates over Δ11.9s · poll 10s`). Fresh artifacts: `data/logs/08-final-{system-head,llm-page,index-page,ups-feed-page2}.png` (32 phase screenshots already present).
- Grep of live served bytes for all 13 deleted flavour fragments + `actions = -`: none survive in HTML or JS.
- `AGENTS.md` carries both new UI-convention rules (flavour-text rule with the `TODO.md:7` cited examples; the event-feed-window rule) and the updated test count.

**Tests / lint (full project 100% green)**
- `bash .agents/validate.sh` → **EXIT=0**: `uv run pytest --cov --cov-fail-under=94` → **624 passed, 9 skipped, coverage 97.91%**; `ruff check src tests agent` → All checks passed; `pyright` → 0 errors; `node --check` ×5 clean; repo hygiene clean.
- `uv run pytest -m live --live` (`.env.dev` sourced) → **9 passed**; `uv pip list --outdated` → empty. Re-ran pytest/ruff/pyright/node after the doc edits → all exit 0.

**Completion criteria**: bounded scroll + 50/page + count footer ✅ (all three feeds, live) · no removed flavour string ✅ · AGENTS.md rule ✅ · `validate.sh` green + screenshots in `data/logs/` ✅.

**Documentation**: full README/AGENTS review against code (env table vs `config.py`/`.env*.example`, script flags, Containerfile uid 10001/8090, chart heights 120/110/160, test count, coverage) — one inaccuracy fixed: README said "Every page's event feed" (the overview has none) → now "The three event feeds (`/system`, `/llm`, `/ups`)"; also restored the missing trailing newline in `TODO.md`. Everything else verified consistent.

**Notes**: paging stays client-side (no API change); the task-02 defect fix in `/ups` setup copy (`NUT_HOST`/`NUT_PORT`, `LISTEN 127.0.0.1`, one `instcmds` per command, never `actions = -`) re-verified against README and live bytes. Pre-existing items intentionally left to their own phases: `ups.test.result: "Done and passed"` rated `warn` (operator's `TODO.md` entry) and the dev-DB `database is locked` retention issue.

**Next pending phase**: `.agents/phases/todo/09_disks_smartctl/`

README.md

@@ -158,7 +158,9 @@ store.py  ── SQLite (WAL): sample(source,host,metric,res,ts) + event ──
   one per stale metric; the list dedupes per (source, metric) and is capped at 12 with a
   marker that says how many it hid.
 * `web/` — four static pages, one stylesheet, hand-rolled SVG charts (`charts.js`). No
-  framework, no CDN, no bundler. The overview (`/`) is exactly two panels — a
+  framework, no CDN, no bundler, and no narration: a page never explains its own pipeline, so
+  the words on screen are the ones you act on — a unit, a `Δ10.0s` provenance tag, a
+  `SIMULATED` badge, or the sentence beside an empty panel. The overview (`/`) is exactly two panels — a
   **Warnings & errors** list built from `/api/summary`'s `alerts` (each row links to the
   dashboard that explains it) and the **Fleet** table — and nothing else: an empty alert
   list reads as an explicit "all clear", and a live problem moves the panel above the
@@ -238,6 +240,13 @@ store.py  ── SQLite (WAL): sample(source,host,metric,res,ts) + event ──
   battery °C) kept below them in smaller muted type because they are what you read *while* the
   UPS is on battery. Health checks, the battery-test buttons (with their `DANGER`
   confirmation) and the NUT variable dump are unchanged, just second.
+  The three event feeds (`/system`, `/llm`, `/ups`) are a **paged window** over the `event`
+  table rather than a printout of it: the list is a bounded box that scrolls, 50 events to a
+  page, with `1–50 of 200` between `‹ prev` and `next ›` (disabled at the ends) underneath.
+  One helper, `Dash.eventsPager()`, renders every feed and each keeps its own row markup; the fetch
+  asks `/api/events` for 200 so there is a page 2 to reach, and the endpoint itself is
+  unchanged. Reading page 3 survives a poll; a refresh that brings new events goes back to
+  page 1, because page 3 of a list that just changed is not the history you were reading.
 
 ## Testing