mesh-catalog

1,131 Commits 47 Branches 0 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
jochen	5d7d9020b8	Say the laptop's scripts unparsed where the build seat has no bash mesh/merge-gate pass: builds asus-zephyrus-g14, i3status-rust, power → ace, g14, novox, shanks; no bus step; every machine composes with the change as it d… Details mesh/repo-check pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; it… Details mesh/delivery delivered Details The Go toolchain the repository check runs in carries no bash, so the scripts' syntax check failed there on a missing interpreter, not a broken script.	2026-10-08 16:20:45 +02:00
jochen	afce6b03f4	triggerhappy: the machine's hotkeys as a module holding node-hotkeys (hq ADR 0212) The laptop's model module owned triggerhappy's trigger file and service, although the daemon is a general piece others have keys for. triggerhappy now owns the daemon, reads only the mesh's file, runs every trigger as the account, and the model module contributes its vendor keys.	2026-10-04 16:50:57 +02:00
jochen	b098b64b22	Phase 3: asus-zephyrus-g14 and memory-pressure, with Go tools and long-running code The laptop model's hardware module and a memory-pressure module for any machine (hq research 027/03, 026/05, to-be 42 phase 3). The predecessor's polling auto-profile and mem-guard user scripts become each module's own Go code launched by the node runtime (ADR 0198): a profile switcher woken by the kernel's power-supply uevents, and a guard that warns on RAM, swap or PSI before systemd-oomd acts, on the desktop over the account's bus and always as an event. supergfxctl and triggerhappy are kept as found (research 027 Q1).	2026-10-04 15:42:56 +02:00

Author

SHA1

Message

Date

jochen

5d7d9020b8

Say the laptop's scripts unparsed where the build seat has no bash

mesh/merge-gate pass: builds asus-zephyrus-g14, i3status-rust, power → ace, g14, novox, shanks; no bus step; every machine composes with the change as it d…

Details

mesh/repo-check pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; it…

Details

mesh/delivery delivered

Details

The Go toolchain the repository check runs in carries no bash, so the scripts' syntax
check failed there on a missing interpreter, not a broken script.

2026-10-08 16:20:45 +02:00

jochen

afce6b03f4

triggerhappy: the machine's hotkeys as a module holding node-hotkeys (hq ADR 0212)

The laptop's model module owned triggerhappy's trigger file and service, although the daemon is a
general piece others have keys for. triggerhappy now owns the daemon, reads only the mesh's file,
runs every trigger as the account, and the model module contributes its vendor keys.

2026-10-04 16:50:57 +02:00

jochen

b098b64b22

Phase 3: asus-zephyrus-g14 and memory-pressure, with Go tools and long-running code

The laptop model's hardware module and a memory-pressure module for any
machine (hq research 027/03, 026/05, to-be 42 phase 3). The predecessor's
polling auto-profile and mem-guard user scripts become each module's own
Go code launched by the node runtime (ADR 0198): a profile switcher woken
by the kernel's power-supply uevents, and a guard that warns on RAM, swap
or PSI before systemd-oomd acts, on the desktop over the account's bus and
always as an event. supergfxctl and triggerhappy are kept as found
(research 027 Q1).

2026-10-04 15:42:56 +02:00