Repository navigation
ArmouryDaemon 1.1.6
A pack now says what it is and what starts it. Two optional fields carry it: kind is "pack" or "mode", and triggers says what starts the pack - a tracked_app, or a hotkey with a key. Both are additive: a pack that carries neither is a "pack" started by a tracked app, so the three shipped packs load, apply, revert and remove exactly as they did, and spec stays 1 or 2. A value outside the set is refused by name instead of defaulted - unknown kind 'widget' (expected 'pack' or 'mode') - a mode needs at least one trigger, a hotkey trigger needs a key, and a tracked_app trigger takes none.
The capability gate covers the declarative steps. It covered the script, where only the granted functions are registered on the engine, and not the steps, because a step is data and no engine ever sees it: a pack that declared "capabilities": ["files"], or [], could still run a program (cli), start or kill a process (process_start, process_kill), inject keystrokes (hotkey) and write the registry (registry_set). Every mechanism names its capability now. A step whose capability the pack did not declare is refused when the pack is validated, so the pack never loads, and refused again where the step would run. registry_set gets a capability of its own, registry: a registry write reaches outside the four file roots the sandbox enforces, so it is its own grant rather than part of files-write.
A change of the cooldown no longer brings an expired window back to life. The daemon drains its pipe before the 1 Hz tick that reaps an expired window, so a set_cooldown in that gap gave the dead window the new length: the dashboard ran a countdown for a cooldown that was not running, and the next game launch was held behind it. Only a window that is still running is re-timed; one that has ended is dropped, and the next start changes the machine at once.
What else changed
overlay_showandoverlay_hiderequests are coalesced: one pending request, and a request for the state the daemon is already in is skipped. A script with a thousand pairs used to cost a black window per monitor, a marker file write and delete, and a pack job for each pair.- The refusal message survives being raised inside a pack function. Rhai wraps an error from a script-defined function, so the daemon's match missed it and the pack's log got
Function not foundinstead of the line naming the missing capability. audio_mute_allleaves a crash-recovery record: the devices it muted go intoidle.ledger, the file idle mode already uses, so the next start unmutes them after a crash or a reboot.- A game that starts inside a revert's window wins. The revert is cancelled and the machine stays in Turbo, while the window keeps holding pack changes for the rest of its length.
- A hand-edited
cooldown_secondsis clamped to 5-3600 s at startup, so it cannot panic the daemon.
The pack format stays additive, and the three shipped packs are unchanged.