hl-fwdesk's nix resolved git+ssh://.../hermenix.git?ref=main against a
cached ref->rev mapping from an earlier fetch this session, running a
stale commit's nu/hermenix.nu (from before flake.lock existed) and
hitting the exact same "cannot write modified lock file" error again
despite both fixes already being pushed. --refresh forces Nix to check
Gitea for the current tip on every invocation instead of trusting the
cached resolution (respects tarball-ttl otherwise) - required given the
whole design point is "always run whatever's current, no manual pull."
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>