dsh-background-by-model 0.7.6 → 0.7.8

package/lib/client.js

@@ -648,11 +648,11 @@ window.__ModuleLoader__.load({
 			"input"
 		];
 		const DEFAULT_PART_OPACITIES = {
-			bg: .85,
-			sidebar: .93,
+			bg: 0,
+			sidebar: .1,
 			card: 1,
-			code: 1,
-			input: 1
+			code: .81,
+			input: .88
 		};
 		/**
 		* Interface blur (px, 0..60), global (Interface page):
@@ -683,7 +683,7 @@ window.__ModuleLoader__.load({
 			chat: 0,
 			trajectory: 0,
 			rightbar: 0,
-			input: 0
+			input: 60
 		};
 		/** Longest allowed switch duration; 0 is a hard cut. */
 		const TRANSITION_MAX_MS = 3e3;
@@ -742,6 +742,9 @@ window.__ModuleLoader__.load({
 		function ruleCanPaint(rule) {
 			return rule.enabled && (ruleSlots(rule).length > 0 || rule.color !== null);
 		}
+		const DEFAULT_CHAT_TEXT_OPACITY = .35;
+		const DEFAULT_TRAJECTORY_OPACITY = .73;
+		const DEFAULT_RIGHTBAR_OPACITY = .45;
 		/**
 		* `#RRGGBB` → the `[h, s, l]` triple every rule stores (`s` and `l` in 0..1), or
 		* null when the string is not a hex color.
@@ -810,20 +813,58 @@ window.__ModuleLoader__.load({
 		function defaultHolidayRules() {
 			return HOLIDAYS.map(defaultHolidayRule);
 		}
-		/** A default config with independent nested objects (never hand out the shared ones). */
+		/**
+		* A rule with nothing in it yet: no picture, no match string, no color.
+		*
+		* Two states need this factory and they are the same state — a fresh install
+		* (see `freshThemeConfig` and `normalizeConfig`), and the "add rule" tile one
+		* entry further down the list.
+		*
+		* Such a rule is deliberately valid rather than half-built: it is skipped by
+		* matching until it has something of its own to paint (`ruleCanPaint` — a picture,
+		* or a theme color), which is what makes a rule nobody has filled in yet invisible
+		* instead of letting an empty background steal the fallback from rule 1.
+		*
+		* It used to be born with an allocated slot and an empty image entry, which is
+		* what put a blank tile at position 1 of a new rule's strip — and, worse, stopped
+		* the picture the user added next from being the first one (a rule paints its
+		* FIRST image). The slot is allocated when the first picture arrives.
+		*/
+		function blankRule(id) {
+			return {
+				id,
+				images: [],
+				match: "",
+				enabled: true,
+				color: null,
+				wallpaperOpacity: 1,
+				blur: 0,
+				rotate: defaultRotation()
+			};
+		}
+		/**
+		* A default config with independent nested objects (never hand out the shared ones).
+		*
+		* The rule list is seeded with one blank rule rather than left empty: "no rules at
+		* all" is not a state the panel should ever open in, because the first thing a new
+		* user has to do is name a match string and drop a picture in — and the drop target
+		* for that is the rule card, which an empty list has no way to show. The empty
+		* state is still reachable (deleting the last rule is a thing the user can mean),
+		* and is described by `ruleNoneHint`.
+		*/
 		function freshThemeConfig() {
 			return {
-				rules: [],
+				rules: [blankRule("r1")],
 				opacities: { ...DEFAULT_PART_OPACITIES },
 				blurs: { ...DEFAULT_PART_BLURS },
 				transition: defaultTransition(),
 				settingsOpacity: 1,
-				chatTextOpacity: 0,
-				trajectoryOpacity: 1,
-				rightbarOpacity: null,
+				chatTextOpacity: DEFAULT_CHAT_TEXT_OPACITY,
+				trajectoryOpacity: DEFAULT_TRAJECTORY_OPACITY,
+				rightbarOpacity: DEFAULT_RIGHTBAR_OPACITY,
 				autoExtract: true,
 				holidays: {
-					enabled: true,
+					enabled: false,
 					items: defaultHolidayRules()
 				}
 			};
@@ -1058,14 +1099,36 @@ window.__ModuleLoader__.load({
 				if (typeof id === "string") stored.set(id, item);
 			}
 			return {
-				enabled: r.enabled !== false,
+				enabled: typeof r.enabled === "boolean" ? r.enabled : false,
 				items: HOLIDAYS.map((def) => normalizeHolidayRule(def, stored.get(def.id)))
 			};
 		}
+		/**
+		* The file-preview panel's own opacity.
+		*
+		* Three states, and the middle one is why this is a function rather than the
+		* one-line fallback every other field gets: a real number is the card's own
+		* value, `null` is "never owned, so follow `opacities.bg`", and a KEY that is not
+		* there at all — a hand-written config, or one written before the option existed
+		* — is the shipped profile's 45% (see DEFAULT_RIGHTBAR_OPACITY).
+		*
+		* `null` has to survive as ITSELF instead of falling through to the default:
+		* every release so far has written it — a panel the user never dragged is
+		* persisted as an explicit `null` — so treating it as "missing" would hand the
+		* shipped 45% to every configuration whose preview panel was following the main
+		* background, a silent change to a setup nobody asked to change. It is also
+		* unreachable from the UI (no control returns to it); it exists for configs that
+		* were written while the shipped default was `null`.
+		*/
+		function normalizeRightbarOpacity(v) {
+			if (v === null) return null;
+			if (typeof v === "number" && isFinite(v)) return clamp01(v, 1);
+			return DEFAULT_RIGHTBAR_OPACITY;
+		}
 		/** Coerce an unknown persisted value into a valid ThemeConfig, falling back per-field. */
 		function normalizeConfig(raw) {
 			const r = raw ?? {};
-			const rules = Array.isArray(r.rules) ? r.rules.map(normalizeRule).filter((x) => x !== null) : [];
+			const rules = Array.isArray(r.rules) ? r.rules.map(normalizeRule).filter((x) => x !== null) : [blankRule("r1")];
 			const ops = r.opacities ?? {};
 			const bl = r.blurs ?? {};
 			const blurs = {};
@@ -1078,9 +1141,9 @@ window.__ModuleLoader__.load({
 				blurs,
 				transition: normalizeTransition(r.transition, legacyFadeMs(r.rules)),
 				settingsOpacity: clamp01(r.settingsOpacity, 1),
-				chatTextOpacity: clamp01(r.chatTextOpacity, 0),
-				trajectoryOpacity: clamp01(r.trajectoryOpacity, 1),
-				rightbarOpacity: typeof r.rightbarOpacity === "number" && isFinite(r.rightbarOpacity) ? clamp01(r.rightbarOpacity, 1) : null,
+				chatTextOpacity: clamp01(r.chatTextOpacity, DEFAULT_CHAT_TEXT_OPACITY),
+				trajectoryOpacity: clamp01(r.trajectoryOpacity, DEFAULT_TRAJECTORY_OPACITY),
+				rightbarOpacity: normalizeRightbarOpacity(r.rightbarOpacity),
 				autoExtract: r.autoExtract !== false,
 				holidays: normalizeHolidays(r.holidays)
 			};
@@ -1223,28 +1286,6 @@ window.__ModuleLoader__.load({
 		function holidayById(id) {
 			return cfg.holidays.items.find((r) => r.id === id) ?? null;
 		}
-		/**
-		* A fresh rule, holding NO image yet.
-		*
-		* It used to be born with an allocated slot and an empty entry, which is what put
-		* a blank tile at position 1 of a new rule's strip — and, worse, stopped the
-		* picture the user added next from being the first one (a rule paints its first
-		* image). A rule with no pictures is a valid state: `ruleCanPaint` (./schema) skips
-		* it — it has no image and no color yet — until either arrives, and the slot is
-		* allocated when the first picture does.
-		*/
-		function newRule(id) {
-			return {
-				id,
-				images: [],
-				match: "",
-				enabled: true,
-				color: null,
-				wallpaperOpacity: 1,
-				blur: 0,
-				rotate: defaultRotation()
-			};
-		}
 		/** Every slot any rule owns — the user's rules and the holiday entries alike. */
 		function takenSlots() {
 			const taken = /* @__PURE__ */ new Set();
@@ -1364,10 +1405,10 @@ window.__ModuleLoader__.load({
 			return clamp01(cfg.settingsOpacity, 1);
 		}
 		function rChatTextOpacity() {
-			return clamp01(cfg.chatTextOpacity, 0);
+			return clamp01(cfg.chatTextOpacity, DEFAULT_CHAT_TEXT_OPACITY);
 		}
 		function rTrajectoryOpacity() {
-			return clamp01(cfg.trajectoryOpacity, 1);
+			return clamp01(cfg.trajectoryOpacity, DEFAULT_TRAJECTORY_OPACITY);
 		}
 		/** Own opacity of the file-preview panel; while unowned it IS the main background's. */
 		function rRightbarOpacity() {
@@ -1392,6 +1433,64 @@ window.__ModuleLoader__.load({
 			rotIndex = 0;
 		}
 		//#endregion
+		//#region src/preset.ts
+		/**
+		* JSON with object keys in a fixed (sorted) order — the same string for the same
+		* value, whatever order the object that carried it happened to build its keys in.
+		*
+		* `JSON.stringify` alone is not an identity for a value that came off the wire and
+		* through a sanitizer: key order is an accident of how the object was assembled,
+		* and a resume that missed on it would silently re-download everything (the safe
+		* direction) while a resume that MATCHED on a value it should not have would be
+		* the unsafe one — so this is deliberately total as well: anything JSON cannot
+		* carry (a function, a `Symbol`, `undefined`) serializes as `null` and an
+		* `undefined` property is skipped, exactly as `JSON.stringify` treats it.
+		*/
+		function canonical(value) {
+			if (Array.isArray(value)) return `[${value.map(canonical).join(",")}]`;
+			if (value !== null && typeof value === "object") return `{${Object.entries(value).filter(([, v]) => v !== void 0).sort(([a], [b]) => a < b ? -1 : a > b ? 1 : 0).map(([k, v]) => `${JSON.stringify(k)}:${canonical(v)}`).join(",")}}`;
+			return JSON.stringify(value) ?? "null";
+		}
+		/**
+		* The identity of one revision of the profile: the manifest's shape version plus
+		* the config, in canonical form.
+		*
+		* The profile is served from a branch, so "the profile" is not a fixed thing: the
+		* bytes a previous attempt is holding are only known to belong to what is being
+		* installed when that config comes back the same. Order-insensitivity is what lets
+		* this be a comparison of VALUES rather than of spellings — `normalizeConfig`
+		* (./schema) rebuilds the config it reads, so pinning the key to the exact key
+		* order the wire happened to use would make the hold useless the moment anything
+		* upstream normalized differently.
+		*/
+		function presetKey(version, config) {
+			return `${version}\n${canonical(config)}`;
+		}
+		/**
+		* The bytes of a failed attempt that may be reused for the revision `key` names.
+		*
+		* A fresh object every time, never the held record itself: the caller fills it in
+		* as the rest of the profile arrives, and handing out the same mutable record
+		* would let a re-fetch of one file edit the state the NEXT attempt resumes from.
+		* An empty answer — nothing held, or held for a different revision — is the honest
+		* one either way: the pool then asks for every slot the config names.
+		*/
+		function presetResume(held, key) {
+			if (held === null || held.key !== key) return {};
+			return { ...held.images };
+		}
+		/**
+		* The slots of `slots` that `images` does not hold yet, in the config's own order.
+		*
+		* Order matters in the only way it can here: it decides which file a worker takes
+		* first, and the files are not the same size. Only names the CONFIG asked for are
+		* ever returned, so a held picture nothing points at — a slot the author removed
+		* from the profile — can never be fetched again or shipped.
+		*/
+		function presetMissing(slots, images) {
+			return slots.filter((slot) => images[slot] === void 0);
+		}
+		//#endregion
 		//#region src/client/rotation.ts
 		/** Dwell-time presets the settings UI offers, in ms. */
 		const ROTATE_PRESETS = [
@@ -2143,7 +2242,10 @@ window.__ModuleLoader__.load({
 .dab-brand:hover .dab-brand-name{color:var(--dsw-alias-brand-primary)}
 .dab-brand-tile{width:30px;height:30px;flex:none;border-radius:9px;display:grid;place-items:center;color:var(--dsw-alias-label-primary-inverted);background:var(--dsw-alias-brand-primary);box-shadow:0 4px 14px -4px var(--dsw-alias-brand-primary)}
 .dab-brand-name{font-size:13px;font-weight:650;letter-spacing:.01em;line-height:1.25}
-.dab-brand-tag{font-size:9px;letter-spacing:.16em;font-weight:600;color:var(--dsw-alias-label-quaternary,var(--dsw-alias-label-tertiary));text-transform:uppercase}
+/* The weak token was written as quaternary-WITH-a-fallback, so this tag has
+   always painted tertiary: the dead name is dropped rather than being kept as
+   decoration nothing resolves to (check:ui rejects the name outright now). */
+.dab-brand-tag{font-size:9px;letter-spacing:.16em;font-weight:600;color:var(--dsw-alias-label-tertiary);text-transform:uppercase}
 .dab-nav-list{position:relative;display:flex;flex-direction:column;gap:4px}
 .dab-nav-ind{position:absolute;left:0;right:0;top:0;height:38px;border-radius:11px;background:var(--dsw-alias-bg-layer-2);border:1px solid var(--dsw-alias-border-l2);background:color-mix(in srgb,var(--dsw-alias-brand-primary) 13%,transparent);border-color:color-mix(in srgb,var(--dsw-alias-brand-primary) 25%,transparent);transition:transform .38s cubic-bezier(.22,1,.36,1)}
 .dab-nav-item{position:relative;z-index:1;display:flex;align-items:center;gap:10px;height:38px;padding:0 12px;border:0;background:none;border-radius:11px;color:var(--dsw-alias-label-tertiary);font-size:13px;cursor:pointer;text-align:left;transition:color .22s ease}
@@ -2196,8 +2298,20 @@ window.__ModuleLoader__.load({
 .dab-num::-webkit-outer-spin-button,.dab-num::-webkit-inner-spin-button{-webkit-appearance:none;margin:0}
 .dab-num{-moz-appearance:textfield;appearance:textfield}
 .dab-urlinput{flex:1;min-width:180px;height:34px;padding:0 12px;border-radius:10px;border:1px solid var(--dsw-alias-border-l2);background:var(--dsw-alias-bg-layer-2);color:var(--dsw-alias-label-primary);font-size:12.5px;outline:none;transition:border-color .2s}
-.dab-urlinput::placeholder{color:var(--dsw-alias-label-quaternary)}
 .dab-urlinput:focus{border-color:var(--dsw-alias-brand-primary);box-shadow:0 0 0 3px color-mix(in srgb,var(--dsw-alias-brand-primary) 18%,transparent)}
+/* Placeholder text is the field's PREDICTION, never its content: the weak caption
+   token, one step below the text it sits in, so an empty box cannot read as a
+   filled one. All three inputs that carry one are listed here (the rule's match
+   field lives further down, in the rule card) rather than each deciding for
+   itself what "empty" looks like.
+   This used to name --dsw-alias-label-quaternary, which this harness defines
+   NOWHERE: an undefined token drops the declaration, and the placeholder then
+   INHERITS the input's own label-primary — the brightest text in the panel,
+   inside a field the user has not typed in. check:ui now fails on any --dsw-…
+   name the installed theme does not publish, so that one cannot come back.
+   label-caption is the token PLACEHOLDER_RULE (../wallpaper) already uses for the
+   composer, so the plugin answers this question in one voice. */
+.dab-num::placeholder,.dab-urlinput::placeholder,.dab-rule-match::placeholder{color:var(--dsw-alias-label-caption)}
 /* Prints the current hex on the color itself. Without the value this was an
  * empty bordered rectangle sitting in the same column as the H/S/L number
  * fields, which made it read as one more — blank — text input; nothing is ever
@@ -2254,7 +2368,6 @@ window.__ModuleLoader__.load({
 .dab-part-head{display:flex;align-items:center;gap:11px;margin-bottom:14px}
 .dab-part-ico{width:32px;height:32px;flex:none;border-radius:10px;display:grid;place-items:center;color:var(--dsw-alias-brand-primary);background:var(--dsw-alias-bg-layer-2);background:color-mix(in srgb,var(--dsw-alias-brand-primary) 12%,transparent)}
 .dab-part-name{font-size:13.5px;font-weight:600}
-.dab-part-badge{margin-left:auto;font-family:var(--dab-mono);font-size:11px;color:var(--dsw-alias-label-tertiary);background:var(--dsw-alias-bg-layer-2);border-radius:99px;padding:3px 9px}
 
 /* ── segmented control ───────────────────────────────────────────────────── */
 .dab-seg{position:relative;display:inline-flex;padding:3px;background:var(--dsw-alias-bg-layer-2);border:1px solid var(--dsw-alias-border-l2);border-radius:11px}
@@ -2383,7 +2496,7 @@ window.__ModuleLoader__.load({
 .dab-pick-item:hover{background:var(--dsw-alias-bg-layer-2);color:var(--dsw-alias-label-primary)}
 .dab-pick-item.is-active{color:var(--dsw-alias-brand-primary);font-weight:600;background:color-mix(in srgb,var(--dsw-alias-brand-primary) 12%,transparent)}
 .dab-pick-match{flex:1;min-width:0;overflow:hidden;text-overflow:ellipsis;white-space:nowrap}
-.dab-pick-n{flex:none;font-family:var(--dsw-mono);font-size:10.5px;opacity:.7}
+.dab-pick-n{flex:none;font-family:var(--dab-mono);font-size:10.5px;opacity:.7}
 
 /* ── one rule editor (the tab panel's content) ─────────────────────────────── */
 .dab-rule-panel{min-height:0}
@@ -2398,7 +2511,6 @@ window.__ModuleLoader__.load({
 .dab-rule-num{font-family:var(--dab-mono);font-size:11px;font-weight:700;color:var(--dsw-alias-label-tertiary);min-width:16px}
 .dab-rule-badge{font-size:10px;font-weight:700;letter-spacing:.04em;text-transform:uppercase;color:var(--dsw-alias-brand-primary);background:color-mix(in srgb,var(--dsw-alias-brand-primary) 14%,transparent);border-radius:99px;padding:2px 8px}
 .dab-rule-match{flex:1;min-width:150px;height:32px;padding:0 11px;border-radius:9px;border:1px solid var(--dsw-alias-border-l2);background:var(--dsw-alias-bg-layer-2);color:var(--dsw-alias-label-primary);font-family:var(--dab-mono);font-size:12.5px;outline:none;transition:border-color .2s,box-shadow .2s}
-.dab-rule-match::placeholder{color:var(--dsw-alias-label-quaternary)}
 .dab-rule-match:focus{border-color:var(--dsw-alias-brand-primary);box-shadow:0 0 0 3px color-mix(in srgb,var(--dsw-alias-brand-primary) 18%,transparent)}
 .dab-icon-btn{width:28px;height:28px;flex:none;display:grid;place-items:center;border-radius:8px;border:1px solid var(--dsw-alias-border-l2);background:transparent;color:var(--dsw-alias-label-tertiary);cursor:pointer;transition:color .2s,border-color .2s,background .2s}
 .dab-icon-btn:hover:not(:disabled){color:var(--dsw-alias-label-primary);border-color:var(--dsw-alias-brand-primary)}
@@ -4573,20 +4685,13 @@ window.__ModuleLoader__.load({
 						children: [
 							/* @__PURE__ */ (0, react_jsx_runtime.jsxs)("div", {
 								className: "dab-part-head",
-								children: [
-									/* @__PURE__ */ (0, react_jsx_runtime.jsx)("div", {
-										className: "dab-part-ico",
-										children: /* @__PURE__ */ (0, react_jsx_runtime.jsx)(Icon, { size: 16 })
-									}),
-									/* @__PURE__ */ (0, react_jsx_runtime.jsx)("div", {
-										className: "dab-part-name",
-										children: t(labelKey)
-									}),
-									/* @__PURE__ */ (0, react_jsx_runtime.jsxs)("span", {
-										className: "dab-part-badge",
-										children: [Math.round(opacity * 100), "%"]
-									})
-								]
+								children: [/* @__PURE__ */ (0, react_jsx_runtime.jsx)("div", {
+									className: "dab-part-ico",
+									children: /* @__PURE__ */ (0, react_jsx_runtime.jsx)(Icon, { size: 16 })
+								}), /* @__PURE__ */ (0, react_jsx_runtime.jsx)("div", {
+									className: "dab-part-name",
+									children: t(labelKey)
+								})]
 							}),
 							/* @__PURE__ */ (0, react_jsx_runtime.jsx)(LiveSlider, {
 								label: t("uiOpacity"),
@@ -7775,6 +7880,20 @@ window.__ModuleLoader__.load({
 				applyActive();
 				return true;
 			};
+			/**
+			* What the last FAILED profile attempt already had in hand.
+			*
+			* Only a failure leaves anything here — a download that completes is applied or
+			* thrown away whole, and holding megabytes of base64 for a re-click that a
+			* second re-download would settle is not a trade this makes. What it buys is the
+			* one case that had no answer at all before: a profile whose sixth of seven files
+			* failed now costs ONE file on the next press instead of seven.
+			*
+			* Held across section re-injections on purpose (it is declared here, in `apply`,
+			* not inside `sectionInject`): the retry is usually the next click of the same
+			* button, but the panel can be closed and reopened between them.
+			*/
+			let presetHeld = null;
 			const sectionInject = (actions) => {
 				bound = actions;
 				sync();
@@ -7785,7 +7904,7 @@ window.__ModuleLoader__.load({
 					readModelFacts,
 					imageOf: (slot) => displayImageOf(slot),
 					addRule: () => {
-						const rule = newRule(nextRuleId());
+						const rule = blankRule(nextRuleId());
 						cfg.rules.push(rule);
 						rulesRev++;
 						persistConfig();
@@ -8120,15 +8239,18 @@ window.__ModuleLoader__.load({
 					* request, up to `PRESET_CONCURRENCY` of them at a time. What the fan-out
 					* buys is wall-clock time — the real profile measured 8.3 s fetched one at
 					* a time against 4.8 s with four in flight — while each file keeps its own
-					* mirror fallback, its own validation, and its own slot name in a failure.
+					* mirror fallback, its own retry rounds (the node half's business, see
+					* ./preset), its own validation, and its own slot name in a failure.
 					*
 					* STRICT, and the pool is what makes that a decision rather than a
 					* formality: the first wallpaper that cannot be had stops the queue, so the
 					* files nobody has asked for yet are never asked for. Whatever was already
-					* in flight finishes and is thrown away. Nothing has been touched at this
-					* point, so "the author renamed a file" arrives as an error naming the file
-					* rather than as a profile that is quietly missing a picture — and that
-					* loudness is the whole reason this feature is allowed to follow a branch.
+					* in flight finishes and is thrown away — but what it FETCHED is kept for the
+					* next press (`presetHeld` below), which is the difference between retrying
+					* one file and retrying the lot. Nothing has been touched at this point, so
+					* "the author renamed a file" arrives as an error naming the file rather
+					* than as a profile that is quietly missing a picture — and that loudness is
+					* the whole reason this feature is allowed to follow a branch.
 					*/
 					fetchRecommended: async (onProgress) => {
 						const head = await fetchPresetConfig();
@@ -8137,17 +8259,22 @@ window.__ModuleLoader__.load({
 							error: head.error
 						};
 						const slots = head.slots;
-						const images = {};
+						const key = presetKey(head.version, head.config);
+						const images = presetResume(presetHeld, key);
+						let bytes = 0;
+						for (const url of Object.values(images)) bytes += url.length;
+						const missing = presetMissing(slots, images);
+						/** Files already in hand from the attempt this one is resuming. */
+						const held = slots.length - missing.length;
 						let next = 0;
 						let done = 0;
-						let bytes = 0;
 						/** Latched by the first worker to fail, so the rest stop asking. */
 						let stopped = false;
-						onProgress?.(0, slots.length);
+						onProgress?.(held, slots.length);
 						const worker = async () => {
 							for (;;) {
-								if (stopped || next >= slots.length) return null;
-								const slot = slots[next++];
+								if (stopped || next >= missing.length) return null;
+								const slot = missing[next++];
 								const got = await fetchPresetImage(slot);
 								if (!got.ok) {
 									stopped = true;
@@ -8156,21 +8283,28 @@ window.__ModuleLoader__.load({
 										slot
 									};
 								}
-								images[slot] = got.dataUrl;
-								bytes += got.dataUrl.length;
-								if (bytes > PRESET_TOTAL_MAX) {
+								if (bytes + got.dataUrl.length > PRESET_TOTAL_MAX) {
 									stopped = true;
 									return { error: "too large" };
 								}
-								onProgress?.(++done, slots.length);
+								images[slot] = got.dataUrl;
+								bytes += got.dataUrl.length;
+								onProgress?.(held + ++done, slots.length);
 							}
 						};
-						const failure = (await Promise.all(Array.from({ length: Math.min(PRESET_CONCURRENCY, slots.length) }, worker))).find((r) => r !== null) ?? null;
-						if (failure !== null) return {
-							ok: false,
-							error: failure.error,
-							slot: failure.slot
-						};
+						const failure = (await Promise.all(Array.from({ length: Math.min(PRESET_CONCURRENCY, missing.length) }, worker))).find((r) => r !== null) ?? null;
+						if (failure !== null) {
+							presetHeld = {
+								key,
+								images
+							};
+							return {
+								ok: false,
+								error: failure.error,
+								slot: failure.slot
+							};
+						}
+						presetHeld = null;
 						return {
 							ok: true,
 							preset: {