← back to AbramsEgo
build-queue/done/24-replenish.md
29 lines
# AbramsEgo task 24 — REPLENISH: fresh-eyes full-completion audit (Fable 5)
You are the queue replenisher. Read SPEC.md FIRST, then audit the RUNNING dashboard, not the
file bookkeeping.
1. Pull the live surface: `curl -s -u admin:'DW2024!' http://127.0.0.1:9773/api/data` and read
`public/index.html` + `server.js`. Check every SPEC panel (1–8) is present AND wired to real
data (no dead placeholders), and every Steve hard rule holds:
- 🕓 created date+time chip visible on EVERY admin card/row (full ISO in `title=`).
- sort `<select>` + density slider + infinite scroll on every grid that can exceed ~40 rows,
localStorage-persisted. (Officers panel is compliant via the panel-level fetchedAt chip —
officers carry no per-record timestamp; the local fleet list at ~3 procs was deliberately
left without grid controls in task 15 — don't re-flag those.)
- every cost figure labeled; free/local shows `$0 (local)`.
- Verify task 23 (cron model derived from the invoked script — expect ≥3 of the 114 cron
jobs with a non-null `model` in /api/data) actually landed on the live instance.
2. For each REAL gap found (broken data, missing SPEC feature, hard-rule violation): write ONE
surgical <15-min task file to `build-queue/tasks/NN-<slug>.md` (NN starting at 25), following
the style of `build-queue/done/12-officers-datetime-chip.md` — name exact files/lines, one
verify command, one commit line. BOUND: enqueue at most 3 tasks, highest-value first. Also
re-enqueue a copy of this replenisher as the LAST task (next number) ONLY if you enqueued ≥1 task.
3. If NO real gaps: enqueue nothing, do NOT re-enqueue yourself — the loop rests, the build is
at full completion. Don't invent busywork to justify the run.
4. Move this file to `build-queue/done/` and commit
`chore: replenish audit (fable) — <verdict>` with author `steve@designerwallcoverings.com`.
Local only. No deploy, no DNS, no publish — draft any gated need to
~/.claude/yolo-queue/pending-approval/ instead.