docs(ai): replace version control directives with reference to VERSION_CONTROL.md

Author: topfunky

.ai/agents/VERSION_CONTROL.md

@@ -0,0 +1,100 @@
+# Version Control with Jujutsu
+
+Guidelines for using Jujutsu (jj) for version control operations in this dotfiles project.
+
+## Core Principles
+
+- Use `jj` for version control operations. Background LLM Agent must not use `git`.
+- **Pre-Commit Validation**: Run `make validate` and ensure it passes before any commit
+- **User Confirmation**: Always obtain explicit user confirmation before executing any commit commands to VCS (use only `jj`).
+- Follow conventional commit message format
+- Use atomic commits with `jj commit`
+- Sign commits when possible (using GPG or SSH signing)
+
+## Version Control Basics
+
+- **ALWAYS use `jj` (Jujutsu) for version control - NEVER use `git` commands**
+- Make atomic commits with `jj commit`
+- Follow [Conventional Commits](https://www.conventionalcommits.org/) format:
+  - `feat:` for new features
+  - `fix:` for bug fixes
+  - `refactor:` for code refactoring
+  - `test:` for adding or updating tests
+  - `docs:` for documentation changes
+  - `chore:` for maintenance tasks
+
+## Committing Changes
+
+**Minimize command overhead when committing:**
+
+**ONLY use these two commands when committing:**
+1. **Review changes**: Run `jj show` to see current changes
+2. **Commit atomically**: Run `jj commit -m "message"` to commit
+
+**Do NOT run:**
+- `jj status` (not needed before committing)
+- `jj diff` (use `jj show` instead)
+- `jj log` (not needed after committing)
+- Any other verification commands unless `jj commit` returns an error
+
+**Example workflow:**
+```bash
+# Review what changed
+jj show
+
+# Commit with descriptive message
+jj commit -m "fix: initialize database on launch to handle empty state"
+
+# That's it! No need for jj status, jj diff, jj log, or other verification commands
+```
+
+**Important:**
+- `jj commit` is atomic and will report errors if it fails
+- Trust the command - if it succeeds, the commit is complete
+- Only investigate further if you see an error message
+- `jj status` and `jj diff` are fine for exploration/debugging, but not needed as part of the commit workflow
+
+## Jujutsu Workflow Integration
+
+### Commit Message Format
+```
+<type>(<scope>): <description>
+
+[optional body]
+
+[optional footer]
+```
+
+#### Types
+- `feat`: new feature
+- `fix`: bug fix
+- `docs`: documentation changes
+- `style`: formatting changes
+- `refactor`: code refactoring
+- `test`: adding tests
+- `chore`: maintenance tasks
+- `ci`: automation tasks
+- `ai`: modifications to llm configuration
+
+#### Examples
+```
+feat(bash): add rust development tools installer
+
+Implement comprehensive installer for modern Rust-based CLI tools including
+error handling, progress feedback, and dependency checking.
+
+feat(jj): enhance log aliases with better filtering
+
+- Add mine() revset for personal commits
+- Improve default() revset with recent() filter
+- Add statistical output to log commands
+
+fix(setup): resolve symlink creation on existing files
+
+Handle case where target symlinks already exist by checking and removing
+stale links before creating new ones.
+
+docs: update installation instructions
+
+Add troubleshooting section and prerequisites clarification.
+```

AGENTS.md

@@ -11,19 +11,9 @@ Follow best practices that a principal level programmer would use when implement
 - **Scripts**: Implement scripts in separate files (bash, python, etc.) rather than embedding them as inline strings in YAML/TOML/JSON.
 - **Dependencies**: Use current versions of dependencies, including GitHub Actions. Update dependencies to latest versions when adding or modifying code.
 
-## Source Control (`jj`)
+## Version Control
 
-- Use `jj` exclusively for version control.
-- **Initialization**: If the current repo is a git repo but not a jj project, initialize it with `jj git init` before any version control operations. This ensures no git commands will ever be run.
-- **Confirmation**: Show changed files and stats (e.g. `jj diff --stat`) and ALWAYS ask the user for confirmation before creating a commit.
-- **Commit**: `jj commit -m "type(scope): description"` (Atomic: describes current change and creates new one)
-- **Sync**: NEVER sync with remote repository. Allow the user to sync manually outside of the agent.
-
-## Commits
-
-- **Style**: Conventional Commits.
-- **Types**: `feat`, `fix`, `docs`, `chore`, `refactor`.
-- **Format**: `type(scope): concise imperative description`.
+See [`.ai/agents/VERSION_CONTROL.md`](.ai/agents/VERSION_CONTROL.md) for comprehensive version control guidelines using Jujutsu (jj).
 
 ## Documentation