refactor: mirror module namespaces to their directories (task 0031) #23
Reference in New Issue
Block a user
Delete Branch "task-0031-module-namespace-tidy"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Task:
.claude/tasks/0031-module-namespace-tidy.mdSummary
Adopt the convention that a Module's option path mirrors its directory under
modules/, with an index file (name-matches-directory) declaring the directory's own segment rather than a doubled one.modules.agents.*:claude-code(whole directory, assets included),pi(flattened to a single file),skills(renamed fromagent-skills), andgitea-axiinto anagents/tools/subgroup.agents/andtools/are pure namespace prefixes — no aggregatorenable.hypridleandhyprlocknested undermodules.desktop.hyprland.*(withhyprland.nixas the index), and the desktop aggregator updated.modules/example.nixremoved.CONTEXT.mdand ADR 0004; theneogaiahost, the two liveCLAUDE.mdgotchas, and theskillsModule's intentional-exception comment updated.Verified:
nix flake checkbuildschecks.x86_64-linux.neogaiagreen; every new option path resolves and every old one (modules.claude-code,modules.pi,modules.gitea-axi,modules.example,modules.desktop.hypridle/.hyprlock) and would-be aggregator (modules.agents.enable,modules.agents.tools.enable) no longer resolves.No deviations from the plan.
Review
Risk
Overall: Low
neogaiaconsumes them and it is updated in lockstep, no cross-repo or external callers.example.nix, a teaching stub); trivially revertible via git, no schema/migration/published-API change.nix flake checkbuilds the host toplevel green, this repo's real build/verify seam, exercising every renamed option path.agent-sudo-guard.shhook is moved verbatim, not modified).cfg/option-path edits, no control-flow changes.Standards — unaddressed
.claude/tasks/0031-*.mdcontains semicolons in prose — left as-is: task files are kept verbatim as historical record, which the task itself scopes out.(All other Standards findings — semicolons and multi-sentence lines in the ADR and
CONTEXT.mdentry, and glossary-term/agent-state references in theskills.nixcomment — were fixed and are in the diff.)Spec — unaddressed
CONTEXT.mdglossary entry referencesmodules/and "aggregate enable," judged to stay at convention level (matching the siblingEnable conventionentry's style) rather than implementation detail.— Claude