2026-09-20 Conventions and Learnings System Deployed

What I set out to do

Format, verify, commit, and switch the changes implementing the conventions and learnings workflow per ADR 0020.

What I actually did

  • Ran just check to execute code formatting and pre-commit hooks across the workspace:
    • mdformat formatted the markdown tables in nix/home-manager/modules/coding-agents/common/context/AGENTS.md.
    • All workspace checks passed cleanly (linters, deadnix, statix, and flake checks).
  • Staged and committed changes in commit f0b1638 (feat(obsidian): add conventions and learnings):
    • Created templates nix/home-manager/files/obsidian/templates/conventions-template.md and nix/home-manager/files/obsidian/templates/learnings-template.md.
    • Configured Templater folder templates in nix/home-manager/modules/obsidian.nix for Atlas/References/Conventions and Chronicles/Learnings.
    • Added conventions and learnings rules table and guidelines to AGENTS.md covering Writing, Visual, and Dashboard output families.
  • Performed dry-run verification (hm -n) to inspect Home Manager generation plan.
  • Executed hm to switch the Home Manager generation, deploying the new templates into the Obsidian vault and syncing instructions across coding agents.

What was striking

  • hm is a shell script wrapper on $PATH that passes arguments directly to home-manager switch --flake ~/.config/nix#<system>. Calling hm without extra arguments directly builds and activates the generation.