Miguel Palhas
a6720f4c06
Three words the operator reads change; nothing underneath does. Waivers are still written, recorded and served under their existing names, the `blocked` column and flag keep theirs, and the release deck keeps its name in DESIGN.md §9.3 and in the code. - `waive + grab` reads `force grab`, and its accessible name says which rule the click relaxes. The `waived` bucket reads `below policy`, and so does the verdict chip on its rows — an operator can act on "below policy" and cannot act on the name the record keeps. - A waived import already said what was relaxed for two rules; `size` joins them and the fallback names the rule rather than badging it `waived`. - `blocked` reads `no targeted search`, everywhere the flag surfaces. §6.3 gives it one effect and a bare toggle hid it: the accessible name carries the RSS half at rest, and a note under the controls spells it out while the flag is on. - The season and episode controls are already the #230 search icon; only their labels still said "deck". They now say what the click does. `just ci` passes through the gate: 509 tests, biome, tsc, tokens. Verified in a real browser (agent-browser) on the library, movie detail, series detail, the episode release view, queues and settings, at 1440 and 390 wide — no horizontal scroll at either. Refs #232
arr
One service that replaces Radarr and Sonarr, and later Bazarr, for a single household.
Five .NET services idle at 600-900 MB to run a loop with four steps in it: decide what you want, find it, fetch it, put it where Jellyfin can read it. Each has a configuration surface an order of magnitude larger than the subset anyone uses, and none of them share a model.
This is that loop, once, in Rust.
- Prowlarr stays — it owns tracker auth, Cloudflare bypass and the indexer definitions, and replacing it buys nothing.
- Transmission stays.
- Jellyseerr stays, talking to a thin Radarr-compatible shim.
Status
Design complete, implementation not started. See DESIGN.md for the contract
and the issue tracker for the work.
Documents
DESIGN.md— the contract. Domain model, policy engine, sourcing, import, crate layout, build order.CLAUDE.md— repository conventions, label taxonomy, and how an autonomous driver session should sequence the work.