Add superfile (worked example for the new-tool template)

[alycda]

Stacked on #198 (base is claude/loving-hawking-5eh9pm, not main). Retarget to main once #198 merges. This PR adds superfile and fills in the new-tool template as it goes, to see where the template helps and where it doesn't.

what

superfile, a TUI file manager (Go, MIT). CLI/TUI. It builds for aarch64-darwin and linux. Added to home.nix and to the darwin-gated list in work.nix.

why

No file manager is installed today; I grepped the repo for yazi, ranger, lf, nnn, broot and xplr and found none. This is an evaluation target for the template, so the "closest existing tool" answer is eza plus bat for listing and previewing, which don't navigate or operate on files.

how

• Placement: profile packages, no module. superfile writes its own config and state at runtime, so there is nothing for home-manager to own. work.nix also feeds the alyssa@work-dev devcontainer, so it sits in the darwin-gated list. Not lib/core-packages.nix, which every container inherits.
• Source: nixpkgs superfile. The locked rev (7a0f122) has 1.3.3; nixos-unstable and master have 1.6.0. That is a stale lock rather than a lagging nixpkgs, so the fix is nix flake update, which the weekly workflow does. I did not pin forward as lib/weave.nix does, and I did not bump the lock here because that moves every input under a one-package change. Until the next update this installs 1.3.3.
• Constraints:
  • headless-safe: gated out of the container; no credential prompt
  • runtime-mutable state stays unmanaged
  • base-image collision risk: only the superfile binary, nothing that overlaps the nixos/nix profile. This is by inspection, not by activating in the image.
  • network calls: auto_check_update defaults to true, a once-a-day check on exit. Left at the default, with a comment saying how to turn it off.

verify

• statix check . and deadnix --fail . pass
• both profile files parse
• the locked nixpkgs' superfile builds on x86_64-linux and superfile --version prints v1.3.3
• not verified: full evaluation of the home configurations. This sandbox's proxy refuses the github: flake inputs, so nix eval .#homeConfigurations... can't run here. CI's eval-configurations.sh is the check for that.
• not verified: anything on a real macOS profile. After a switch, run zsh -lc 'command -v superfile && superfile --version'.

Template evaluation

The template did its job: it forced the version check, the placement reasoning and the "not verified" list. Four gaps showed up, none fixed here (they belong on #198 if you agree):

1. Binary name. The upstream docs say spf; nixpkgs installs superfile (mainProgram), on 1.6.0 too. The verify baseline command -v <tool> only works with the real binary name, which what doesn't ask for. Suggest adding "binary name, if it differs from the project name" to what. I added no spf alias; that is your call.
2. Phone-home behaviour. Nothing in how asks about update checks or telemetry, and this tool has one on by default. Given a privacy-first default, suggest a constraint checkbox: "network calls at startup or exit, and how to disable them".
3. Which version source. The prompt says "version at the pinned rev, and master if stale". The check that mattered was the three-way one: locked rev vs nixos-unstable head vs master. It decides between flake update and a pin-forward, which are different PRs. Suggest naming nixos-unstable in the prompt.
4. "Can't run it where you are". This prompt earned its place. The flake eval was blocked here, and without the prompt the gap would have been easy to skip.

🤖 Generated with Claude Code

https://claude.ai/code/session_014ctTM9ShmZvCpEmMKEdHvP

---

Generated by Claude Code

[github-actions]

⊕ Entity-level changes

home-manager/profiles/home.nix

Status	Type	Name
Δ	binding	home

home-manager/profiles/work.nix

Status	Type	Name
Δ	binding	home

Summary: 2 modified across 2 files

_{functions and classes, not lines · sem}

[alycda]

Update to the "Template evaluation" section above: gaps 1–3 (binary name, network calls, three-way version check) are now applied to the template in #198 (62ad229), and this branch has merged them in (2e16f09). Gap 4 needed no change. The "none fixed here" wording in the description is out of date.

---

Generated by Claude Code