# Changelog > The full release history lives here; the **Recent optimizations** section of [README.md](./README.md#recent-optimizations) lists only the two most recent releases (v0.8.2 / v0.8.1). ## v0.8.2 - **The dsh dependency floor moves to the host's own version (`>=0.2.1-alpha.2`)** — `engines.dsh`, the five `dsh-client-*` peers and `dsh-home-paths` still asked for the 0.1.7 generation while the harness in use is 0.2.1-alpha.2. Those five are the packages the host injects into the browser half, so the declaration is what says which generation this code was written against — with the old floor an install could pair it with the previous one. `dsh-invariants` cannot follow (npm has no 0.2.1-alpha.2 of it, and a 0.2.x host does not ship it), so it keeps `>=0.1.7-rc.2`; `@deepseek-ai/cordis` is untouched. The lockfile resolves the dsh family to 0.2.1-alpha.2, and `pnpm test` is ten checks, all green against it. ## v0.8.1 - **The wallpaper layer gains a brightness slider, next to opacity and blur** — the two existing sliders could take a picture down and frost it, but nothing could lift one: an underexposed photo, a night shot or a dim monitor meant editing the file before it went in. The new **背景亮度 / Background brightness** slider sits between them (`0–200%`, `100%` untouched, double-click to reset) and belongs to the rule, exactly like the other two, so each model's wallpaper keeps its own exposure. A festival wallpaper's brightness is yours as well, like its opacity and framing; its slot, mode and colors stay the definition's. - **The two effects that share `filter` are composed in ONE place (a fix waiting to happen)** — brightness and blur are one CSS property, so a second assignment anywhere would have left whichever ran last and silently dropped the other. There is now a single `wpFilter()` that builds the string from the active rule (brightness first, blur second, and the neutral brightness left out so an untouched wallpaper keeps the empty `filter` it always had), and both the full apply and the live drag write through it. The old standalone `setWpBlur` helper had no callers and is now the parameterless `setWpFilter`. - **`brightness` is optional in the shape on purpose** — every config written before this release lacks the key, and the absence has to keep meaning "the picture as it was saved" all the way to the render layer: `normalizeRule` leaves the key off rather than baking a default in (so an upgrade never rewrites a rule list to state what its owner was already looking at), and `rBrightness` is the one place the absence becomes `100`. A literal `undefined` there would have been copied over the live rule by `Object.assign`, which copies keys and not values — the slider reading 100 while the layer held nothing. - **`SCHEMA_VERSION` moves to 7** — the field is new on the node side too, and a schema-6 sanitizer rebuilds each rule from the keys it knows, so a brightness the user just dragged would survive in memory until the next reload and then be gone in silence. Nothing has to be lifted the other way: an absent key already means untouched. A theme file exported by this build carries version 7 in the same change, and a v6 profile still imports. - **Every page the centre column shows gets ONE opacity slider (插件页面)** — 插件, 自动化任务 and the pages a plugin registers of its own (上下文洞察) each bring their own root element and class name, so the item could not be a selector: it is whatever the main slot has mounted, which is what lets one row cover a page that does not exist yet. It is located as the child of `[data-slot="main"]` — a `display:contents` anchor with no box of its own, so the walk steps through box-less elements rather than settling on the first child — and the chat view, the slot's other occupant, is excluded by its own scrollport marker. Opacity only: the frost behind the column is the main background's blur. It ships at 0, where the plugin writes nothing at all. - **A page is tinted through a variable, never an inline style** — the surface is a plugin-owned `--dsh-any-bg-page` read by a rule the plugin already injects, and a page carries only a `data-dab-page` attribute that is dropped again at zero. Nothing is stashed, so nothing can be restored wrong: `.t-XoWW_page`'s own `background: var(--dsw-alias-bg-base)` simply applies again, and the rule's fallback is that same host token, so a mark that outlived its variable could not leave a transparent hole. - **The interface parts are found by name, not by position** — the frame grew a bottom row and a drag handle after the overlay, which quietly turned "the three children before the overlay" into "the centre column, the collapsed right column and the bottom row": the part sliders wrote where nobody looks and the conversation frame stopped answering its slider. Each column is now named by the class suffix its CSS module keeps across builds, and the right column by the host's own `data-rightbar-col`, with the positional answer only as the `??` fallback. - **The Interface page loses every blur slider, and the capability behind them** — ten surfaces each carried a `0–60 px` frost, and none of them did anything worth keeping: what a blurred column frosted was the wallpaper behind it, which the wallpaper layer's own blur already does per rule, and what a blurred panel frosted was a backdrop nobody reads once the panel is translucent. The sliders, the `blurs` field, the underlays, the four plugin-owned CSS variables and the whole `setBlurs` channel are gone together, so the page is opacity and nothing else. The wallpaper's own 背景模糊 is untouched: a rule field, on the other page, and the one doing the visible work. - **`SCHEMA_VERSION` lands on 9: a field added, then one removed** — the page tint is new, and a schema-7 sanitizer rebuilds the config from the keys it knows, so an alpha dragged onto a page would be gone at the next reload in silence (8). The per-surface blur then left the shape entirely, and that step reads the same mechanism backwards: a schema-8 sanitizer would re-add `blurs` from its own defaults — input & controls at 60 px — for a build that no longer has the slider (9). Neither direction needs a lift: an absent `pageOpacity` is the untouched zero, and an absent `blurs` is the state a schema-9 build wants. - **Gates** — `check:node` pins the brightness round trip (the 200 % ceiling, the 0 floor, junk falling back to 100), the absent key surviving a write, and a config that still carries `blurs` loading with the field dropped in silence — a migration, not drift. `check:image-mode` pins the single composer behind all four filter assignments and the page item (the slot anchor, the box-less walk, the conversation's marker, the shipped zero, both apply sites), and its closing section requires the blur field, its writers, its channel and its dictionary key to be absent together with the announced shape past 8. `pnpm test` is ten checks, all passing. ## v0.8.0 - **The bundle is built when the tarball is packed, instead of being committed** — `lib/` was ~1 MB of generated JavaScript in every release and effectively all of this repository's growth, while keeping it in step with `src/` was something a person had to remember. There is no `prepublishOnly` hook here, so a stale bundle shipped in silence and nothing in either flow would have noticed. It is now gitignored and built by `prepack`, which npm runs for both `npm pack` and `npm publish`, so what is published is always built from the tagged source. Nothing changes for anyone installing the package: the same three files arrive, built a minute earlier. - **The `github:` install route is gone, deliberately** — `dsh plugin --profile web add github:HarmlessFunny/dsh-background-by-model` fetched a tree that no longer contains `lib/` and has nothing in it that builds one, so it could only produce a plugin that would not load. npm is the only source now and the `npx` form follows it; the third method, a working copy built from source, says up front that the build is a step you have to run. - **Releases are published from GitHub Actions over OIDC, so the versions carry build provenance** — the npm token is out of the release path entirely, and npm attaches a provenance attestation binding each version to the commit and the workflow that produced it. Every version up to v0.7.10 was uploaded by hand and can claim nothing of the kind; from here they are checkable rather than merely asserted. - **The README and this file are cut back to the register of the v0.3.x entries** — a feature is introduced in a sentence, the ten checks are one line each, and the FAQ keeps all fifteen questions with each answer cut to the sentence carrying the fact. Nothing a user needs was removed; what went was the narration of how each change was arrived at. ## v0.7.10 - **The festival art's cache is keyed by the release the plugin pins, so an updated plugin is answered by a download instead of by the previous generation's bytes** — the cache lived at `holiday-cache/` and `readHolidayAsset` returned any file that existed and was a valid image, with no version comparison, no network and no log line. Pointing a build at a new release of the assets repository therefore changed the URL it would have fetched and nothing about what it returned. `holidayCachePath` now carries the tag (`holiday-cache/v0.1.0/mid-autumn.webp`), which makes the release part of the file's identity: a build pinning a new tag looks in a directory nobody has written to, so the first holiday after an update is a cache miss, and `ls holiday-cache/` answers which generations are on this disk. - **A superseded generation is dropped, after the new art is on disk and never before it.** A versioned key on its own would leave every generation lying there forever — about 730 KB each, including assets a later release stops shipping at all. `pruneHolidayCache` runs at the end of a successful cache write and removes the generation directories that are not this build's tag, so a pinned release that turns out to be unreachable cannot cost a user the art they already had. It is best-effort, and `resetStore` still leaves every generation alone. - **Gates** — `check:node` derives both URL assertions and the cache path from one `REF`, and pins that art missing from the pinned generation is re-downloaded rather than read stale, that a superseded generation is gone once the new art has landed, and that the generation in use is left alone. `pnpm test` is ten checks, all passing. ## v0.7.9 - **Every asset reference is pinned to one release tag of the assets repository (`v0.1.0`), and the three that had drifted apart now agree** — the README's screenshots read `main`, the festival art was pinned to a raw commit hash (`HOLIDAY_ASSETS_COMMIT`), and the recommended profile followed `main` deliberately: three references, three answers to "which bytes is this build looking at". It is now `HOLIDAY_ASSETS_REF = 'v0.1.0'`, with `PRESET_ASSETS_REF` carrying the same string, so one release of `HarmlessFunny/assets` is one version of every byte the plugin fetches — the art, the profile and the screenshots together — in a form a person can read, compare against the tags on GitHub and update in one place. - **The festival art's bytes do not move with the name.** `58a9e107` is an ancestor of `v0.1.0` and both `holiday/*.webp` files are byte-identical between the two revisions, so the download is the same download. What did change is that the raw mirror carries the tag as well, which keeps "both mirrors serve the same revision" true by value rather than by convention. - **The recommended profile gives up "correct it without a release", deliberately** — it followed a branch because its case for immutability was the opposite of the festival art's: a profile fails loudly (the user is looking at the button) where a holiday fails silently on a day nobody is watching. That is what is traded away: correcting one JSON file now costs a tag in `assets`, a new value in `src/index.ts` and a release on npm. And because jsDelivr serves a version reference as immutable, a re-pointed tag takes a purge request instead of a push — which is exactly why `presetKey` survives, since an edge that has not been purged can still answer with the previous bytes of the same URL. - **Gates** — `check:node`'s `revision()` helper matched a 40-character SHA and could not see a tag at all; it now matches beside the repository name (`assets@` and `assets//`), so the two mirrors stay comparable, and both assertions require `v0.1.0` instead of pinning a branch. `pnpm test` is ten checks, all passing. ## v0.7.8 - **A fresh install opens on one blank rule instead of the "no rules yet" screen** — with no config file at all `migrateLegacy` answered `rules: []`, and `normalizeConfig` read that empty array as "the user deleted every rule". Only a **missing** `rules` key now means "nothing has ever been configured", and it is answered with one blank rule — id `r1`, so it is rule 1, the fallback and the tab the panel selects. A key that is there and empty is still the user's own deletion and stays empty. The factory moved into `src/schema.ts` (`blankRule`) and is shared by the shipped default, the sanitizer and the client's "add rule". - **The placeholder was not "too bright": the declaration never applied** — `--dsw-alias-label-quaternary` is defined nowhere in the harness theme, so the declaration was dropped at computed-value time and the placeholder fell back to `inherit`, the input's own `label-primary`. All three placeholder inputs now read `--dsw-alias-label-caption`, the token `PLACEHOLDER_RULE` already hands the composer. Two more dead names went with it: `.dab-brand-tag`'s dead alias, and `.dab-pick-n`'s `--dsw-mono` for `--dab-mono`. - **The recommended profile retries per file, and a failed attempt hands what it fetched to the next one** — a file used to get exactly two chances (one per mirror), so a single 502 on the sixth of seven wallpapers threw away the six good downloads behind it. Every file now gets up to three rounds, waiting 400 ms and then 800 ms, and an attempt that fails holds the bytes it did get, reusing them only while the config comes back as the same value (`presetKey`). 404/403, oversized and timeout are not retried, each for its own reason. The strictness is unchanged — the first file that cannot be had still fails the whole attempt and names the slot — and the button's counter now describes the profile, so a resumed attempt opens on 6/7. - **Gates** — `pnpm test` is ten checks (the new `check:preset`). `check:node` pins the fresh-install rule and the distinction that keeps it from being seeded back, and pins the retry **by request count**: three lines for one transient 503, two requests for a file the host does not have, six for a permanently broken mirror. `check:ui` gains a section requiring every `var(--dsw-…)` the UI reads to be a token the installed theme actually publishes, skipping with a notice when the theme bundle is absent. ## v0.7.7 - **A fresh install starts on the author's own profile, and it needs no network** — the shipped Interface defaults now ARE the numbers `preset/theme-config.json` carries: main background `0%`, left panel `10%`, right panel `45%`, cards `100%`, code `81%`, inputs `88%` with `60 px` of blur, settings `100%`, conversation text `35%`, trajectory `73%`. Every one of those values used to be chosen per key for **safety** rather than for looks, which is why a new install opened on a pale approximation of the host. The constants live in `src/schema.ts` under a note that they are copied from a live data directory. - **`rightbarOpacity` keeps its "never owned" state while a fresh install starts owned** — the preview panel's `null` means "follow `opacities.bg`", and every release so far has written it, because a panel the user never dragged is persisted as an explicit `null`. `normalizeRightbarOpacity` therefore hands the shipped `45%` only to a key that is not there at all; treating `null` as missing would have silently repainted the preview panel of every existing configuration. - **The festival switch ships OFF** — a first install paints what the model rules say and nothing else, and the single switch on the Config page is how the feature is asked for. The recommended profile still turns it **ON**. The sanitizer is now "a real boolean is honoured, anything else takes the shipped default", so the absent field of a config written before the feature existed and junk from a hand-edit both mean OFF. - **The percentage pill in each Interface card is gone** — the number was already on the slider row directly below it, so the card head is the icon and the name again and `.dab-part-badge` goes with it. - **Gates** — `pnpm test` is still nine checks; the new defaults moved `check:code-plate` and `check:node`, whose assertions are written **by value** so that a constant changed without the profile — or the profile changed without the constants — fails a check instead of drifting out of step. ## v0.7.6 - **The rules page turns from a stack of self-growing cards into one tab strip and one editor** — every rule is a tab and exactly one editor is mounted, so the page height is a function of one card plus the strip, whatever the rule count. The tabs carry what only the card head used to show: the number, a thumbnail, the match string, and the two states worth knowing unopened (whether it is in use, and whether it rotates or is off); the strip scrolls sideways rather than wrapping, for the same reason. The `+` and the "which rule" menu sit **outside** the scroller, because inside, the only control that can add a rule scrolled away from the end of a long list. The match tester moved to the profile page, which is what it is about. The two decisions behind the strip are pure and now live in `src/client/rules-view.ts`, pinned by the new `check:rules`. - **The rotation card's controls were reshuffled, at your request** — the Next button and the "On screen 2 / 3" readout moved out of the rotation switch's gate (that readout is the only place the card says which picture is showing, and it vanished with the switch); "also step on a model switch" joined the order row, where all three answer "when does a picture change"; "1 hour" is gone from the dwell presets; the row of eight fixed swatches is deleted with its only readers (the `PALETTE` table and the `.dab-swatch*` rules); and the whole rotation block moved into the second column, below the theme colour, out of the collapsed card's worst spot. - **The festival art stops shipping in the package: it is fetched on the day, and cached by asset** — the two wallpapers (228 KB + 500 KB) were two thirds of the tarball, for a picture that is looked at one day a year. They now live in [`HarmlessFunny/assets`](https://github.com/HarmlessFunny/assets), and the node half downloads, validates and caches one on the first read of the day under `~/.dsh/.dsh-background-by-model-data/holiday-cache/`. The reference is pinned to a commit, never a branch; `cdn.jsdelivr.net` is tried first with raw as the fallback, both at the same revision; a failed download is a normal state, so the model rules keep painting; and a cache entry that is not an image is treated as a miss rather than trusted. The cache stays keyed by **asset** name, deliberately outside the slot namespace, so `writeImage` still refuses a holiday slot. - **A recommended profile, installed in one click** — a third card on the Config page downloads the author's own configuration from the same assets repository: `preset/preset.json` (the shape gate), `preset/theme-config.json` (6.5 KB of readable JSON) and one `preset/modelbg-` file per wallpaper. It was first written as a single theme file with every wallpaper inlined as base64 — 2.9 MB in which 99.8% of the bytes were a picture, and not a document anyone can hand-edit. The request set is derived from the config rather than from a second manifest, so every slot name is checked against `SLOT_RE` and the count is capped; the two holiday slots a config legally names are dropped rather than requested; and one missing wallpaper fails the whole attempt and names the slot. It remains the only destructive action in the panel: the download happens before the question, and the wipe only after the download succeeds. - **The published package drops from 1.1 MB to about 220 kB** — the documentation screenshots moved to the same assets repository and both READMEs reference them by absolute jsDelivr URL (which is what putting them in `files` was for), `screenshots.json` is deleted since nothing consumes it, and `lib/client.js.map` (624 KB) is no longer published though it stays in the repository. Ten files, about 220 kB packed / 690 kB unpacked, against thirteen files and 1.1 MB / 2.0 MB before. ## v0.7.5 - **The layout mode belongs to the picture, not the rule** — 适应 / 填充 / 拉伸 / 平铺 / 居中 was one value per rule covering every picture of a rotation, so a landscape photo and a tall screenshot could not be framed differently. The mode now lives on `images[].bgMode`, read back from the image being painted, and the chip row under the filmstrip edits the image selected there. The row is **disabled** rather than hidden on a rule with no picture. README and README.zh were corrected everywhere they claimed the mode was the rule's. - **`SCHEMA_VERSION` moves to 6, because both directions of this move are silent (a fix)** — a schema-5 host rebuilds every image entry from the keys it knows, so a per-image mode written to it would vanish on the first write; and a schema-6 read of a schema-5 config has to **lift** the rule-level value onto each of its images, or every existing wallpaper would land on the default. `bgMode` joined `LEGACY_RULE_KEYS`, so the host log does not report the field it is deliberately consuming as drift. - **A holiday's image is 填充 by definition** — full-bleed festival art must not letterbox. The mode comes from the definition like the slot and the colours beside it, so a hand-edited value cannot repaint a festival; the framing next to it stays yours. - **The fade only animates what the palette in force writes (a fix)** — reported as a white block fading to black and snapping back, with the white value measured as `237, 243, 254`. That number is the answer: `#edf3fe` is `--dsw-static-deepseek-50`, the host's light-scheme user bubble, and the fade sheet had registered it because `fadeTokenNames()` asks for the **dark** branch's token list while the light branch writes only 35 of its 80 names. The other 45 still belong to the host, which changes them on a schedule of its own — and this plugin is what provoked it, by disposing and re-registering its theme on every colour change. A scope's token is now emitted only when the palette **in force** writes it, and a skin whose `colorScheme` already holds is not rebuilt at all. - **The code block follows the palette, and its plate has an opacity of its own (a fix)** — reported as dark green ink on a near-black plate inside a **light** interface. The host's shiki sheet substitutes `var(--dsw-alias-markdown-code-block)` where it is DECLARED, on `:root`, while the plugin declared those tokens on `body` only, so on the root element there was nothing to read but the host's own colour. The palette rule is now emitted for `:root` as well, `:root` joins the fade scopes, and the plate and its banner are palette tints again. A new **`code`** opacity part drives both surfaces, each through its own plugin-owned variable; it defaults to opaque, which is what a code block is. - **Four small ones (a fix)** — with rotation on, deleting images until one was left kept the switch reading "on" while the panel disabled it below two images, so it could not be turned off either; removing an image now clears `enabled` when fewer than two are left, and `normalizeRule` enforces the same invariant for everything that does not pass through the panel. "切换时长" was printed twice, as a section heading and again as the slider's label. And the profile footer's package name and the brand tile are links to the project's repository, both reading the one address in `repo.ts`, which `check:ui` compares against `package.json`. - **Gates** — `pnpm test` is now **eight** checks. `check:code-plate` and `check:image-mode` join the suite; `check:rotation` gains the switch-and-count invariant, `check:ui` the repository-link agreement, `check:transition` the ownership rule, and `check:repaint` the two lines that arm the fade. ## v0.7.4 - **The controls inside the dialog now change colour on the wallpaper's clock instead of jumping when it finishes (a fix)** — on a theme-colour change, the controls in the settings dialog held the **previous** colour for the whole duration and only took the new one once the background had finished. Measured in a real session: `body`'s own token interpolated correctly across the three seconds, while the active chip's `background-color` was bit-for-bit the OLD value at every sample and only reached the new one after the animation ended. - **What holds is an intermediate element, not "inheritance cannot see an animated value"** — a consumer that merely inherits follows the declaring element frame for frame, which an isolated repro confirms. The plugin armed the **full token list** on three elements, two of which only re-declare the three layer tokens: give an inherited token a transition and that element's transition targets the value it saw when the fade was armed, so it becomes a damped copy of the animation and drags its whole subtree behind it. - **The fix: the transition list is per scope, and a scope only gets the tokens it declares** — `paletteFadeCss` takes `scopes: { selector, tokens }[]` instead of a list of selectors: `body` carries the full list, and the dialog and the trajectory root each carry only the three layer tokens they re-declare. That is not a "do less work" optimisation; a scope handed a name it does not declare copies the lag above into its whole subtree. - **Three surfaces were still snapping, and they are the ones painted from a colour of the plugin's OWN (a fix)** — classifying every pixel of the middle frame against the first and the last puts the settings dialog's own plate on the final colour while every card inside it is still on the first. A card that fades while the plate behind it does not is a different paint path: the plate is painted from `--dsh-any-bg-settings-surface`, a plugin-owned variable written inline, and an **unregistered** variable cannot interpolate at all. The same shape exists twice more — the file-preview panel and the Cordis panel. - **The fix: a scope may name a STANDARD property, and the paint rule and the fade share one selector** — `PaletteFadeScope` gained `properties?: string[]`, emitted into the same `transition` list and deliberately not filtered against the registered names. `fadeScopes()` carries `background-color` for the settings plate and the file-preview panel and `--dsw-specific-menu` for the Cordis panel, and both paint rules and their fade scopes now read one shared constant each, so the half that paints and the half that fades cannot drift apart. Measured in Chromium against the real emitted CSS, all five surfaces sit at the same fraction of the way at every sample — 80.2% at t = 1500 ms, exactly `ease(0.5)`. - **One phenomenon recorded that is NOT the cause** — the probe also shows the fade sheet being rewritten without its `transition` a frame or so after it is armed, and a transition that has already started is not cancelled by removing the declaration. It is not what froze the dialog, but it does mean an element whose transition would only start later gets nothing at all. - **Gates** — `check:transition` gained the two halves of the fade shape: a scope is never given a token it only inherits, a scope with nothing of its own emits no rule, a scope carrying only a standard property still emits its rule and rides the same duration and easing, and `0` ms disarms the property too. `check:repaint` gained the pairing itself: each plugin-painted surface must be painted from its own variable **and** have a fade scope naming the same shared constant, so a fourth one added without a fade becomes a failing check rather than a screenshot nobody took. ## v0.7.3 - **The switch itself became a setting: four effects, an easing and one duration, on the Config page** — every wallpaper change this plugin performs went through one hard-coded cross-fade whose length was read off a field no control could reach. The effects are **cross-fade**, **instant**, **zoom** and **slide** (the last two transform the incoming layer only, so neither costs a byte of extra transfer); instant and a `0` ms duration are the same hard cut rather than one being read as "unset", a `0` is kept as a real value, and `prefers-reduced-motion` is honoured as a **veto** rather than as a shorter animation. The decision is pure (`src/client/transition.ts`), which is what lets `check:transition` pin the failures that throw nothing. - **The card carries a preview swatch, and that is not decoration** — a wallpaper fading into itself is invisible, so replaying the effect on the picture already on screen would show nothing at all: the one way this feature could look broken while working perfectly. The swatch replays the chosen effect at the duration a real switch would use right now. - **There is exactly one duration, and the per-rule choice is gone** — the card's default was "Follow each rule", which named `rotate.fadeMs`, a field that had existed in the shape since 0.7.0 and that no control ever reached. The slider IS the setting now, and `legacyFadeMs` folds the first deliberate value it finds into the global duration when a config that predates the setting is first read; an explicit `durationMs` always wins over a legacy field sitting beside it. - **The interface colour now changes over the same clock as the wallpaper** — the fade is a **registration** problem, not a declaration one, because an unregistered custom property cannot interpolate: `src/client/palette-fade.ts` emits `@property` rules that turn the alias tokens into ``s, plus a `transition` for the elements whose own declarations change with the palette. It is armed **only when the palette itself moved**, because a live transition on a slider drag would make the surface lag behind the pointer, and a token the host does not publish is deliberately left unregistered. - **A light↔dark flip switches instantly, and the wallpaper keeps animating (this one is a fix)** — interpolating between the two palettes walks the whole interface through mid-tones where the ink is wrong in both directions, so the fade is armed only while the **scheme** stays put. The wallpaper is deliberately untouched by that rule: one image fading into another has no scheme to get wrong, so it keeps whatever the switch effect says. - **The ink is written synchronously now, and that was a real bug with exactly one writer (a fix)** — switching a rule to a dark theme colour could leave a panel's text on the **previous** palette while every surface followed the new one: dark ink on a dark panel, cleared only by reloading, with nothing in the log. Every other surface has a second, synchronous writer, so only the token stylesheet could go stale — and its one writer was reachable only from a `requestAnimationFrame` callback wrapped in `catch {}`, where a window that is not rendering swallows the frame. A palette that moved is now written synchronously, in the same task as the surfaces it has to agree with, and the writer logs its failure instead of swallowing it. - **The config shape moved to 5 and an export to format 6, and an older host still cannot eat a profile** — a schema-4 sanitizer REBUILDS the config from the keys it knows, so a stale host process would drop the effect, the easing and the duration on the first write, silently. Theme exports move to format 6; 5 and older still import. - **Gates** — `check:transition` joins `pnpm test`, which is now **six** checks. `check:repaint` gained the three lines this bug was made of, `check:node` the announced schema and the legacy fold, and `check:ui` the new strings and the two new classes. ## v0.7.2 - **The filmstrip IS the control: drag to reorder, double-click to show** — the order used to be reachable only through a pair of ↑ / ↓ arrows and a "make first" button in the row below, which is a second and worse way to say "put this one there". The drop point is a 2px bar drawn INSIDE the tile it precedes, because a bar that took up room would push around the very tiles the pointer is being measured against. Which picture is on screen is the strip's OTHER gesture, and it writes nothing at all — the image being shown is runtime state, not a setting, so the next boot starts at the rule's first image again. - **The order and "which one is on screen" no longer interfere with each other (this one is a fix)** — both old actions ended by moving the image index onto the image they had just moved, so tidying the list swapped the wallpaper as well. `moveRuleImageTo(id, slot, to)` replaces both: it remembers the SLOT being painted before the splice and puts the index back on it afterwards. - **The tile that is on screen lost its ring and kept its dot** — `.is-sel` already rings the tile open for editing, so a second ring put two "selected" tiles in a row of near-identical thumbnails. Being on screen is the dot, and nothing else. - **Every image of a batch upload gets its own color** — a theme color belongs to an IMAGE, and the extraction was addressed by POSITION: `addRuleImages` appended the whole batch and then asked for a color for the last entry alone, so every picture before it kept no color of its own and stayed on the system theme. It is now addressed by the slots the batch itself just appended. - **Copy trimmed, and the framing button moved** — the "Rules" heading and the two explanatory sentences are gone (the panel's title and the `fallback` badge already say it), the labels lost their nouns (`Image 1 / 5`, `Add` / `Replace` / `Remove`), and `Edit position` moved to the end of the layout row — what it opens edits how the picture fills the area, which is what those five modes are about. - **Gates** — `check:repaint` gained the batch section, and `moveRuleImageTo` joins the actions required to sample the winner and close with `repaintIfMoved` while the two deleted actions leave it. `check:ui` covers the new strings and the new class. ## v0.7.1 - **The theme color moved down to the image** — a rule is a rotation through several pictures, and pictures collected for different moods do not share one accent, so every image now carries its own `color: [h, s, l] | null` and the whole color section edits the image selected in the filmstrip. The controls gained one line naming their target ("Applies to the selected image: 2 / 3") and the filmstrip marks the images that already carry a color of their own, because a section that silently retargets is exactly how "I changed the color and nothing happened" starts. No new control and no layout change. - **A rule's own `color` now means exactly one thing: what an image-less rule paints** — it is deliberately NOT a default for the rule's pictures. An image with no color of its own follows the **system theme** rather than inheriting the rule's, which is what makes a rotation through a green picture, a red one and a system-themed one expressible at all. Clearing one image's color therefore clears only that image; the rule keeps its own, ready for the state where it is the only thing left to paint. - **Nothing loses its theme on upgrade, and the distinction is one key** — an image entry written before this release has no `color` key at all, and that missing key is the whole test: it means "this picture never had a color of its own", so the rule's color is lifted onto it once in the shared sanitizer. An explicit `null` means "cleared on purpose" and is never re-inherited over, which is why every write emits the key even when the value is null. - **A rotation step re-emits the interface palette, and that is the bug this feature would otherwise ship with** — the step only repainted the wallpaper, so a per-image color existed in the config and in the panel while the interface behind it kept the previous picture's palette until something else re-ran an apply. The palette apply is now one function (`applyPalette`) called by both a model switch and every step of the rotation. `pnpm check:repaint` fails if either path stops going through it. - **Holidays carry their palette per image too** — a festival's fixed color is written on the holiday *and* on its image, and `normalizeHolidayRule` forces both from the definition on every read. The shape is therefore ready for a holiday that rotates through several pieces of art, as a change to `HOLIDAYS` and its assets rather than a second code path in the render layer. - **The config shape moved to 4, and an older host still cannot eat a profile** — `images[].color` is unknown to a schema-3 `normalizeImage`, which REBUILDS each image entry from the keys it knows, so the color would live in memory until the next reload and then be gone. `SCHEMA_VERSION = 4` is published on every `read`, and a host announcing less lands in the hold-writes path. Exports move to format 5. - **A rule with no picture has exactly one upload target** — the big empty preview tile *is* the button now (a real `