feat(web): say what a pack was abandoned for
A pack that hard-failed at import blacklisted its release, put every episode back to missing and left the season reading 0/10, with nothing on screen joining the two. Every fact was already recorded. The blacklist now carries its reason out of the database: deck rows read `blacklisted · size` instead of a bare `blacklisted`, and say whether the policy turned the file down — relaxable for this title — or the release itself failed, which a retry only repeats. A season whose pack was abandoned says so on its row and above its deck, with the release name, when it failed, and what it failed on. A row the blacklist no longer answers for keeps rendering and claims no reason. Two defects from the integration review of #211 sit in the same code and are fixed here: a waived row threw away the rule it now carries and read a bare `below policy`, and the empty-eligible count called every waived row force-grabbable, since #211 gave those rows the rule `overridable` reads. Verified against a real browser: series detail, both season decks and their buckets, at 1280 and 390 px. Refs #227, #211
This commit is contained in:
@@ -617,6 +617,48 @@ body {
|
||||
vertical-align: baseline;
|
||||
}
|
||||
|
||||
/* #227: a pack abandoned at import, above the candidates. A quiet panel, not
|
||||
an alert: the failure is history the season owes an explanation for, and
|
||||
the operator opened this deck to grab something, not to be shouted at. The
|
||||
tone follows the same reading as the row chips — amber for their own policy
|
||||
floor, red for a release that failed on its own. */
|
||||
.deck-notice {
|
||||
margin: 0 0 var(--space-6);
|
||||
padding: var(--space-3) var(--space-4) var(--space-4);
|
||||
background: var(--panel);
|
||||
border: 1px solid var(--line);
|
||||
border-radius: var(--radius);
|
||||
}
|
||||
|
||||
.deck-notice[data-blacklist="policy"] {
|
||||
background: oklch(from var(--signal-warn) l c h / 7%);
|
||||
border-color: oklch(from var(--signal-warn) l c h / 40%);
|
||||
}
|
||||
|
||||
.deck-notice[data-blacklist="release"] {
|
||||
background: oklch(from var(--signal-fault) l c h / 7%);
|
||||
border-color: oklch(from var(--signal-fault) l c h / 40%);
|
||||
}
|
||||
|
||||
/* the release name is evidence, in the readout face like every other one */
|
||||
.notice-release {
|
||||
margin: 0 0 var(--space-2);
|
||||
overflow-wrap: anywhere;
|
||||
font-size: var(--text-xs);
|
||||
color: var(--ink);
|
||||
}
|
||||
|
||||
.notice-line {
|
||||
margin: 0;
|
||||
max-width: 68ch;
|
||||
font-size: var(--text-sm);
|
||||
color: var(--ink-muted);
|
||||
}
|
||||
|
||||
.notice-line + .notice-line {
|
||||
margin-top: var(--space-2);
|
||||
}
|
||||
|
||||
.deck-group {
|
||||
margin: 0 0 var(--space-8);
|
||||
}
|
||||
@@ -644,6 +686,18 @@ body {
|
||||
color: var(--ink-faint);
|
||||
}
|
||||
|
||||
.deck-notice .deck-label {
|
||||
margin-bottom: var(--space-2);
|
||||
}
|
||||
|
||||
.deck-notice[data-blacklist="policy"] .deck-label {
|
||||
color: var(--signal-warn);
|
||||
}
|
||||
|
||||
.deck-notice[data-blacklist="release"] .deck-label {
|
||||
color: var(--signal-fault);
|
||||
}
|
||||
|
||||
.deck-rows {
|
||||
margin: 0;
|
||||
padding: 0;
|
||||
@@ -719,6 +773,35 @@ body {
|
||||
color: var(--verdict-rejected);
|
||||
}
|
||||
|
||||
/* #227: a blacklisted release was grabbed, downloaded in full and thrown out
|
||||
at import, and the two ways that happens want opposite decisions. The
|
||||
policy turning a file down is the operator's own floor — amber, the hue
|
||||
this app already gives a gap they can act on. The release itself failing is
|
||||
the one case in the deck that is genuinely broken, so it takes fault red;
|
||||
the "never fault red" rule above is about a rejection, and this is not one.
|
||||
A row whose blacklist entry is gone claims nothing and stays slate. */
|
||||
.chip[data-blacklist="policy"] {
|
||||
color: var(--signal-warn);
|
||||
border-color: oklch(from var(--signal-warn) l c h / 55%);
|
||||
}
|
||||
|
||||
.chip[data-blacklist="release"] {
|
||||
color: var(--signal-fault);
|
||||
border-color: oklch(from var(--signal-fault) l c h / 55%);
|
||||
}
|
||||
|
||||
/* a reason written as a sentence is longer than any rule name, and the chips
|
||||
around it are fixed-width columns that must not be pushed off the line
|
||||
(§9.3: no horizontal scroll at any viewport). This one chip wraps instead. */
|
||||
.chip[data-blacklist],
|
||||
.chip[data-flag="import-failed"] {
|
||||
min-width: 0;
|
||||
max-width: 100%;
|
||||
padding-top: var(--space-1);
|
||||
padding-bottom: var(--space-1);
|
||||
overflow-wrap: anywhere;
|
||||
}
|
||||
|
||||
/* media state ramp (§4.2): green on disk, violet downloading, amber wanted
|
||||
and still missing. Unwanted-missing and parked are nothing-happening and
|
||||
stay neutral; `parked` exists so a vanished grab never reads as a gap. */
|
||||
@@ -1199,6 +1282,20 @@ body {
|
||||
border-bottom: 1px solid oklch(from var(--line) l c h / 45%);
|
||||
}
|
||||
|
||||
/* #227: what the blacklisting means for the next move, on its own line under
|
||||
the chips. Only a blacklisted row carries it, so the dense list stays dense
|
||||
everywhere else. */
|
||||
.rel-why {
|
||||
flex-basis: 100%;
|
||||
min-width: 0;
|
||||
font-size: var(--text-xs);
|
||||
color: var(--ink-muted);
|
||||
}
|
||||
|
||||
.rel-why[data-blacklist="release"] {
|
||||
color: oklch(from var(--signal-fault) 0.78 0.1 h);
|
||||
}
|
||||
|
||||
.rel-note {
|
||||
font-size: var(--text-xs);
|
||||
color: var(--ink-muted);
|
||||
@@ -1519,6 +1616,13 @@ body {
|
||||
font-size: var(--text-xs);
|
||||
}
|
||||
|
||||
/* #227: the season the operator's own report was about read `0/10` beside
|
||||
this chip's absence. It sits next to the counts because that number is what
|
||||
looked like nothing had ever been tried. */
|
||||
.chip[data-flag="import-failed"] {
|
||||
cursor: help;
|
||||
}
|
||||
|
||||
/* issue 122: gone upstream while its file remained — a conflict, amber dashed */
|
||||
.chip[data-flag="vanished"] {
|
||||
color: var(--signal-warn);
|
||||
|
||||
Reference in New Issue
Block a user