[RAGE][DOTEXP-004] Dotfiles authoring expert flows: init, import, adopt, migrate, add config and verify #229

New issue

Open

opened 2026-09-20 01:44:30 +00:00 by nsaspy · 0 comments

nsaspy commented

2026-09-20 01:44:30 +00:00

Owner

Parent: #281. Depends on layout + ownership slices.

Make DotfilesExpert useful to people creating dotfiles, not just analyzing this repo.

Symbolic workflows:

initialize a new dotfiles workspace;
inventory an existing home/config tree;
choose/declare plain Git vs Stow vs chezmoi vs Home Manager vs mixed strategy;
import/adopt selected files;
add a new managed config;
split shared vs host-specific state;
convert unmanaged -> managed;
migrate between layouts incrementally;
preview links/files/templates/Nix effects;
detect secrets/private/runtime state before Git;
generate/update a machine-readable layout manifest and human docs;
verify deployed postconditions.

No mutation during inspect/plan. Actual changes use canonical typed create/edit/link/file effects with expected-state checks.

Acceptance: zero-model fixture turns an unmanaged XDG config set into a declared managed workspace, applies a bounded fake filesystem plan and verifies resulting mappings without touching unrelated files.

Parent: #281. Depends on layout + ownership slices. Make DotfilesExpert useful to people creating dotfiles, not just analyzing this repo. Symbolic workflows: - initialize a new dotfiles workspace; - inventory an existing home/config tree; - choose/declare plain Git vs Stow vs chezmoi vs Home Manager vs mixed strategy; - import/adopt selected files; - add a new managed config; - split shared vs host-specific state; - convert unmanaged -> managed; - migrate between layouts incrementally; - preview links/files/templates/Nix effects; - detect secrets/private/runtime state before Git; - generate/update a machine-readable layout manifest and human docs; - verify deployed postconditions. No mutation during inspect/plan. Actual changes use canonical typed create/edit/link/file effects with expected-state checks. Acceptance: zero-model fixture turns an unmanaged XDG config set into a declared managed workspace, applies a bounded fake filesystem plan and verifies resulting mappings without touching unrelated files.