feat(wrapperModules.zed): init

[SibaldH]

Summary

Adds a new zed wrapper module.

This provides a Home Manager-like declarative interface for Zed without depending on Home Manager. The wrapper can generate Zed config files and symlink them into the user’s $XDG_CONFIG_HOME/zed directory before launching Zed.

Supported options include:

• userSettings for settings.json
• userKeymaps for keymap.json
• userTasks for tasks.json
• userDebug for debug.json
• extensions, translated into auto_install_extensions
• themes, supporting generated JSON themes and existing theme file paths
• linkConfig, to control whether generated config is symlinked on launch
• forceSymlinks, to opt into replacing existing user config files or symlinks

Design notes

Zed expects its configuration files in the user config directory, so this wrapper does not try to pass a custom config path to Zed. Instead, it generates the config files into the wrapper derivation using constructFiles, then links individual files into $XDG_CONFIG_HOME/zed when the wrapped binary starts.

The default behavior is intentionally conservative: existing real files or unrelated symlinks are not overwritten unless forceSymlinks = true is set.

Testing

• nix fmt
• nix build ./ci#checks.x86_64-linux.wrapperModule-zed -Lv
• nix flake check -Lv ./ci

Reviewer notes

I opened this as a draft because I would like feedback on the config-linking approach.

In particular, I would appreciate feedback on:

1. whether linkConfig = true is a good default;
2. whether the forceSymlinks safety behavior matches the expectations of this repository;
3. whether the option names should stay close to Home Manager’s Zed module names or use more generic wrapper-module naming.