qBit 5.2 caches uploaded .torrent metadata in the session; without QBT_SID the follow-up torrents/add fails 400.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Restores Archie, the server monitor and the full-width bar surface. None of
today's changes fixed the stutter, and the surface refactor regressed it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Reverting the diagnostic. The narrow surface is still the right destination
but it needs the frame band drawn without adding a second full-screen
surface, which is what the reverted attempt got wrong.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The bar's PanelWindow was screen-sized because the frame band and every
panel drew into it. Hyprland blurs that namespace, and blur is recomputed
whenever what is behind the surface changes — with a game underneath, that
is every pixel every frame. Measured at 3440x1440 it cost a third of the
card; the diagnostic shrink took game-running GPU 57% -> 38% and made the
stutter unprovokable.
So the surface is now barWidth at rest and grows to the screen only while a
dropdown, the toast or the launcher is up. exclusiveZone is unchanged, so
windows never reflow on resize. chromeSdf's cutout derives from
screen.width rather than the surface width, so the shader is identical at
both sizes and the narrow surface simply clips it.
The frame band moves to its own background-layer surface, below windows and
matched by no blur rule. Its shader hides (rather than the window
unmapping, which would flicker) while the bar is wide, since chromeSdf then
draws the frame itself and melts panels into it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Archie goes for good — he'd have had to move to the background layer with
the frame band, and that isn't where he belongs. History has him.
The implicitWidth change is a diagnostic, not a design: it clips the frame,
panels, toast and launcher, which all draw into this one screen-sized
surface. Every cost measured today (blur 84->62, SDF 27->17) scales with
that area, so this tests whether shrinking it is worth a real refactor
before committing hours to one.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The SSH qs-stats stream and the router ping both tick every 2s, and each
tick rewrote six Text items in the bar. That surface is the whole screen,
so every tick repainted 3440x1440, reran the SDF shader and made Hyprland
recompute the blur behind it — one late frame, twice a second. Suppressing
both processes was the only change all day that held the frametime graph
flat under deliberate provocation.
Archie was measured innocent and comes back. The OSD anchored its y to the
glance widget, so it now derives from barBottom instead.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
As a user sheet it sorted below userChrome.css and lost every !important to
the copy parsed at startup. Agent sheets sort above ua.css; @-moz-document
keeps that origin off web pages.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
wrapFirefox only copies the exe matching binaryName ("zen-beta"), but Gecko
execs lib/zen-bin-*/zen, a symlink into the unwrapped package. The app dir
resolved there, so mozilla.cfg and defaults/pref were never read.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
fred.zenTheme.autoconfig / .cfg / .status say which of the three stages the
theme watcher reaches, using the one API autoconfig always has.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Firefox 62+ restricts mozilla.cfg to pref()/defaultPref(); Components was
undefined, so the watcher threw on its first line and so did its catch.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The watcher not landing left Zen with no theme at all. Keep the startup copy
so the floor is the old behaviour, and let the watcher fight for the live
update on top.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The autoconfig sandbox has no Services global, so the watcher threw before
registering anything. Go through Components.classes only, resolve ProfD per
pass, and record the result in fred.zenTheme.status.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Gecko has no userChrome.css reload, so wrap zen with a mozilla.cfg script
that registers chrome/zen-theme.css through nsIStyleSheetService and
re-registers it under a cache-busting URI when its mtime moves.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
theme-apply sent reload-config to com.mitchellh.ghostty only, and its
comment claimed the scratchpad 'is the same process'. It is not — that
is the whole point of the --class in settings/hyprland.nix. Ghostty's
--class IS the GTK application id, which is how it forces a separate
instance, and a separate instance owns its own bus name and object path.
So the scratchpad never got the reload and kept the old palette until it
was killed.
Now both are told, scratchpad first and best-effort, since it only
exists once SUPER+Return has been pressed this session.
info/ok/alt were fixed blue/green/purple pulled only 25% toward the
accent, so ram, down and up looked imported on any warm palette. They
exist to tell six stats apart, not to warn, and their captions already
say which is which — so they now tint 55% toward the accent and trade
separation for family. err and warn keep the old 0.25: a critical
temperature is not the place to prioritise harmony.
Not hue-rotation off the accent, which was the obvious approach and is
unstable: it inherits the accent's saturation, collapsing the three into
near-identical greys on a muted wallpaper (minsep 0.107 on 5y39p9) and
blowing them out to neon on a vivid one (0.455 on d8wxw3). Tinting holds
~0.175 on every palette tested.
cpu drops the raw accent for base05 — it was the one fully saturated
value in the column.
base03/base04/base05 were three independent slots off the wallpaper, not
one ink at three strengths. On wallhaven-k8dqr6 the raw ladder is red,
blue and cream; on 5y39p9 base03 is a saturated gold against pale cream.
That is why muted labels read as a second accent and why the shell frame
never quite matched the window border beside it.
base04 and base03 are now base05 mixed toward base00. The two factors and
the mix live in settings/ui.nix and are used by all three consumers:
Theme.qml, theming.nix's hypr.lua (applied at runtime) and hyprland.nix's
build-time fallback. Same trick base01/base02 already used for surfaces.
Verified on 5y39p9: hypr.lua now emits aca888 / 727761 from base05 f1e2b6
against base00 0a1f1c, matching what inkStep computes in the shell.
All three were base03, which is its own wallpaper slot rather than a
step of the ink: on 5y39p9 it is a saturated gold against pale cream,
on k8dqr6 an outright red against cream. So muting the speaker changed
the icon's colour rather than its weight, and the launcher's host and
placeholder read as a second accent.
Dimmed base05 instead, same idiom as the workspace dots.
