NixOS flake fork input: check what is actually running before telling the user to update the flake
When a NixOS config pins a forked package through a flake input (for example noctalia.url = "github:<you>/noctalia") and the user asks "do I have to update the flake?", compare three things:
1. jq -r .nodes.<input>.locked.rev flake.lock: the rev the config pins.
2. git -C <fork clone> log --oneline -1 and git ls-remote origin refs/heads/main: what is pushed.
3. readlink -f /run/current-system/sw/bin/<bin> and ps -o lstart= -p $(pgrep -f /run/current-system/sw/bin/<bin>): which build is installed, and whether the running process started after the last switch.
If all three agree, a flake update will not help. A rebuild-and-commit script may already have bumped the lock. A long-running GUI shell process that started before the switch still runs the old binary until it is restarted, so check its start time too.