You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Generalize suggestions prefer host-wide coverage first
The quiet-moment generalizer now offers a host-wide host/*
suggestion before any narrower per-path subset when a host's
entries span more than one path prefix. Previously the detector got
stuck at the deepest common path prefix and could suggest a subset
(api.example.com/v1/users/*) — or nothing at all when each deep
prefix had a single entry — never the pattern covering every request
to the host. Candidate groups are now ranked by how many existing
list entries they subsume, so the broadest generalization is offered
first; declining it walks to the narrower options (closes #186).
TUI pending-list placement + resilient approve
Pending holds now float pinned to the bottom of the operations
pane, like the generalize/suggestion card, so they stay on screen
no matter how many resolved operations scroll above them — no more
scrolling a long history to reach the queue. The cursor enters the
pending region by moving down past the last resolved row and leaves
it by moving up off the top pending row (closes #185).
Approving a hold that was already resolved no longer errors with
"hold not found". A hold can be resolved out from under the
operator (timeout, advisor, double-press) while its row still shows
pending; the hold id is just a pointer. Pressing a / d on such a
row now falls back to writing the request URL to the allow / deny
list — the same write path as the retroactive add on a resolved row —
so the action succeeds (closes #184).