companion: idle in step with wscreensavers, and despite No lock

Her stages sat at 1, 3 and 5 minutes, and the saver starts at 5, so she
lay down under it. They are now 20, 40 and 70% of wscreensavers'
idleTimeoutMinutes, read live from its config: 1, 2 and 3.5 minutes at
its default.

She never idled at all while No lock was on: it holds an idle inhibitor
and her monitors respected inhibitors. Measured with a throwaway shell,
a 5 s monitor respecting them never fired while one ignoring them did.
They now ignore inhibitors, as the saver does, and presentation and
gaming mode keep her awake by name.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

1 files changed, 8 insertions, 1 deletions

diff --git a/desktop/companion/README.md b/desktop/companion/README.md
index 45e522d..cfa3ffc 100644
--- a/desktop/companion/README.md
+++ b/desktop/companion/README.md
@@ -50,8 +50,15 @@ frame falls back to its outfit's `base`.
 - She only feels the pointer while it is over her: Quickshell has no
   global pointer and Hyprland sends no motion events. Hence the 0.6 s
   dodge rather than moving away as the pointer approaches.
+- Idle stages are 20, 40 and 70% of wscreensavers' `idleTimeoutMinutes`,
+  read live from its config, so she lies down before the saver starts.
 - `IdleMonitor.enabled` read false on creation when left out, so each of
-  the three sets it.
+  the three sets it. It also reads false at `Component.onCompleted` even
+  when set, and true a moment later; do not trust that first reading.
+- The monitors ignore inhibitors. No lock holds an idle inhibitor for as
+  long as it is on, and with `respectInhibitors: true` she never idled
+  (measured: a 5 s monitor respecting them never fired, one ignoring them
+  did). Presentation and gaming mode keep her awake by name instead.
 - Fullscreen is `lastIpcObject.fullscreen === 2`. Maximised is 1, and
   most windows here are maximised.
 - The lock screen covers every layer, so locking needs no code.