[clhodapp]

An nvf or nixvim configuration declared inside a machine, a home or a hjem configuration now relates to that configuration the way a home relates to its machine. It has an activation of its own, which the configuration above runs each time it is activated itself.

Stacked on #103, whose drift check every profile runs.

The profile

lib.caisson.integrations.profileOf gives the configuration the outputs activationPackage and profile. activate checks for drift against the nearest configuration above with an activation. It then points a Nix profile at the Neovim with nix-env --profile, which also registers a garbage-collector root. When the profile already points at that Neovim, it adds no generation.

Declared inside	Profile	Activated by
a NixOS or system-manager machine	/nix/var/nix/profiles/caisson/<kind>/<name>	unit caisson-profile-<kind>-<name>, as root, wanted by multi-user.target
a darwin machine	the same	a postActivation step, as root
a home	$HOME/.local/state/caisson/profiles/<kind>/<name>	a home activation step after linkGeneration
a hjem configuration inside a machine	the same	the machine's unit caisson-profile-<user>-<kind>-<name>, as the user, after hjem-activate@<user>
nothing (a top)	the same	running activate by hand

Every activation of the configuration above puts the profile back to what that configuration declares. That covers home-manager switch, a switch of the machine, and a boot, since the machine activates its homes and profiles at boot.

Choosing a profile

Each class installs profileShimsOf: nvim, plus vi and vim where the Neovims have them. Each runs the profile named by $CAISSON_NVIM_PROFILE, read every time it runs, and the configuration's default when the variable is unset. A home or a hjem configuration sets the variable to its own profile, and a shell can export another value. Where several profiles share the variable, caisson.profiles.selected names the default, and evaluation fails until it does.

Other changes (pre-1.0)

• nvf and nixvim get a default module declaring caisson.drift.warn.
• The home marker from feat(integrations): check drift between every activated configuration and the one above it #103 moves to $HOME/.local/state. A unit of the machine and a shell of the user may see $XDG_STATE_HOME differently, and both must find the same file. User profiles use the same prefix for the same reason.

Testing

• nix flake check passes, including the unit tests, the pinned-world suite and the eval-weight gate.
• Pinned-world tests check the units, users, shims and session variables for a NixOS machine, a home, a system-manager machine and a hjem configuration inside one. They also check that a top's profile points at the derivation neovimConfiguration builds.
• Run for real with a throwaway $HOME:
  • the first activate creates the profile at the right Neovim;
  • a second activate adds no generation;
  • after a hand change with nix-env --set, the next activate puts the profile back, and the history keeps all three generations;
  • the nvim shim runs the profile the variable names, and the default when it is unset.
• nix flake check --no-build passes in all 17 workspace consumers with this branch in place of both caisson pins: ch-home-manager and ch-personal-machines on fix/activation-drift (their maint: update flake pins #17 and refactor(nixpkgs): registries are read from caisson-core by the name of the mkLib argument #59), ch-system-manager on test/system-manager-configurations (refactor: nixos-minimal as its own integration over the nixos class #15), the others on main.

Not covered yet

• There is no VM test of the boot-time unit or of the reset through a machine. caisson has no VM tests, and the drift VM test in ch-home-manager would need nvf as a new test dependency there.
• A hjem configuration activated standalone with hjem standalone switch doesn't activate its profiles. Inside a machine, the machine does.

Docs: nix-caisson/nix-caisson.github.io, branch docs/editor-profiles.

🤖 Generated with Claude Code