* docs: Ralph report scaffolding + pureintent eval baseline (10.87s)
* cycle-1: drop nixvim — pureintent eval 10.87s → 6.98s (-36%)
nixvim's home-manager module system is by far the dominant cost of
evaluating `nixosConfigurations.pureintent`: a profile of selective
imports puts it at 3.97s of the 10.87s baseline (~36%).
Replace it with a minimal `programs.neovim.enable = true` configuration.
The runtime behaviour of `nvim` changes (no plugins, no LSP, no
mapleader/telescope/treesitter/etc.) — accepted by the user.
Measured on srid-nc (nixos, 6.12.85 kernel), 7 warm-cache runs with
`--option eval-cache false`:
baseline: 10.85 10.86 10.86 10.87 10.87 10.88 10.91 -> median 10.87s
cycle-1: 6.94 6.96 6.98 6.98 7.02 7.02 7.73 -> median 6.98s
Other configurations still evaluate:
- nixosConfigurations.naiveintent
- darwinConfigurations.infinitude-macos
- homeConfigurations."srid@zest"
Removes flake input `nixvim` (+ its `flake-parts`, `nixpkgs`, `systems`
sub-inputs from the lock).
* docs: wrap up Ralph report (10.87s -> 6.99s = -35.7%)
7 dead-ends documented so they don't have to be re-tried. Key
finding: after dropping nixvim (cycle 1), the eval floor is
home-manager's per-entry submodule materialisation
(systemd.user.services / programs.ssh.matchBlocks), not the
option-declaration count of any wrapper module. Inlining
jumphost-nix or vira moves the cost; it does not eliminate it.
Routes shell-invoked commands through the existing jumphost SOCKS5 proxy
(programs.jumphost.socks5Proxy), so Go tools that bypass libc (nix, step,
pu) pick up the proxy via ALL_PROXY/HTTPS_PROXY/HTTP_PROXY while libc
callers (ssh) get it via proxychains.
Usage: devbox-run nix run github:juspay/project-unknown -- connect <name>
* Enable incus on pureintent, rename lxd.nix, drop unused flake-parts
- Add incus module import to pureintent and bind the UI to its
Tailscale IP (no firewall change needed since tailscale0 is trusted).
- Rename modules/nixos/linux/lxd.nix -> incus.nix since the module
configures virtualisation.incus, and enable the bundled web UI.
- Drop the unused modules/flake-parts/incus-image helper; the
`images:nixos/*` community images cover container/VM launches.
* Move incus module into a directory with a README
The troubleshooting notes used to live as comments in the module; they
belong in docs alongside a quick-start on launching containers/VMs and
configuring the UI listener.
* Expand incus README with VM gotchas
Document the sharp edges hit while bringing up a NixOS VM for the first
time: secureboot, memory/cpu/disk limits (with the error signatures
that point at each), configuring the guest (flakes, firewall), and a
three-step guide to exposing a service from inside.
