Adom Screensaver

@@ -1,15 +1,15 @@-# adom-screensaver — the vibe-coding screensaver+# adom-screensaver, the vibe-coding screensaver  > 🪟 **Windows only.** This runs on your **Windows laptop**, not a Linux/WSL2 container.  Turn your Windows laptop into an always-on home for your Claude Code threads. A branded Adom screensaver that rests your screen, **keeps your machine awake** (network + Remote Control stay-alive), and — while it rests — runs a **live billboard of the latest Adom Wiki drops**, rendered in a+alive), and, while it rests, runs a **live billboard of the latest Adom Wiki drops**, rendered in a real Edge/Chromium engine so it plays **video (silently)** and renders **SVG**, not just static images.  Launch it any time with **Win + Shift + L**. -![Adom Screensaver — the branded splash that explains what it's doing while it rests your screen and keeps your machine awake](/blob/app/adom-screensaver/screenshots/hero.png)+![Adom Screensaver, the branded splash that explains what it's doing while it rests your screen and keeps your machine awake](/blob/app/adom-screensaver/screenshots/hero.png)  Built for the people who fire up their Claude threads before they head to dinner and need them still running when they get back.@@ -21,7 +21,7 @@ adompkg install adom-screensaver ```  **What that does:** on your Adom container (Linux/WSL2) it installs the **skills** and stages the-**prebuilt, signed** Windows binaries — it does **not** run anything there. The screensaver is a+**prebuilt, signed** Windows binaries, it does **not** run anything there. The screensaver is a Windows app. To actually put it on your machine, then ask Claude:  ```@@ -29,7 +29,7 @@ set up the Adom screensaver on my Windows laptop ```  Claude deploys the **prebuilt, code-signed** binaries to your laptop over the `adom-desktop` relay,-wires keep-awake + autostart, registers it as your screensaver, and sets the display-off timing — no+wires keep-awake + autostart, registers it as your screensaver, and sets the display-off timing, no compiler needed, and Windows Defender won't quarantine it (it's signed by "Adom Industries, Inc.").  ## What it does@@ -38,44 +38,44 @@ compiler needed, and Windows Defender won't quarantine it (it's signed by "Adom   `SetThreadExecutionState(ES_CONTINUOUS | ES_SYSTEM_REQUIRED)` on a permanently-alive thread, so   the system stays awake (network + Remote Control survive) while the screen is free to turn off. - **Opens with a gorgeous splash, then the billboards.** A dark cover lifts over ~800ms to reveal-  a power-aware **nerd-stats panel** — live rows for *Power* (plugged / on battery %), *Screen*+  a power-aware **nerd-stats panel**, live rows for *Power* (plugged / on battery %), *Screen*   (powers-off countdown), *Sleep* (never while plugged, or the on-battery countdown), *Keep-awake*   (`ES_SYSTEM_REQUIRED` held → NIC up, `/remote-control` reachable), and *Billboards* (how many are-  loaded + cache size, climbing live) — plus the animated "fetching the latest drops" counter.+  loaded + cache size, climbing live), plus the animated "fetching the latest drops" counter. - **A live Wiki billboard (WebView2).** It then cross-fades through recent apps/skills from the-  Adom Wiki — each with its hero, title, brief, and a **"just ask Claude"** prompt. Because it's a+  Adom Wiki, each with its hero, title, brief, and a **"just ask Claude"** prompt. Because it's a   real browser tile it **plays webm video muted + looped** and renders **SVG**. Hero images/SVGs are-  **truly cached to disk** so they paint instantly and survive offline (video streams — too large to+  **truly cached to disk** so they paint instantly and survive offline (video streams, too large to   cache). Order is **re-shuffled every run**. Footer shows power + the display-off countdown.-- **Rests the panel — no burn-in.** When your display-off time arrives, the saver **pauses all+- **Rests the panel, no burn-in.** When your display-off time arrives, the saver **pauses all   video** (releasing the browser's display wake-lock that would otherwise keep the screen lit),-  **blanks to pure black**, and **powers the panel off** — while keep-awake holds the machine ++  **blanks to pure black**, and **powers the panel off**, while keep-awake holds the machine +   network alive. It does *not* keep cycling bright billboards on a panel that's meant to be off.   A 60-second heartbeat to `wv.log` records exactly what it did overnight. - **Both wikis, with a migration nudge.** It pulls **Wiki v2** (canonical) *and* **Wiki v1**   (legacy). If a page is on both, it shows the v2 version; v1-only cards carry an *"On Wiki v1 ·-  nudge the team to migrate to v2"* kicker — so the screensaver doubles as a gentle prod to+  nudge the team to migrate to v2"* kicker, so the screensaver doubles as a gentle prod to   finish the v1 → v2 migration. - **Honest dimming.** On laptops where software can't dim the backlight (e.g. ASUS ROG dGPU/MUX),-  it doesn't pretend to — the on-screen dim is cosmetic (the billboard rests at ~70% brightness); the **real backlight-off is+  it doesn't pretend to, the on-screen dim is cosmetic (the billboard rests at ~70% brightness); the **real backlight-off is   Windows' display-off timeout**, which genuinely powers the LEDs down with a clean keypress wake.-- **Instant wake.** Move the mouse and the billboards are gone **immediately** — the window hides+- **Instant wake.** Move the mouse and the billboards are gone **immediately**, the window hides   and the browser tears down in the background (fading a layered window over a live WebView2/video is   slow and would lag the dismiss, so it doesn't). The lightweight opening phase still fades out   gracefully. **Never plays audio.** - **Branded fade-to-black open.** The screensaver fades up from your desktop with a small dark-grey   Adom mark centered, which then fades itself to black before the splash takes over.-- **Launch on demand — Win + Shift + L.** A global hotkey starts the screensaver instantly (the+- **Launch on demand, Win + Shift + L.** A global hotkey starts the screensaver instantly (the   manual counterpart to the idle timer, the way `Win + L` is for lock). Contributed by Drew as-  `adom-screensaver-hotkey` and folded in as a first-class feature — toggleable from the+  `adom-screensaver-hotkey` and folded in as a first-class feature, toggleable from the   preferences screen if it ever collides with another shortcut. - **Lid-close rides through; no needless lock.** Closing the lid no longer slams the machine to-  sleep — on AC it does nothing, on battery Windows' own idle timer (e.g. 30 min) is the give-up-  clock — so a quick close-and-carry doesn't kill your threads. And because the screensaver only+  sleep, on AC it does nothing, on battery Windows' own idle timer (e.g. 30 min) is the give-up+  clock, so a quick close-and-carry doesn't kill your threads. And because the screensaver only   *rests the screen* (it doesn't sleep), it **doesn't throw a lock screen**; a real sleep-then-wake   still asks for sign-in as usual.-- **Public-only, curatable rotation.** Only **public** wiki pages are advertised — explicitly-  org-private/internal pages are filtered out — and you can drop anything else (legacy v1 pages have+- **Public-only, curatable rotation.** Only **public** wiki pages are advertised, explicitly+  org-private/internal pages are filtered out, and you can drop anything else (legacy v1 pages have   no visibility field) by adding its slug to `exclude.txt`, no rebuild. - **Signed.** Both binaries are code-signed with Adom's Azure Trusted Signing cert ("Adom   Industries, Inc.", the same one HD and AD use), so Windows Defender doesn't quarantine the `.scr`.@@ -84,19 +84,19 @@ compiler needed, and Windows Defender won't quarantine it (it's signed by "Adom  ## Screenshots -### The preferences screen — read & fix your live power settings+### The preferences screen, read & fix your live power settings Reachable from Windows' Screen Saver **"Settings…"** button, it reads your *actual* Windows power settings (lid, sleep, screen-off, lock) and shows them against the recommended "vibe-coding" profile, with one-click **Apply** for anything that's drifted. A **Re-check** button re-reads the live settings, and a toggle turns the **Win + Shift + L** hotkey on or off.-Windows' defaults predate the AI age — they assume an idle laptop should sleep; this profile keeps+Windows' defaults predate the AI age, they assume an idle laptop should sleep; this profile keeps it working instead. -![Adom Screensaver preferences screen — live power-settings drift table](/blob/app/adom-screensaver/screenshots/preferences.png)+![Adom Screensaver preferences screen, live power-settings drift table](/blob/app/adom-screensaver/screenshots/preferences.png) -### A live billboard slide — advertising the latest Wiki drops-While the screen rests, it cycles recent Adom Wiki apps/skills — each hero, title, and a-**"just ask Claude"** prompt — over a live power + display-off-countdown footer.+### A live billboard slide, advertising the latest Wiki drops+While the screensaver is up, it cycles recent Adom Wiki apps/skills, each hero, title, and a+**"just ask Claude"** prompt, over a live power + display-off-countdown footer.  ![A live billboard slide from the Adom Wiki](/blob/app/adom-screensaver/screenshots/billboard-concur.png) @@ -104,10 +104,10 @@ While the screen rests, it cycles recent Adom Wiki apps/skills — each hero, ti  | Dependency | Required? | Why | |---|---|---|-| `adom-desktop` relay | Yes (runtime) | The cloud container drives your Windows laptop through it — pushing files, compiling, shipping the WebView2 SDK, configuring power/registry. Ships with your Adom desktop bridge. |+| `adom-desktop` relay | Yes (runtime) | The cloud container drives your Windows laptop through it, pushing files, compiling, shipping the WebView2 SDK, configuring power/registry. Ships with your Adom desktop bridge. | | WebView2 Runtime | Yes (on the laptop) | Renders the billboard (video + SVG). Ships with Windows 11 / Edge. | | .NET Framework (`csc.exe`) | Yes (on the laptop) | Ships with every Windows. Compiles the screensaver + keep-awake helper natively. |-| PowerToys | **No** | Explicitly replaced — native keep-awake without it. |+| PowerToys | **No** | Explicitly replaced, native keep-awake without it. |  No `adompkg` package dependencies. @@ -147,7 +147,7 @@ No `adompkg` package dependencies. | `adom-screensaver-billboard` | Dual-wiki streaming discovery, video/SVG, `exclude.txt` curation, the manifest. | | `adom-screensaver-wake` | Wake IPC for HD/AD/any app that needs the screen. | | `adom-screensaver-build` | Compile + ship the WebView2 `.scr` (+ SDK DLLs) and verify renders. |-| `adom-screensaver-rationale` | The *why* — origin story, the staged cascade, and the design reasoning behind every behavior. |+| `adom-screensaver-rationale` | The *why*, origin story, the staged cascade, and the design reasoning behind every behavior. |  The main skill is [SKILL.md](SKILL.md); the sub-skills live in [skills/](skills/). @@ -156,5 +156,5 @@ The main skill is [SKILL.md](SKILL.md); the sub-skills live in [skills/](skills/ Built on a real ASUS ROG Zephyrus, where software can't touch the backlight (`WmiSetBrightness` ignored on the dGPU/MUX path; NVIDIA blocks `SetDeviceGammaRamp`). So the app doesn't fake it: the cosmetic dim is a CSS brightness veil (~70%) over the billboard, and the only real software backlight-off is-letting Windows turn the display off — which this app sets up, with keep-awake holding the system+letting Windows turn the display off, which this app sets up, with keep-awake holding the system so the network never drops.

@@ -1,30 +1,30 @@ --- name: adom-screensaver-description: Deploy (prebuilt + signed), configure, run, and troubleshoot the Adom vibe-coding screensaver + native keep-awake on a user's Windows laptop via the adom-desktop relay. A WebView2 (Edge/Chromium) billboard of recent Adom Wiki drops — plays webm silently, renders SVG, truly caches heroes — that rests the panel (no burn-in) while keeping the machine awake so Claude Code / Remote Control threads survive. WINDOWS ONLY. Use to install/deploy, change idle or display-off timing, disable lock-on-wake, trigger it, or troubleshoot. Trigger words — adom screensaver, adom-screensaver, vibe-coding screensaver, keep laptop awake, keep awake without powertoys, stay awake, screen off but stay awake, adom-stayawake, display off timeout, screensaver lock on wake, set up screensaver, trigger screensaver, Win+Shift+L screensaver, screensaver burn-in.+description: Deploy (prebuilt + signed), configure, run, and troubleshoot the Adom vibe-coding screensaver + native keep-awake on a user's Windows laptop via the adom-desktop relay. A WebView2 (Edge/Chromium) billboard of recent Adom Wiki drops, plays webm silently, renders SVG, truly caches heroes, that rests the panel (no burn-in) while keeping the machine awake so Claude Code / Remote Control threads survive. WINDOWS ONLY. Use to install/deploy, change idle or display-off timing, disable lock-on-wake, trigger it, or troubleshoot. Trigger words, adom screensaver, adom-screensaver, vibe-coding screensaver, keep laptop awake, keep awake without powertoys, stay awake, screen off but stay awake, adom-stayawake, display off timeout, screensaver lock on wake, set up screensaver, trigger screensaver, Win+Shift+L screensaver, screensaver burn-in. --- -# Adom Screensaver — deploy (prebuilt) + operate+# Adom Screensaver, deploy (prebuilt) + operate  Turns a **Windows** laptop into an always-on home for the user's Claude Code threads: a branded **WebView2 billboard** of recent Adom Wiki drops + native keep-awake (no PowerToys). Drive it from the Adom container through the **`adom-desktop`** relay. See also:-- **[[adom-screensaver-billboard]]** — the viewer, dual-wiki discovery, true caching, `exclude.txt` curation.-- **[[adom-screensaver-wake]]** — how HD/AD or any app dismisses it + holds the display on (IPC).-- **[[adom-screensaver-rationale]]** — the *why*: origin story, the cascade, power/lock/rest reasoning.+- **[[adom-screensaver-billboard]]**, the viewer, dual-wiki discovery, true caching, `exclude.txt` curation.+- **[[adom-screensaver-wake]]**, how HD/AD or any app dismisses it + holds the display on (IPC).+- **[[adom-screensaver-rationale]]**, the *why*: origin story, the cascade, power/lock/rest reasoning.  > ⚠️ **WINDOWS ONLY.** `adompkg install adom-screensaver` on a Linux/WSL2 container only installs-> these skills + stages the deploy payload — it does **not** run anything there. The screensaver is+> these skills + stages the deploy payload, it does **not** run anything there. The screensaver is > deployed to the user's **Windows laptop** over the relay. (The private source + build live on the > org-only `adom-screensaver-dev` page; this public package ships only the prebuilt, **signed**-> binaries — no compiler needed.)+> binaries, no compiler needed.)  ## What it is A fullscreen WebView2 rendering `billboard.html`: opens with a branded fade-to-black, then a power-aware **nerd-stats splash** (cover-fades up ~800ms over the fully-rendered content), then cross-fades through Wiki v2 + v1 hero cards. Plays **webm muted/looped**, renders **SVG**/raster; hero images/SVGs are **truly cached to disk** (video streams). When the **display-off time** arrives-it **rests** — pauses video (releasing the browser's display wake-lock), blanks to black, and powers-the panel off — so it never burns a bright billboard into a panel that's meant to be off. Keep-awake+it **rests**, pauses video (releasing the browser's display wake-lock), blanks to black, and powers+the panel off, so it never burns a bright billboard into a panel that's meant to be off. Keep-awake holds the system/network the whole time. **Win+Shift+L** launches it on demand. Only **public** wiki pages are advertised (org-private filtered; curate more via `exclude.txt`). @@ -33,27 +33,27 @@ pages are advertised (org-private filtered; curate more via `exclude.txt`). b64=$(base64 -w0 script.ps1); adom-desktop run_script "{\"interpreter\":\"powershell\",\"scriptB64\":\"$b64\"}" ``` **Check `adom-desktop status` hostname first** (it can flip between the laptop and winvm). Calls time-out ~60s; launch long things detached + poll. A winexe (`.scr`/`.exe`) ignores `&` — use+out ~60s; launch long things detached + poll. A winexe (`.scr`/`.exe`) ignores `&`, use `Start-Process`. If `run_script` returns empty, re-arm `shell_auto_approve`.  ## Deploy = PREBUILT signed binaries (no compile) Install dir: `C:\Users\<user>\adom-screensaver`. The package's `dist/win/` already holds the **signed** `.scr` + helper + DLLs + html + assets (subject `Adom Industries, Inc.`, Azure Trusted-Signing — so Defender won't quarantine them). To deploy:+Signing, so Defender won't quarantine them). To deploy: 1. **Push `dist/win/*`** to the install dir (`send_files` for the big DLLs; base64 for the small    files via the Defender-safe `.new` + `Move-Item -Force` pattern). Files: `adom-screensaver.scr`,    `adom-stayawake.exe`, `Microsoft.Web.WebView2.Core.dll`, `Microsoft.Web.WebView2.WinForms.dll`,    `WebView2Loader.dll`, `billboard.html`, `config.html`, `adom.ico`, `adom-wordmark.png`,-   `bundle.json`. **Do not compile** — ship the signed binaries as-is.+   `bundle.json`. **Do not compile**, ship the signed binaries as-is. 2. **Keep-awake + autostart:** launch `adom-stayawake.exe`; set BOTH the HKCU `…\Run` value    `adom-stayawake` AND a Startup-folder shortcut (one alone got wiped on reboot). It's power-aware    (AC = hold `ES_SYSTEM_REQUIRED`; battery = passive) and registers the Win+Shift+L hotkey. 3. **Register** (merge, never clobber): `HKCU\Control Panel\Desktop` → `SCRNSAVE.EXE`=`<dir>\adom-screensaver.scr`,    `ScreenSaveActive`=1, `ScreenSaveTimeOut`=**120** (2 min), `ScreenSaverIsSecure`=0. Apply live:    `SystemParametersInfo(0x0011,1,..)` + `SystemParametersInfo(0x000F,<secs>,..)`.-4. **Real backlight-off:** `powercfg /change monitor-timeout-ac 5` (+ `-dc 5`) — the saver rests ++4. **Real backlight-off:** `powercfg /change monitor-timeout-ac 5` (+ `-dc 5`), the saver rests +    powers the panel off at this mark.-5. **No lock on wake (optional, ADMIN):** `CONSOLELOCK`=0 needs elevation — warn the user, trigger one+5. **No lock on wake (optional, ADMIN):** `CONSOLELOCK`=0 needs elevation, warn the user, trigger one    UAC prompt, verify via the per-scheme registry index. (A real sleep-then-wake still asks for sign-in.) 6. **Verify the deployed `.scr` is signed:** `(Get-AuthenticodeSignature <dir>\adom-screensaver.scr).Status` = `Valid`. @@ -61,23 +61,23 @@ Signing — so Defender won't quarantine them). To deploy:  ## Configure (common asks) - **Idle timeout** ("come on after N min"): `ScreenSaveTimeOut`=N*60 + live `SystemParametersInfo(0x000F,..)`.-- **Display-off / rest** ("rest the screen after N min"): `powercfg /change monitor-timeout-ac N`.+- **Display-off** ("turn the display off after N min"): `powercfg /change monitor-timeout-ac N`. - **Win+Shift+L hotkey:** toggle from the preferences screen (writes `hotkey.disabled` in the install dir).-- **Curate the rotation:** append a slug to `exclude.txt` — NO redeploy ([[adom-screensaver-billboard]]).+- **Curate the rotation:** append a slug to `exclude.txt`, NO redeploy ([[adom-screensaver-billboard]]). - **Preferences screen:** Windows Screen Saver "Settings…" opens the live power-settings drift table.  ## Run on demand **Win+Shift+L**, or `Start-Process '<dir>\adom-screensaver.scr' -ArgumentList '/s'`. Grace ~1s, then any-key/mouse wakes — **instant** during the billboards (the window hides immediately; no slow fade).+key/mouse wakes, **instant** during the billboards (the window hides immediately; no slow fade).  ## Troubleshooting - **Blank/black billboard:** WebView2 Runtime missing, or the 3 DLLs / `WebView2Loader.dll` not beside   the `.scr`; check `%LOCALAPPDATA%\adom-screensaver\wv.log` (also has a 60s heartbeat + REST lines).-- **Defender quarantined the .scr:** shouldn't happen — it's signed. If a *modified* unsigned build was+- **Defender quarantined the .scr:** shouldn't happen, it's signed. If a *modified* unsigned build was   deployed, re-deploy the signed `dist/win` binaries (signing is a `-dev`/build concern).-- **Screen on all night / burn-in:** the rest path failed — confirm the deployed `.scr` is the current+- **Screen on all night / burn-in:** the rest path failed, confirm the deployed `.scr` is the current   signed build; `wv.log` should show `REST: … powering panel off` at the display-off mark.-- **Keep-awake gone after reboot:** Run key + SCRNSAVE.EXE can get wiped — that's why we also set the+- **Keep-awake gone after reboot:** Run key + SCRNSAVE.EXE can get wiped, that's why we also set the   Startup shortcut. Re-launch + re-apply.  ## Honesty constraints

@@ -1,21 +1,21 @@ --- name: adom-screensaver-rationale-description: The WHY behind adom-screensaver — the necessity-is-the-mother-of-invention origin story (keeping /remote-control alive without burning in the screen), the justification for every behavior, the staged 2-min-billboard → 5-min-display-off cascade, power-aware keep-awake, the lock-on-wake rule, the wiki-billboard "advertise apps" concept, and the org-aware personalized vision. Read this when reasoning about WHY the screensaver behaves a certain way, defending or changing a behavior, explaining its purpose to someone, or deciding whether a proposed change respects the original intent. Triggers — why does the screensaver, screensaver reasoning, screensaver rationale, why was adom-screensaver built, screensaver justification, why keep-awake, why does the screen stay on, screensaver cascade, why billboard, screensaver design, screensaver purpose.+description: The WHY behind adom-screensaver, the necessity-is-the-mother-of-invention origin story (keeping /remote-control alive without burning in the screen), the justification for every behavior, the staged 2-min-billboard → 5-min-display-off cascade, power-aware keep-awake, the lock-on-wake rule, the wiki-billboard "advertise apps" concept, and the org-aware personalized vision. Read this when reasoning about WHY the screensaver behaves a certain way, defending or changing a behavior, explaining its purpose to someone, or deciding whether a proposed change respects the original intent. Triggers, why does the screensaver, screensaver reasoning, screensaver rationale, why was adom-screensaver built, screensaver justification, why keep-awake, why does the screen stay on, screensaver cascade, why billboard, screensaver design, screensaver purpose. metadata:   node_type: skill ---  Parent skill: **adom-screensaver** -This is the **design rationale** — the *why*. For *how* to operate/build/extend, see the+This is the **design rationale**, the *why*. For *how* to operate/build/extend, see the sibling skills (`adom-screensaver` operate, `-billboard`, `-wake`, `-build`). When a change is proposed, check it against the reasoning here first: most "obvious simplifications" regress a behavior that exists for a hard-won reason. -## Necessity is the mother of invention — the origin+## Necessity is the mother of invention, the origin  John kept getting burned by a specific failure: he'd start a **`/remote-control`** thread in-Claude Code, then walk away from the laptop — go to dinner with the family — and come back to a+Claude Code, then walk away from the laptop, go to dinner with the family, and come back to a **dead session**. The laptop had gone to **sleep and killed the session**, *even while plugged in*. The AI had stopped working the moment he left. @@ -26,19 +26,19 @@ either the session dies, or the panel cooks. adom-screensaver exists to dissolve that trade-off. The core insight is that **"machine awake" and "screen on" are two different things**, and Windows' defaults conflate them. The screensaver splits them: hold the **machine** awake (network + `/remote-control` survive) while letting the-**screen** turn off to rest the panel. Best of all worlds — the thing Windows wouldn't give you+**screen** turn off to save power. Best of all worlds, the thing Windows wouldn't give you out of the box, because its power model predates AI agents that run for hours on your behalf.  ## What each behavior is FOR (don't regress these)  - **Power-aware keep-awake.** Plugged in → hold the machine awake indefinitely (`/remote-control`-  runs as long as you like — your laptop becomes a *vibe-coding server*). On **battery** → stay+  runs as long as you like, your laptop becomes a *vibe-coding server*). On **battery** → stay   passive and let Windows' own idle-sleep timer be the give-up clock (default 30 min), so a   forgotten laptop in a bag eventually sleeps instead of draining flat. The keep-awake holds   `ES_SYSTEM_REQUIRED` only on AC; it deliberately does **not** assert it on battery. See the-  power decisions in the project memory before changing this — it regressed twice.+  power decisions in the project memory before changing this, it regressed twice. - **Lid-close = "Do nothing".** Closing the lid is a hardware *button action*, separate from idle-  sleep — keep-awake can't influence it. Set the lid action to "Do nothing" so closing the lid to+  sleep, keep-awake can't influence it. Set the lid action to "Do nothing" so closing the lid to   walk to the next room doesn't instantly sleep; the idle-sleep timer (30 min on battery) is the   real give-up. Walk around freely; come back within 30 min and nothing was interrupted. - **Lock rule: "no sleep → no lock; real sleep → normal sign-in."** `ScreenSaverIsSecure=0` so@@ -48,34 +48,34 @@ out of the box, because its power model predates AI agents that run for hours on  ## The staged cascade (the 2-min → 5-min design) -The saver runs in **stages**, on purpose — a gentle cascade rather than a hard cut to black:+The saver runs in **stages**, on purpose, a gentle cascade rather than a hard cut to black: -1. **0–2 min idle:** nothing. (`ScreenSaveTimeOut = 120s`.)-2. **2–5 min idle:** the **billboard** plays — a *dim, mostly-black* full screen cycling recent+1. **0-2 min idle:** nothing. (`ScreenSaveTimeOut = 120s`.)+2. **2-5 min idle:** the **billboard** plays, a *dim, mostly-black* full screen cycling recent    wiki drops. This phase is **lightweight to dismiss**: the panel is still powered, so a single    mouse flick or keypress expires it instantly. 3. **5 min idle:** the **display powers off** entirely (`monitor timeout = 300s`) to actually-   rest the panel. The machine stays awake (on AC) the whole time.+   turn the display off. The machine stays awake (on AC) the whole time.  **Why this ordering matters:** the saver often kicks in when you didn't really want it (you paused to read, took a call). If the *first* thing it did was fully power the screen off, every accidental trigger would cost you the heaviness of the panel going dark and then warming back up. By showing a dim billboard first and only powering the screen off 3 minutes later, an early/accidental trigger-is trivially undone — you barely notice it. The full display-off is reserved for when you've truly+is trivially undone, you barely notice it. The full display-off is reserved for when you've truly stepped away. Don't collapse the two stages into one. -## The screensaver became a canvas — the billboard+## The screensaver became a canvas, the billboard  Once you have a full screen that's "resting," it's the **perfect canvas**. Instead of black, the-billboard surfaces the **coolest new stuff in the Adom Wiki** — each app/skill's hero image, title,+billboard surfaces the **coolest new stuff in the Adom Wiki**, each app/skill's hero image, title, and a "just ask Claude: `install <x>`" prompt. So the screensaver does double duty: it keeps the machine working *and* **educates the user (and John) about new wiki apps while they're away**.  This reframes wiki hero images as **marketing surfaces**: your wiki assets advertise apps on-people's lock screens and nudge adoption — value far beyond the wiki page itself.+people's lock screens and nudge adoption, value far beyond the wiki page itself.  - **Media:** a **video hero** (`.webm`) is **streamed silently** (muted, looped) straight from the-  wiki — motion grabs the eye; nothing is downloaded. No video → fall back to the **hero image**.+  wiki, motion grabs the eye; nothing is downloaded. No video → fall back to the **hero image**. - **Dual-wiki:** pulls Wiki v2 (canonical) + Wiki v1 (legacy, with a "migrate to v2" nudge); v2   wins on overlap. Order is shuffled each run so the first slide varies. - **Curation:** a runtime `exclude.txt` drops baseline/uninteresting slugs without a rebuild.@@ -90,18 +90,18 @@ people's lock screens and nudge adoption — value far beyond the wiki page itse - **Distributed via the wiki, installed by HD.** The screensaver is a Windows-*host* app, so it's   not `adompkg install`-into-the-workspace. It's published to Wiki v2 with a `dist/win/` bundle in   the tarball; HD's setup steps fetch + install it on the host (opt-in, reversible). Publish a new-  version → every HD picks it up, no HD rebuild. (macOS/Ubuntu HD must gracefully skip it — it's+  version → every HD picks it up, no HD rebuild. (macOS/Ubuntu HD must gracefully skip it, it's   Windows-only.)  ## Use cases to keep in mind  - **Vibe-coding server:** laptop plugged in on a desk, lid open or closed, running `/remote-control`-  threads for hours while John is elsewhere. Never sleeps; screen rests.-- **Mobile / on battery:** moving between rooms or out the door — rides short lid-closings, then+  threads for hours while John is elsewhere. Never sleeps; the display turns off.+- **Mobile / on battery:** moving between rooms or out the door, rides short lid-closings, then   sleeps on the 30-min give-up so it doesn't drain. - **Ambient discovery:** any idle moment becomes a chance to learn what's new in the wiki.  **Guiding principle:** the screensaver bends the laptop's behavior away from Microsoft's-pre-AI defaults, *on purpose*, to protect long-running AI work — while being honest about power-(rest the screen, respect the battery, keep real-sleep security). Any change should preserve that+pre-AI defaults, *on purpose*, to protect long-running AI work, while being honest about power+(turn the display off, respect the battery, keep real-sleep security). Any change should preserve that balance.