The bar, and its popovers

home/desktop/quickshell/bar/. The desktop's bar, the only one; Waybar left in the migration to Quickshell. It is loaded by shell.qml (Bar {}), and the popovers live in files next to it.

It shows: the workspaces per monitor plus the title, the clock, cpu/ram/disk/temp, the GPU, audio (Pipewire), Spotify (Mpris), the network, the VPN, the weather, the tray, notifications.

Hiding the bar (the IPC handler)

It exists because of Flameshot's overlay: on Hyprland a normal WINDOW never covers a top layer, and the bar lives in one, so the overlay shows a FROZEN frame that already contains the bar and the LIVE bar draws on top, giving the "duplicated bar" effect. There is no window rule that solves it (an open feature request, hyprwm/Hyprland#4847), so the only path is hiding. See flameshot.md.

visible: false unmaps the layer surface, so the 30 px strip stops capturing clicks, which matters for selecting a region at the top of the screen.

Do NOT name the handler "show": it collides with the qs ipc show subcommand and the CLI never calls the function. The same trap is documented in shell.qml, in the vpn IpcHandler.

The compact bar on a narrow panel

The three Groups are ANCHORED (left, centerIn, right), and anchors in QML do not push, they let things overlap. On the 2560 px panel that never shows; on the secondary standing on its pivot, 1080 px wide, the right group alone (7 pills plus the tray) lands on top of the centered clock.

compact reads the panel's own WIDTH and not "is this the secondary", so rotating the monitor back restores the full bar with no config change (rule 3). The threshold is 1600 px, which is what the full set needs in the WORST case: the left group reaches around 620 px with a long title and Spotify playing, and the centered group starts at (width - 280) / 2, so below that they touch.

What stays on a compact panel is what a support screen actually needs: the workspaces, the window title and the clock. What goes is either duplicated from the main bar or system state that belongs in ONE place: Spotify, the weather, the notification counter and the whole right group. It is the same split the Quickshell and Waybar communities land on for a secondary bar.

The title's maxWidth is a SHARE of the panel (13%) instead of the old 340 px literal, so it shrinks with the bar instead of being the thing that causes the collision.

The glance band on the standing monitor

dash/Dashboard.qml. The top 30% of the standing secondary, reserved so that no window lands in it.

Why it exists. A 27" panel on its pivot is 597 mm tall, so its top third sits ABOVE eye level for anyone sitting at the desk, while the ergonomic target is 0 to -30 degrees below the horizontal. A window up there is a neck problem, not a layout preference. The split is 30/70 on purpose: 576 px of band against 1344 px of work area, on a 1920 px screen.

How the space is taken: exclusiveZone, not a gap. A workspace rule with gaps_out = { top = N } reserves the same strip, and it was the first attempt, but N would then have to be kept in sync BY HAND with the panel's height, and it only covers the workspaces it names. A layer surface declares its own height and Hyprland tiles below it, so ONE number governs both. That number subtracts the bar's own zone (host.barExclusiveZone) and the two 4 px margins, which is what makes the bar and the band together add up to the 30%.

What earns a place. The top of a standing screen is for what is read in two seconds and never clicked: the time, the month, the machine's four vitals and what is playing. Everything that takes a click stays in the 70%. The notification FEED is deliberately not there, only a bell with the count: a feed in the eyeline is the opposite of a glance surface, so the centre opens on a click and nowhere else.

No new data. Every number is already collected in Bar.qml for the bar and its popovers, so the component takes that Scope as host and reads it. The month is monthCells(), the same function the year popover renders, at 17 px instead of 9.

The horizon. The panel's bottom edge is the CPU of the last 2 minutes, in dash/Horizon.qml. It divides the glance zone from the work zone with the one signal worth catching out of the corner of an eye, instead of with a decorative rule. It is its OWN component and not the shared Sparkline: the band wants a gradient crest, a brighter newest bar and an animated height, and none of that should follow the widget into the popovers, where a flat bar is the right answer.

It carries a CPU · 2 MIN caption because the first person to see it read the shape as audio. A graph with no label invites the wrong guess, and the label costs 10 px of dim text.

It SCROLLS, it does not morph, and that is the whole difference. Animating 60 bar heights on every sample makes the graph writhe for 220 ms and then sit still, which reads as a stutter even though nothing is dropping frames (qs was at 3% of a core while doing it). A new sample shifts the data one step LEFT, so the track jumps one step RIGHT at that same instant and walks back over exactly sysInterval, and the pixels never jump: one animated property instead of sixty, and motion that never stops. The step is width / (window - 1) and not width / window, because the track has to be ONE step wider than the viewport or the left edge shows a sliver of nothing at the start of every cycle.

MEASURED: 3% of a core morphing against 7% scrolling, on a 144 Hz panel. The band is drawing every frame now, forever, which is what that difference buys. If it ever needs to stop costing that, the cheap variant is the same slide over 600 ms with the graph at rest for the remaining 1.4 s.

The date block. The clock shows HH:mm:ss at one size, then the weekday spelled out, then an ISO line (2026-09-15 · Setembro · W38). The order is deliberate: the weekday is what a person wants off a clock, and the ISO date plus the ISO-8601 week are the precise record underneath. isoWeek() counts the week against the year its THURSDAY falls in, which is what puts 01/01 on week 53 of the year before when it lands on a Friday.

host is NOT a required property, and that is not sloppiness. Quickshell's Variants creates the delegate with modelData as the only initial property, so a SECOND required property fails the creation with failed to create variant with object and the layer never appears at all.

The clock

The time AND the date are ALWAYS visible, in the same pill. It used to be a toggle on click: one or the other, and to see the date you had to click twice, there and back. The time comes first and the date goes into the Pill's sub, in a discreet color. A hierarchy, not a separation.

The weekday comes from a local dowAbbr and NOT from Qt's "ddd", because Qt's format depends on the PROCESS' locale, so "sáb" would become "Sat" if the bar came up with no LC_TIME. There is no year; whoever needs it has the calendar on hover.

The system snapshot: one read per tick

The bar used to read the machine through FIVE forks on three cadences: /proc/stat every 2 s, /proc/meminfo every 5 s, sensors -j and the GPU hwmon every 3 s, /proc/net/dev every 2 s. Today it is ONE head -n 200 -v over a fixed list of /proc and sysfs paths.

The trick is head -v itself: with several files it prefixes each one with ==> path <==, so the output is SELF-LABELING and the QML splits it by section, with no marker of our own to keep in sync between the shell and the parser.

MEASURED on 18/08/2026: 9 ms and 16 KB per snapshot, against 11 ms for the sensors -j call ALONE that it removes. Fewer forks and five times the data.

Every rate on the panels (the CPU percentage, the disk's I/O, the throughput, the GPU's watts) is a DELTA between two consecutive snapshots divided by sysInterval, never a number the kernel hands over ready. That is why the interval is a property and not a literal: change it in one place and every rate stays correct.

Reading hwmon directly, and not sensors -j

Two reasons, and the second one is a bug that was live:

1. Each sensor's own limit comes with it. tempN_max is where the part starts throttling and tempN_crit is where it gives up, and without them a panel can only draw temp / 100.
2. sensors -j LOSES data on this machine. The xe chip publishes two entries named card (one with power1_cap, another with energy1_input), and a JSON object cannot hold a repeated key, so whichever parses it keeps only the last: the GPU's power cap disappears on parse.

The chip FAMILIES are matched by prefix (coretemp/k10temp are the CPU, xe/i915/amdgpu the GPU, nvme, acpitz/nct/it87 the board), so another machine does not need a new branch here.

That also fixed a reading that never appeared: the old code looked for a chip named nct* to get the board temperature, and this machine HAS NO nct. It has acpitz. The row was empty for months without ever failing, which is the silent-drift failure rule 16 describes.

The GPU reading

Intel Arc B580 on the xe driver, and the usage percentage does NOT exist: the driver publishes no gpu_busy_percent, and intel_gpu_top only speaks i915 (verified on 18/08/2026: "No device filter specified and no discrete/integrated i915 devices found"). The old bar drew that absence as a literal 0%, which is the same class of lie as the pretty-and-false latency the VPN probe exists to avoid.

What the card DOES publish is measured and real, so that is what the panel shows: the render clock against its ceiling (tile0/gt0/freq0/act_freq against max_freq, 400 to 2850 MHz here), the whole BOARD's power (the energy1_input counter in microjoules, turned into watts by the same delta as every other rate, against the 210 W power1_cap) and the fan's RPM.

energy1 is the board and energy2 is the chip alone; the board is what the power supply actually delivers, so that is the one on screen.

The three system panels

The temperature, usage and network pills opened the SAME popover: a title, a list of label/value, and a bar drawn at value / 100. It answered "how much" and stopped there, while the VPN panel right next to it answered "is this fine, and since when". The three now speak that same language:

Panel	Verdict	Graph	Provenance
UsagePopover.qml	idle to stalling	the CPU over 2 min, plus one bar per thread	the CPU model, cores/threads, uptime
TempsPopover.qml	cool to critical	the hottest sensor over 2 min	how many sensors, and from which chips
NetPopover.qml	offline to steady	throughput mirrored over 2 min	the interface, its type, who manages it

The window is 60 samples at one every 2 s, so two minutes, and it accumulates whether the panel is open or not, because the snapshot that feeds it runs anyway. Opening the panel costs nothing extra, with one exception below.

What each one answers that a number could not

Usage. One bar per THREAD, because an average of 20% is a different machine when it is one core pinned at 100 and when it is twelve at a fifth, and only the shape tells them apart. The load is shown PER THREAD as well: a raw "8" means nothing without knowing there are 12 of them. Memory is counted against MemAvailable with the cache on its own row, since the cache is memory you HAVE and reading MemFree is what starts every "my RAM is full" panic.

The kernel's PSI stall percentages only show up when something actually stalled. A row pinned at 0.0 trains the eye to skip it, and this is precisely the row that has to be noticed the day it moves. Same rule as the VPN panel's errors row.

The heaviest processes are the exception to "costs nothing". ps -e walks all of /proc, so that poll only runs while the panel is OPEN, the same gate the VPN probe uses. It answers the one question an aggregate never can: who is eating the machine. ps itself always reads as 100%, since its CPU time covers its whole tiny life, so it is filtered out in the parser, where it does not fight with the shell quoting.

Temperatures. Every sensor is drawn against ITS OWN ceiling. The old temp / 100 compared the incomparable: a CPU package at 47 of a 100 ceiling and a GPU package at 47 of a 60 one drew exactly the same bar. The row's context now says "throttles at 82, crit at 100", which is the number that decides whether 78 degrees is fine.

The chip's remaining sensors are condensed on ONE line, grouped by family by stripping the trailing number: 6 cores and 12 VRAM channels stay two strings instead of 18 rows. The NVMe's Sensor 2 is one of them on purpose: the drive's thermal thresholds apply to Composite, so that is the headline, and the hotter secondary sensor is detail and not an alarm.

The GPU fan says "stopped", not 0. This card idles at zero RPM and only spins up under load, and a bare 0 rpm reads as a dead fan.

Network. The throughput graph is MIRRORED, download growing down from the top and upload up from the bottom, sharing ONE ceiling. Two scales would be prettier and would lie about which direction is bigger. The floor is 128 KB/s so an idle link is not a dramatic sawtooth, the same reasoning as the VPN graph's 60 ms floor.

The main interface comes from the DEFAULT ROUTE, not from the literal enp7s0 that used to be written into the parser. That is what "main" means, and it works on a machine that never saw this motherboard.

The link probe aims OUTSIDE the ISP (an anycast anchor, 1 packet/s, the same widgets/PingProbe.qml the VPN uses). Whether the cable is plugged in is already answered by the carrier flag and the gateway; what was missing is everything past the router. The verdict follows the VPN's order of the damage: no carrier, then no gateway, then loss, then jitter, then the mean.

The VPN: three surfaces, one source

vpnList holds the RAW list [{id,name,connected}] because the popover needs one row per VPN; vpnConnected/vpnName remain the aggregate the pill shows. A single read feeds both.

That matters: rofi used to reassemble the labels on its own with systemctl is-active, which LIES during nxBender's crash loop, saying "active" with no tunnel existing. See vpn.md.

Connecting and disconnecting uses a Process and not launch(), so we know WHEN it finished: the state is reread right away instead of waiting for the 5 s poll, and vpnBusy holds the panel open and the buttons inert during the action.

The split is intentional: INFORMATION on hover, ACTION on click.

• VpnPopover.qml (click): one row per VPN with a state dot and a Connect/Disconnect toggle, plus "Disconnect all". It REPLACES the rofi menu (vpn menu), which was a LOOSE window in the middle of the screen with no visual relation to the bar and outside the shell's theme. It is a click and not a hover because you click buttons inside it, and a panel that opens on hover closes at the first distraction. Same choice as PowerMenu, which also has actions inside.
• VpnStatsPopover.qml (hover): the quality verdict, a graph of the last minute, latency, jitter, loss, traffic and uptime. It has nothing to click, the same criterion as the calendar and the three system panels.

Both anchor at the SAME point of the bar, so the Bar hides the stats one while the actions menu is open; otherwise one would draw on top of the other, since the mouse stays over the pill the whole time.

Right click on the pill is still the shortcut for taking everything down.

The VPN quality probe

The pill only answered "is there a tunnel?"; what was missing was "and is it any good?", which is the question of somebody with an SSH session or a call depending on it.

TWO SOURCES, on purpose: vpn stats-json brings the STATE (iface, IP, MTU, uptime, bytes, and which host serves as the target) every 20 s, 3 s with the panel open, and the latency comes from a CONTINUOUS probe. With no tunnel none of it runs, so the cost at rest is zero. That is why it did NOT go into status-json, which runs every 5 s all day long just to paint the pill.

Why continuous, and not a burst on every read

MEASURED on 14/08/2026 on the FAI tunnel, and it is what condemned the first version:

Method	mdev	peak	loss resolution
3 packets in 0.6 s	0.4 ms	—	33% (3 packets!)
a 20 s window	3.3 ms	54.7 ms	—

The burst observed 3% of the time, so a 2 s hiccup was invisible in 97% of cases, and 1-3% of real loss showed up as "0%". A pretty, false number is worse than an absent number.

THE COST is negligible and it was measured: 84 B/s, and 30 packets at 1/s gave 0% loss, so the target does not rate-limit at that cadence. The 60-sample window gives real jitter and a loss resolution of 1.7%.

ping is LINE-BUFFERED even when writing into a pipe (verified: one line per second, with no stdbuf), so the stream can be read instead of waiting for it to finish.

Three flags carry weight: -O emits "no answer yet" at timeout, and without it a lost packet would be SILENCE and the series would only hold the ones that came back, an eternal 0% loss; -n skips DNS; -W 1 matches the 1 s interval.

WHAT DISCOVERS THE TARGET is the CLI (system/net/vpn.nix): sweeping routes and testing candidates is shell work, while observing all the time is the work of whoever stays open. With no target this probe simply does not come up and the panel says "no probe".

The watchdog

With -O, ping SPEAKS every second even when the target disappears, so SILENCE is not packet loss: it is the probe broken (a dead process, an interface recreated under it). Without the watchdog the panel would freeze showing the last good window, looking "stable", which is exactly the lie it exists not to tell. It marks the hole in the series AND resurrects the process.

Two QML details that cost debugging

• info ARRIVES from outside (this VPN's object in vpn stats-json) instead of being fetched inside. An inline component does not see the id of the document that declares it, so a root.vpnStats[...] from in there blows up with a ReferenceError and the whole instance is never born. The symptom was vpnProbeStat becoming undefined.
• A new tunnel, or a new target, is a NEW series. Splicing two sessions would draw a step that never existed. The IP goes into the key because the interface's NAME repeats: on a reconnect ppp0 becomes ppp0 again (seen on 14/08/2026, the IP going from 192.168.50.2 to .3), and without it the series would cross the drop as if nothing had happened.

The verdict's cutoffs

Anchored to the MEASURED baseline of the FAI tunnel (14/08/2026, 1 packet/s: a ~34 ms mean, 0.8 ms mdev, 0% loss).

The ORDER is the order of the damage: loss first, since it kills a session; then jitter, then the mean, because 200 ms of steady latency is workable and 40 ms of jagged latency freezes SSH and calls.

The NUMBERS are not guesses: 2% loss is 2 packets lost in the 60-sample window, and one stray packet a minute is far too routine to raise an alarm; a 10 ms mdev is an order of magnitude above what a healthy tunnel measures. It says "measuring…" before 5 samples, because a verdict with 2 packets is guesswork.

The tunnel interface's rate RIGHT NOW comes from the netRates the bar already computes every 2 s from /proc/net/dev, since stats-json does not repeat that calculation. An idle interface does not show up in that list, and "it did not show up" means 0 B/s.

The graph is the reason the panel exists

"Is the VPN steady?" is a question about TIME: a lone "34 ms" does not distinguish a smooth tunnel from one that swung between 30 and 900 ms in the last minute.

One bar per second (60 = the probe's whole window), the most recent on the right, and the scale starts at ZERO: auto-scaling from the minimum would turn 0.5 ms of variation into a dramatic sawtooth, the opposite of an honest read. The ceiling has a 60 ms floor so the normal case does not become a sawtooth either, and goes 15% above the peak when it passes that.

A packet with no answer is a FULL bar in faded red: the hole has to JUMP OUT, not disappear. The test for it is broad because the series' null can arrive as undefined, depending on how the model is converted.

The panel is 360 wide and not 300: in the first version the footer cut the probe's IP ("200.136.209…") and the rows were squeezed. A diagnostics panel with elided data is a contradiction, since whoever opens it is precisely after the detail. The graph carries a legend, because without it the drawing does not say what it covers, and "1 packet/s" is the information that separates this panel from a guess.

The weather

Open-Meteo, and the coordinates plus the WMO code to pt-BR table are the SSOT in my.weather (home/desktop/weather.nix), read through a generated JSON the same way the palette is.

The pill's ICON derives from the integer weather_code, NEVER from the label. It used to regex the en-US prose, so translating the label to pt-BR would have turned every icon into the default cloud in total silence. That trap, the 4-degree disagreement with the lock screen that motivated the SSOT, and the measured failure paths are in weather.md.

The holidays table (rechecked 08/08/2026)

The NAMES stay in pt-BR on purpose: they are the official names of Brazilian holidays, the same class of literal as the city's name. The chrome around them is en-US.

scope is "nac" | "sp" | "sc". off is the offset in days from Easter SUNDAY (the movable dates); otherwise a fixed m/d. fac marks an optional public holiday, which does not guarantee a day off, so it stays discreet in the grid and OUT of "upcoming holidays".

THIS LIST DOES NOT UPDATE ITSELF, and it is the only part of the calendar that does not. The MOVABLE ones derive from Easter and scale forever; the FIXED ones are LAW written by hand. A new law, or the city touching a holiday, leaves the grid wrong IN SILENCE. Review it when news of a new holiday shows up, not by the calendar: 2027 is already covered, because nothing here depends on the year.

The legal bases:

Scope	Basis
nac	Law 662/1949, 6.802/1980 (Aparecida), 9.093/1995 (Good Friday), 14.759/2023 (Consciência Negra, national since 2024, NOT just SP anymore)
sp	State law 9.497/1997 (Revolução Constitucionalista, july 9th)
sc	Municipal law 7.502/1974 (Corpus Christi), Babilônia 15/08, the city's anniversary 04/11

Two traps the calendar websites fall into and this list does not:

1. CARNAVAL and CINZAS are neither a national NOR a municipal holiday in São Carlos. They are an optional public holiday (state decree 70.273 plus the city hall), hence fac: true.
2. CORPUS CHRISTI is a FEDERAL optional public holiday, but a MUNICIPAL holiday here (the law above), which is why it goes in as "sc" and WITHOUT fac. In another city it would be fac.

The check: the non-fac entries add up to 14, which is the number the city hall and the local press publish for São Carlos. If it ever diverges, that is a sign of a new law.

The grid's three signals (28/08/2026)

A day cell encodes THREE independent facts, and each one owns a different signal, never one more color:

Signal	Meaning
A solid chip	A holiday, painted with its scope's color
An outlined chip	An optional public holiday (fac), which stays discreet
A ring plus a glow around the whole cell	TODAY

Today used to be a solid chip in colAccent, and it was NOT findable: accent and blue are the SAME hex in tokyo-night (#7aa2f7) and in catppuccin-mocha (#89b4fa), and blue is the sp scope, so today was pixel for pixel an SP holiday among the other 20 painted days. The fix is not a fourth color, which the next palette would collide with again, but a signal no chip uses.

It also stopped OVERWRITING the holiday: the chip is always the holiday's, so 07/09 shows a red chip inside the ring and Carnaval keeps its outline.

The CURRENT MONTH is the coarse signal, and it works at a different scale: a tinted panel with a border around the whole block, plus a pill behind the name. The eye lands on the block first and only then hunts for the ring inside it, which is why the accent on the name alone was not enough, being too close to colText. The panel's padding is what pushed the popover from 880 to 920 wide.

The calendar's year rollover

updateClock() compares the yyyy-MM-dd against calDayKey, and on the SystemClock's first beat after midnight it rebuilds. It holds for 01/01 too: calYear changes and the whole popover (the header plus the 12 grids) reevaluates, with no rebuild and no restarting the shell.

MEASURED on 08/08/2026 simulating the 31/12/2026 to 01/01/2027 rollover: a 2027 header, "today" on 01/01, Carnaval painted on 08-09/02. If the machine crosses the rollover suspended, the resume falls into the same path.

DO NOT OPTIMIZE THIS INTO MUTATING THE OBJECTS IN PLACE. The popover reads calMap through a binding (Repeater { model: bar.monthCells(...) }), and a QML binding only reevaluates when the PROPERTY is reassigned: writing inside the existing object (calMap[k] = v) emits no signal at all. The calendar would freeze IN SILENCE: nothing breaks, nothing logs, it just stops rolling the year over. Measured in headless qml: reassigning propagates, mutating does not.

The calendar popover itself holds no state; calMap, calUpcoming, monthCells and the holidays live in the Bar and arrive by reference through bar, the same contract as the other popovers.

The workspace click, and the 0.55 dispatch trap

The 0.55 LUA syntax made dispatch a shortcut for hl.dispatch(...), so the old form ("dispatch", "workspace", N) assembles hl.dispatch(workspace 3) and blows up in the parser. The click died in silence, with nothing on screen.

Careful: hl.dsp.workspace is a TABLE, not a function, and calling it gives "attempt to call a table value". What switches workspaces is focus, exactly as in keybinds.lua.

The orphan workspaces of a disconnected secondary (30/08/2026)

Each bar shows ITS monitor's workspaces: 1 to 4 on the primary, 5 to 8 on the secondary. With the secondary gone, Hyprland gathers 5 to 8 onto the primary (it re-homes them by RULE, see hypr.md), but the model was a literal pair of arrays, so those workspaces had NO button anywhere: a window parked on ws 5 stayed on screen with nothing in the bar pointing at it, reachable only by SUPER+5.

wsModelFor fixes the model at the source: the secondary's bar keeps 5 to 8, and the primary's shows 1 to 4 plus whichever of 5 to 8 EXISTS while Theme.secondaryConnected is false. Existing is the right test and not "has windows", because Hyprland destroys an empty workspace, so the extra buttons appear only while there is something to go back to, and the bar returns to four the moment the secondary comes back.

Theme.secondaryConnected reads Quickshell.screens, which follows the hotplug, so the whole thing is a binding and needs no event of its own.

The tray

A StatusNotifier tray with a single background for the icon group. It populates when qs is the watcher, with Waybar gone. Left click activates, middle is secondaryActivate, scroll scrolls, and right opens the native menu.

Icon path resolution: some SNIs (Dropbox, for one) publish the icon as image://icon/<name>?path=<dir> in a hicolor theme Quickshell's provider does not resolve. The bar looks for the real file in <dir> and points at file://. See dropbox.md.

Positioning the native menu: the menu is a layer surface, because a PopupWindow receives no pointer under Hyprland#6682, so it positions itself by SCREEN X and not by anchor.rect: the icon's X inside barContent plus the bar's left margin. The Y is implicit, since it sits under the exclusiveZone. See quickshell.md for the full TrayMenu reasoning.

The xembedsniproxy path (wine/Battle.net, pamac) has no DBusMenu. It was DEAD until 30/07, because the proxy was not installed, so no icon like that ever came to exist. Quickshell's display() refuses items with no menu ("No menu present"), so the bar fires the SNI's native ContextMenu() through the tray-native-menu helper: the proxy forwards the click and the app draws its own menu at the cursor.

The power menu

A taskbar-style "Start button": the NixOS logo in the bar's top left corner, opening lock, log out, suspend, reboot and shut down. No sudo: poweroff/reboot/suspend go through systemd-logind, where an active session is authorized with no password, and logging out goes through uwsm.

The lock brings hyprlock up DIRECTLY (the unit from lockscreen.nix) and only then marks the LockedHint. loginctl lock-session on its own did NOT lock: it only emits the Lock signal, and what listened for it was hypridle, so with hypridle stopped by Sunshine's guard the click became a silent no-op. The start is idempotent, so the lock_cmd hypridle fires on seeing the signal duplicates nothing. See lockscreen.md.

There is also a "darken the screen" action: gamma 0 through hyprsunset, NEVER dpms. It restores itself on mouse or keyboard movement (hypridle's on-resume) or when sliding the brightness. Useful for sleeping with no light in the room. The dpms prohibition is the same one from sunshine.md.