Explain that a single `nix flake update` in the consumer's own flake
bumps every package version — including packages this repo's modules
install, since they build against the consumer's nixpkgs via `follows`.
Cover per-input bumps and the release-jump caveat.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
default the consumer example to owning its own `nixpkgs` (with the baseline
following it) so a consumer's update cadence stays theirs; keep the coupled
`follows` form as a quickstart alternative. rename the `pub` input to
`baseline`, and note that `local.*` options double as the override for
deliberately-frozen pins.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The consumer section had only a bare-bones flake snippet. Add an example
private layout (`system/` + `home/` split, `hosts/<host>/`), a fuller
`flake.nix` matching it, and an "Overriding the baseline" section covering
the three mechanisms (neutral default → real value, `local.*` options,
extra modules). Note that structurally only `flake.nix` is required.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Shutdown stalls are hard to debug because journald is torn down mid-way,
so late hangs never reach the journal. `modules/shutdown-debug.nix`
exposes `local.shutdownDebug.*`: verbose systemd logging routed to kmsg
(recoverable from pstore after a forced power-off), an opt-in tty9 debug
shell, and a shortened `DefaultTimeoutStopSec` preset (system + user) so
a hung unit is killed and logged in seconds instead of spinning at 90s.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
daniil-bergandClaude Opus 4.8