bernardo/Nomarchy
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

wave/qa-core-system #3

Merged
bernardo merged 4 commits from wave/qa-core-system into main 2026-05-19 19:17:22 +01:00
Conversation 0 Commits 4 Files Changed 6 +27 -7
bernardo commented 2026-05-19 18:48:40 +01:00
Owner
Copy Link
No description provided.
bernardo added 4 commits 2026-05-19 18:48:40 +01:00
fix(impermanence): user must match created account, not hardcoded "nomarchy" 749f970fb0 
The persistence block at core/system/impermanence.nix:75 read
`users.nomarchy = { directories = [...]; }` — the username was a
literal, not a reference. For any user not literally named "nomarchy"
the block was silently inert and ~/.ssh, ~/.gnupg, ~/.local/share/keyrings,
Documents, Downloads, Pictures, Videos, Projects were wiped on every boot.

Adds `nomarchy.system.impermanence.user` (str, default "nomarchy") and
uses it via `users.${cfg.user}`. The installer now writes the chosen
username alongside `enable` and `mainLuksName` so impermanence installs
with non-default usernames are correct out of the box.

docs/OPTIONS.md: fixes the wrong path on the impermanence row
(documented `impermanence.enable`, real option is
`nomarchy.system.impermanence.enable`) and adds entries for
`mainLuksName` and `user`.

Found during Pillar 8 audit of core/system modules.
chore(schema): drop orphan features.makima 0656f33611 
`lib/state-schema.nix` declared `system.features.makima = false` but
the field was never wired anywhere: no matching option in
core/system/options.nix, no consumer in core/system/state.nix, no
references in the wider tree. Schema-only ghost — removed.

Found during Pillar 8 audit of core/system modules.
fix(hibernate): mkDefault on HandlePowerKey / IdleAction / IdleActionSec 0e93639702 
These three settings.Login fields were set at default priority, so a
downstream system.nix that wrote (e.g.) `services.logind.settings.Login.HandlePowerKey = "poweroff"`
would collide with Nomarchy's value instead of overriding it. Same
mkDefault treatment as the other lid-switch settings in this block.

Found during Pillar 8 audit of core/system modules.
docs(roadmap): log uwsm-in-virtualization module placement (Later) 28a0e28f2d 
core/system/virtualization.nix wires `programs.uwsm` + the Hyprland
session config at the top of the file — loaded unconditionally on every
install, with no actual relationship to libvirt/docker. Cosmetic
mislocation, not a behavior bug; logged as a Later row so it can be
fixed in a dedicated session module without growing this audit PR.

Found during Pillar 8 audit of core/system modules.
bernardo force-pushed wave/qa-core-system from 28a0e28f2d to af8fa321ff 2026-05-19 19:15:26 +01:00 Compare
bernardo closed this pull request 2026-05-19 19:16:59 +01:00
bernardo reopened this pull request 2026-05-19 19:17:14 +01:00
bernardo merged commit bd7e5a5706 into main 2026-05-19 19:17:22 +01:00
bernardo deleted branch wave/qa-core-system 2026-05-19 19:17:22 +01:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
bernardo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bernardo/Nomarchy#3
Delete Branch "wave/qa-core-system"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?