yolo/arr
3
0
Fork 0
Code Issues 12 Pull Requests Actions Packages Projects Releases Wiki Activity

Plainer words: force grab, blocked, and no deck #232

New Issue
Closed
opened 2026-08-25 08:29:33 +01:00 by naps62-yolo · 0 comments
naps62-yolo commented 2026-08-25 08:29:33 +01:00
Owner
Copy Link
Copy Source

Depends on: #230

The UI uses two words the operator does not need and one control that does not
explain itself.

"Waive" leaves the interface. waive + grab becomes force grab. The
waiver stays exactly as it is underneath — §5.7 makes it load-bearing: a soft
fail imports and records a waiver so the file can be recognised later as not
what was asked for, and §5.6 surfaces it on the row. None of that changes. Only
the word the operator reads changes, because "waive" describes the bookkeeping
rather than the act. Where a row is currently badged waived, say something the
operator can act on instead — what was relaxed, not what the record calls it.

"Deck" leaves the interface. The control becomes a search icon (#230). The
release deck keeps its name in DESIGN.md §9.3 and in the code; this is a label
change only, so do not rename identifiers or amend the design document. One
vocabulary in the source, plainer words on screen.

"Blocked" says what it does. Today it is a bare toggle beside wanted and
gives no clue what it blocks. §6.3: "A manual blocked flag stops targeted
search for a title entirely while leaving RSS matching on." That distinction is
the whole point of the flag and the button hides it — an operator would
reasonably read it as "block this title" and be surprised when RSS still
imports something. Make the control carry that, in its accessible name at
minimum and visibly where there is room.

Goes through the impeccable skill. Drive a real browser with agent-browser,
never google-chrome --headless.

Non-goals: no backend change. Waivers are still written, still recorded on
import, and still surfaced through the API under their existing names.

Depends on: #230 The UI uses two words the operator does not need and one control that does not explain itself. **"Waive" leaves the interface.** `waive + grab` becomes **`force grab`**. The waiver stays exactly as it is underneath — §5.7 makes it load-bearing: a soft fail imports and records a `waiver` so the file can be recognised later as *not what was asked for*, and §5.6 surfaces it on the row. None of that changes. Only the word the operator reads changes, because "waive" describes the bookkeeping rather than the act. Where a row is currently badged `waived`, say something the operator can act on instead — what was relaxed, not what the record calls it. **"Deck" leaves the interface.** The control becomes a search icon (#230). The release deck keeps its name in `DESIGN.md` §9.3 and in the code; this is a label change only, so do not rename identifiers or amend the design document. One vocabulary in the source, plainer words on screen. **"Blocked" says what it does.** Today it is a bare toggle beside `wanted` and gives no clue what it blocks. §6.3: *"A manual `blocked` flag stops targeted search for a title entirely while leaving RSS matching on."* That distinction is the whole point of the flag and the button hides it — an operator would reasonably read it as "block this title" and be surprised when RSS still imports something. Make the control carry that, in its accessible name at minimum and visibly where there is room. Goes through the `impeccable` skill. Drive a real browser with `agent-browser`, never `google-chrome --headless`. Non-goals: no backend change. Waivers are still written, still recorded on import, and still surfaced through the API under their existing names.
naps62-yolo added this to the Feedback pass 2 milestone 2026-08-25 08:29:33 +01:00
naps62-yolo added the difficulty/easytype/bugarea/web labels 2026-08-25 08:29:33 +01:00
naps62-yolo added a new dependency 2026-08-25 08:29:33 +01:00
#230 Icon-only controls and readouts
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
arr-api
 area/ci
CI and test harness
 area/compat
arr-compat
 area/core
arr-core
 area/daemon
arr-daemon
 area/db
arr-db
 area/dl
arr-dl
 area/indexer
arr-indexer
 area/infra
workspace and tooling
 area/meta
arr-meta
 area/parse
arr-parse
 area/probe
arr-probe
 area/subs
arr-subs crate: providers, extraction, translation, sync
 area/web
web/
 difficulty/easy
bounded, obvious approach, few files
 difficulty/hard
subtle correctness or cross-cutting
 difficulty/moderate
multiple files, judgement, an interface to design
 difficulty/trivial
one file, mechanical, no design decisions
 phase/1-skeleton
workspace, CI, config, database, empty API and SPA
 phase/2-logic
parsing and policy engine, pure, no network
 phase/3-sourcing
TMDB and Prowlarr, read-only
 phase/4-movies
movies end to end
 phase/5-ui
search, buckets, library views, queues
 phase/6-tv
seasons, episodes, tracking, derived status
 phase/7-people
owner tags and notifications
 phase/8-compat
Jellyseerr shim
 phase/9-subtitles
build order: subtitles, DESIGN.md §15
 type/bug
type/chore
type/feature
type/test
No Label area/web difficulty/easy type/bug
Milestone
No items
No Milestone Feedback pass 2
Projects
Clear projects
No project
Assignees
Clear assignees
hermes (Hermes (agent)) naps62 (Miguel Palhas) naps62-yolo (naps62-yolo (agent))
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Depends on
#230 Icon-only controls and readouts
yolo/arr
Reference: yolo/arr#232
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?