docs: fix Microsoft.UIVerbs findings (click -> select)
Part of #4041's forgotten remainder (UIVerbs was scoped as pure execution work, no decision needed -- see comment 71586). 29 genuine input-device-neutral rewrites ("click"/"clicking"/"clicked" -> "select"/"selecting"/"selected", a few reworded where a direct verb swap didn't read naturally: "one click from the hub" -> "one step from the hub", "click straight from X into Y" -> "go straight from X into Y", "the operator never clicked" -> "the operator never triggered"). Left 5 hits unfixed, each read in context and genuinely not a device-assumption problem: - docs/process/gotchas.md:439 -- "click-to-unlock screen" names a specific OS lock-screen pattern, not an instruction to the reader. - docs/web-ui/agent.md:377 -- "clicks" describes literal RFB pointer events forwarded by hive-screen-mcp's sendPointer, genuinely mouse-specific. - docs/web-ui/agent.md:78 -- "ctrl/middle-click" names a specific keyboard-modifier + mouse-button combination with no "select" equivalent. - docs/web-ui/dashboard.md:741 -- explicitly contrasts "click (or Enter/Space)" as two named input methods; replacing "click" with "select" would conflate the two the sentence is distinguishing. - docs/web-ui/shape.md:253 -- "swipes in from the right" describes the panel's own slide animation, not a user touch gesture. Verified: fresh `vale --filter '.Name == "Microsoft.UIVerbs"' docs` after the fix shows exactly those 5, `nix fmt` reports 0 changes.
This commit is contained in:
iris
mara
parent
3871749da9
commit
a8fb08a7e8
8 changed files with 29 additions and 29 deletions
|
|
@ -445,7 +445,7 @@ The current capabilities are:
|
|||
Each row is one agent. Columns are the capability names returned by
|
||||
`GET /api/capabilities` as `caps: Vec<String>`. Checking or unchecking
|
||||
boxes only stages the change in-browser; nothing is written until the
|
||||
page-level **save all** button (described below) is clicked. Row
|
||||
page-level **save all** button (described below) is selected. Row
|
||||
values follow the `effective`/`assignments` rule described above.
|
||||
|
||||
**T00L GR0UPS** — per-agent tool-group permissions. Tool groups are
|
||||
|
|
@ -477,7 +477,7 @@ render-time state) and the row carries `data-agent` for dirty-tracking.
|
|||
**Saving — one button for the whole page.** No per-row save
|
||||
buttons exist. A single page-level `.perm-save-bar` with a **save all (N
|
||||
agents)** button sits at the bottom of the pane, enabled only when some
|
||||
checkbox diverges from its baseline. Clicking it diffs every checkbox
|
||||
checkbox diverges from its baseline. Selecting it diffs every checkbox
|
||||
across *both* matrices and POSTs one batch to `POST /api/permissions` as
|
||||
`{ changes: [ { agent, tool_groups?, capabilities? } ] }` — only the
|
||||
perm-types that actually changed for each agent are included (an omitted
|
||||
|
|
@ -548,7 +548,7 @@ The table's last row is a permanent inline creation row:
|
|||
inputs live directly in table cells (targets as checkboxes,
|
||||
body textarea that expands on focus, datetime-local pre-filled
|
||||
to 5 minutes from now, mini d/h/m/s number inputs (blank or
|
||||
all-zero = one-shot), description). Click `＋` to POST to
|
||||
all-zero = one-shot), description). Select `＋` to POST to
|
||||
`/api/schedules` as JSON (or `⌫` to clear the half-filled row);
|
||||
carry-state preserves partially typed inputs across re-renders. The tab pill shows the count of active
|
||||
schedules (at least one live target not yet cancelled).
|
||||
|
|
@ -856,7 +856,7 @@ life). Two consequences for anything rendering it:
|
|||
to rebuild-shaped work — `running_transients()` on the backend is
|
||||
a status-only test (any `Running` node whose payload names a
|
||||
non-empty agent lights a pill), so work the operator never
|
||||
clicked (a meta-update cascade, a crash-recover rebuild, a
|
||||
triggered (a meta-update cascade, a crash-recover rebuild, a
|
||||
lease-exempt `prebuild`) lights the same mechanism.
|
||||
|
||||
Ops with no queue node behind them (destroy, migration) supply
|
||||
|
|
@ -890,13 +890,13 @@ watermarks. When the window value is absent the badge falls back
|
|||
to fixed 100k / 150k thresholds.
|
||||
|
||||
**Per-agent `⋮` overflow menu** — a `⋮` button appears on the right
|
||||
edge of each container row. Clicking it opens a small dropdown with
|
||||
edge of each container row. Selecting it opens a small dropdown with
|
||||
per-agent actions and navigation links. Contents:
|
||||
|
||||
- `↺ R3ST4RT` (running agents only) / `■ ST0P` (running only) /
|
||||
`▶ ST4RT` (stopped only) — single-agent run-state toggles.
|
||||
Identical to the bulk actions on the selection bar but operate
|
||||
on one agent without requiring a selection click.
|
||||
on one agent without requiring a selection.
|
||||
- `↻ R3BU1LD` — always available; queues a rebuild for this agent.
|
||||
- `journal logs →` — opens `/logs.html#agent?agent=<name>` so the
|
||||
operator lands directly in the AGENT log tab pre-filtered to this
|
||||
|
|
@ -942,14 +942,14 @@ OS. Three primitives, all built on the `openDialog` core:
|
|||
— a modal confirm that resolves to `null` on cancel or an object
|
||||
of checkbox states on confirm. Destructive actions pass
|
||||
`danger: true` (the confirm button turns red and the cancel
|
||||
button takes focus). Backdrop click and `Esc` both cancel.
|
||||
button takes focus). Selecting the backdrop and `Esc` both cancel.
|
||||
- `themedPrompt(...)` — a modal with a text input, resolving to the
|
||||
entered string or `null`.
|
||||
- `themedToast(message, { type, ... })` — a non-blocking toast (top-right,
|
||||
`info` / `error` / `ok`) for transient validation + action
|
||||
failures, so an error doesn't trap the operator behind a modal.
|
||||
Single-action errors autodismiss; bulk / partial-failure
|
||||
summaries are sticky (click to dismiss) so they aren't missed.
|
||||
summaries are sticky (select to dismiss) so they aren't missed.
|
||||
|
||||
Every destructive run-state action (`ST0P`, `R3ST4RT`, `R3BU1LD`,
|
||||
`DESTR0Y`, `PURG3`, `M0V3`) routes through `themedConfirm`, on both
|
||||
|
|
@ -1000,13 +1000,13 @@ all no-ops and the layout reads like a plain flat list.
|
|||
|
||||
Bulk actions (`R3ST4RT` / `ST0P` / `ST4RT` / `P4US3` / `R3SUM3` /
|
||||
`R3BU1LD` / `DESTR0Y` / `PURG3`) live here rather than as per-card
|
||||
buttons — see **Container row** above. Clicking an agent's icon
|
||||
buttons — see **Container row** above. Selecting an agent's icon
|
||||
toggles its selection (an in-memory `Set<name>`); `Esc` or the bar's
|
||||
`✕ clear` button drops everything. The selection persists across tab
|
||||
switches in-memory — the bar just hides on non-SW4RM tabs since other
|
||||
tabs don't show the agent cards needed to cross-reference.
|
||||
|
||||
When one or more agents are selected (via icon click), a sticky
|
||||
When one or more agents are selected (via the icon), a sticky
|
||||
frosted-mauve bar slides up from the bottom of the viewport
|
||||
(`#selection-bar`, `position: fixed; bottom: 0`). It shows:
|
||||
|
||||
|
|
@ -1099,7 +1099,7 @@ Per-event tags (`hyperhive:approval:<id>`,
|
|||
`hyperhive:msg:<at>:<rand>`) so distinct events stack in the OS
|
||||
notification center instead of overwriting each other.
|
||||
`console.debug` logs at every block point (unsupported,
|
||||
permission ungranted, muted) for in-browser debugging. Click
|
||||
permission ungranted, muted) for in-browser debugging. Selecting it
|
||||
focuses the dashboard tab. The localStorage key
|
||||
`hyperhive.notify.muted` (`"1"` = muted, absent = unmuted) backs
|
||||
the toggle and silences dispatch without revoking the OS
|
||||
|
|
@ -1123,7 +1123,7 @@ below — some endpoints aren't in it yet.
|
|||
travels to the submitting agent as `HelperEvent::ApprovalResolved.note`
|
||||
and also rides on the dashboard's `ApprovalResolved` event.
|
||||
Dashboard prompts via the themed `themedPrompt()` dialog on
|
||||
click — a resizable `<textarea>` where Enter submits and
|
||||
selection — a resizable `<textarea>` where Enter submits and
|
||||
Shift+Enter inserts a newline (so multi-sentence rejection
|
||||
notes are possible).
|
||||
- `POST /api/{rebuild,kill,restart,start,destroy}/{name}` — lifecycle.
|
||||
|
|
@ -1182,7 +1182,7 @@ below — some endpoints aren't in it yet.
|
|||
and the host form. Canonicalises + verifies the path stays
|
||||
inside the allow-list, refuses anything but a regular file,
|
||||
refuses `/agents/<n>/claude` / `config` subtrees, truncates
|
||||
bodies at 1 MiB. Click-time backing for the inline path-link
|
||||
bodies at 1 MiB. Selection-time backing for the inline path-link
|
||||
preview.
|
||||
|
||||
Detection of which tokens *are* path links is done
|
||||
|
|
@ -1310,7 +1310,7 @@ payload):
|
|||
(the broker row id) and `in_reply_to: Option<i64>` for thread
|
||||
rendering. The dashboard message-flow terminal renders reply
|
||||
rows with a `↳ reply` tag that scroll-highlights the parent
|
||||
row on click. Used by the message-flow terminal renderer and
|
||||
row on selection. Used by the message-flow terminal renderer and
|
||||
the operator-inbox derived state.
|
||||
- `approval_added` (id, agent, approval_kind, sha_short, diff,
|
||||
description) / `approval_resolved` (id, agent, approval_kind,
|
||||
|
|
|
|||
Loading…
Reference in a new issue