From d4d8fa6d7a4a84d40cbbaa7afac10d5922b86993 Mon Sep 17 00:00:00 2001 From: iris Date: Fri, 5 Jun 2026 12:47:03 +0200 Subject: [PATCH] =?UTF-8?q?docs(web-ui):=20expand=20Y3R=20C4LL=20questions?= =?UTF-8?q?=20section=20=E2=80=94=20filter=20chips,=20peer=20override,=20a?= =?UTF-8?q?nswer=20form,=20history?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The M1ND H4S QU3STI0NS paragraph was a minimal stub that omitted most of the questions UI: - Filter chips row (all · N / @operator / @peer / per-participant) with localStorage persistence - Peer-targeted questions (agent-to-agent asks) and the operator's ability to override-answer them (0V3RR1D3 button) - Full answer-form anatomy (textarea, option list, merge logic, Enter-to-submit, separate cancel form) - Answered-history collapsible (◆ answ3red (N) details element) Also clarify the P3NDING APPR0VALS paragraph: explicitly mention the pending/history tab pair (it was documented in the Approval card section but not called out at the tab level). --- docs/web-ui/dashboard.md | 34 ++++++++++++++++++++++++++-------- 1 file changed, 26 insertions(+), 8 deletions(-) diff --git a/docs/web-ui/dashboard.md b/docs/web-ui/dashboard.md index ee05f26b..9691bf49 100644 --- a/docs/web-ui/dashboard.md +++ b/docs/web-ui/dashboard.md @@ -59,15 +59,33 @@ share a tab because they're the same concept ("something is waiting on you"). **P3NDING APPR0VALS** — the queue (see "Approval card" below). -The R3QU3ST SP4WN form lives at the top of this section. +The R3QU3ST SP4WN form lives at the top of this section. A +`pending · N` / `history · N` tab pair switches between the live +queue and the last 30 resolved approvals (see "Approval card" for +the history row shape). -**M1ND H4S QU3STI0NS** — pending operator-targeted `ask` -questions (amber pulsing border). Free-text fallback always -rendered alongside any option list; `multi=true` renders options -as checkboxes; submit merges selections + free text -comma-joined. Each row has a `✗ CANC3L` button. Questions with -a `ttl_seconds` show a `⏳ MM:SS` chip; the host-side watchdog -auto-cancels with `[expired]` when the deadline fires. +**M1ND H4S QU3STI0NS** — pending `ask` calls waiting on the +operator, with amber pulsing border. Anatomy of each card: + +- **Filter chips** — `all · N`, `@operator`, `@peer`, plus one + chip per participant name (`@asker` / `@target`). Clicking a + chip narrows the visible list; selection persists in + localStorage so a tab switch doesn't lose the filter. +- **Question card** — timestamp · asker → target · body text + (with file-path links). Operator-targeted questions (`target = + null`) show `▸ ANSW3R`; peer-targeted questions (`target = + agent`) show `⤿ 0V3RR1D3` so the operator can unblock an + agent-to-agent exchange. Questions with a `ttl_seconds` show a + `⏳ MM:SS` live countdown chip; the host-side watchdog resolves + with `answerer = "ttl-watchdog"` on expiry. +- **Answer form** — free-text textarea (Enter = submit, + Shift+Enter = newline) + optional option list (radio for + single-select, checkboxes for `multi=true`). Submit merges + selected options + free text comma-joined into a single + `answer` field. `✗ CANC3L` is a separate form so the submit + merge handler doesn't interfere. +- **◆ answ3red (N)** — collapsible `
` below the pending + list; shows the last 20 resolved questions with their answers. ## SYST3M tab