feat(core): rename .auto-claude data folder to .aperant

.claude/commands/setup-statusline.md

@@ -80,7 +80,7 @@ Output: Raw JSON status data
 
 ## Status File
 
-Auto-build writes status to `.auto-claude-status` in your project root:
+Auto-build writes status to `.aperant-status` in your project root:
 
 ```json
 {
@@ -121,7 +121,7 @@ When active, you'll see these indicators:
 ## Troubleshooting
 
 ### Status not showing?
-1. Check if `.auto-claude-status` exists in your project root
+1. Check if `.aperant-status` exists in your project root
 2. Verify the path to `statusline.py` is correct
 3. Try running the command manually: `python auto-claude/statusline.py --format compact`
 

.gitignore

@@ -54,13 +54,16 @@ lerna-debug.log*
 .worktrees/
 
 # ===========================
-# Auto Claude Generated
+# Aperant Generated
 # ===========================
+.aperant/
 .auto-claude/
 .planning/
 .planning-archive/
 .auto-build-security.json
+.aperant-security.json
 .auto-claude-security.json
+.aperant-status
 .auto-claude-status
 .claude_settings.json
 .update-metadata.json

CLAUDE.md

@@ -82,10 +82,10 @@ Your context window will be automatically compacted as it approaches its limit,
 
 ### Resetting PR Review State
 
-To fully clear all PR review data so reviews run fresh, delete/reset these three things in `.auto-claude/github/`:
+To fully clear all PR review data so reviews run fresh, delete/reset these three things in `.aperant/github/`:
 
-1. `rm .auto-claude/github/pr/logs_*.json` — review log files
-2. `rm .auto-claude/github/pr/review_*.json` — review result files
+1. `rm .aperant/github/pr/logs_*.json` — review log files
+2. `rm .aperant/github/pr/review_*.json` — review result files
 3. Reset `pr/index.json` to `{"reviews": [], "last_updated": null}`
 4. Reset `bot_detection_state.json` to `{"reviewed_commits": {}}` — this is the gatekeeper; without clearing it, the bot detector skips already-seen commits
 
@@ -217,7 +217,7 @@ const readTool = tool({
 
 ### Spec Directory Structure
 
-Each spec in `.auto-claude/specs/XXX-name/` contains: `spec.md`, `requirements.json`, `context.json`, `implementation_plan.json`, `qa_report.md`, `QA_FIX_REQUEST.md`
+Each spec in `.aperant/specs/XXX-name/` contains: `spec.md`, `requirements.json`, `context.json`, `implementation_plan.json`, `qa_report.md`, `QA_FIX_REQUEST.md`
 
 ### Memory System (Graphiti)
 
@@ -355,5 +355,5 @@ npm run dev        # Development mode with HMR
 npm run dev:debug  # Debug mode with verbose output
 npm run dev:mcp    # Electron MCP server for AI debugging
 
-# Project data: .auto-claude/specs/ (gitignored)
+# Project data: .aperant/specs/ (gitignored)
 ```

apps/desktop/e2e/flows.e2e.ts

@@ -231,9 +231,9 @@ test.describe('E2E Flow Verification (Mock-based)', () => {
     const projectPath = TEST_PROJECT_DIR;
     expect(existsSync(projectPath)).toBe(true);
 
-    // Check for auto-claude directory detection
-    const autoBuildPath = path.join(projectPath, 'auto-claude');
-    expect(existsSync(autoBuildPath)).toBe(true);
+    // Check for aperant directory detection
+    const aperantPath = path.join(projectPath, '.aperant');
+    expect(existsSync(aperantPath)).toBe(true);
 
     cleanupTestEnvironment();
   });

apps/desktop/prompts/coder.md

@@ -12,7 +12,7 @@ You are continuing work on an autonomous development task. This is a **FRESH con
 environment at the start of each prompt in the "YOUR ENVIRONMENT" section. Pay close attention to:
 
 - **Working Directory**: This is your root - all paths are relative to here
-- **Spec Location**: Where your spec files live (usually `./auto-claude/specs/{spec-name}/`)
+- **Spec Location**: Where your spec files live (usually `./.aperant/specs/{spec-name}/`)
 - **Isolation Mode**: If present, you are in an isolated worktree (see below)
 
 **RULES:**
@@ -57,9 +57,9 @@ You may see absolute paths like `/e/projects/myapp/prod/src/file.ts` in:
 ```bash
 # Verify you're still in the worktree
 pwd
-# Should show: .../.auto-claude/worktrees/tasks/{spec-name}/
+# Should show: .../.aperant/worktrees/tasks/{spec-name}/
 # Or (legacy): .../.worktrees/{spec-name}/
-# Or (PR review): .../.auto-claude/github/pr/worktrees/{pr-number}/
+# Or (PR review): .../.aperant/github/pr/worktrees/{pr-number}/
 # NOT: /path/to/main/project
 ```
 
@@ -140,7 +140,7 @@ pwd && ls -la
 find . -name "implementation_plan.json" -type f 2>/dev/null | head -5
 
 # 3. Set SPEC_DIR based on what you find (example - adjust path as needed)
-SPEC_DIR="./auto-claude/specs/YOUR-SPEC-NAME"  # Replace with actual path from step 2
+SPEC_DIR="./.aperant/specs/YOUR-SPEC-NAME"  # Replace with actual path from step 2
 
 # 4. Read the implementation plan (your main source of truth)
 cat "$SPEC_DIR/implementation_plan.json"
@@ -791,7 +791,7 @@ The system **automatically scans for secrets** before every commit. If secrets a
    api_key = os.environ.get("API_KEY")
    ```
 3. **Update .env.example** - Add placeholder for the new variable
-4. **Re-stage and retry** - `git add . ':!.auto-claude' && git commit ...`
+4. **Re-stage and retry** - `git add . ':!.aperant' && git commit ...`
 
 **If it's a false positive:**
 - Add the file pattern to `.secretsignore` in the project root
@@ -803,22 +803,22 @@ The system **automatically scans for secrets** before every commit. If secrets a
 # FIRST: Make sure you're in the working directory root (check YOUR ENVIRONMENT section at top)
 pwd  # Should match your working directory
 
-# Add all files EXCEPT .auto-claude directory (spec files should never be committed)
-git add . ':!.auto-claude'
+# Add all files EXCEPT .aperant directory (spec files should never be committed)
+git add . ':!.aperant'
 
 # If git add fails with "pathspec did not match", you have a path problem:
 # 1. Run pwd to see where you are
 # 2. Run git status to see what git sees
 # 3. Adjust your paths accordingly
 
-git commit -m "auto-claude: Complete [subtask-id] - [subtask description]
+git commit -m "aperant: Complete [subtask-id] - [subtask description]
 
 - Files modified: [list]
 - Verification: [type] - passed
 - Phase progress: [X]/[Y] subtasks complete"
 ```
 
-**CRITICAL**: The `:!.auto-claude` pathspec exclusion ensures spec files are NEVER committed.
+**CRITICAL**: The `:!.aperant` pathspec exclusion ensures spec files are NEVER committed.
 These are internal tracking files that must stay local.
 
 ### DO NOT Push to Remote
@@ -851,7 +851,7 @@ Next phase (if applicable): [phase-name]
 === END SESSION N ===
 ```
 
-**Note:** The `build-progress.txt` file is in `.auto-claude/specs/` which is gitignored.
+**Note:** The `build-progress.txt` file is in `.aperant/specs/` which is gitignored.
 Do NOT try to commit it - the framework tracks progress automatically.
 
 ---
@@ -881,7 +881,7 @@ All subtasks completed!
 Workflow type: [type]
 Total phases: [N]
 Total subtasks: [N]
-Branch: auto-claude/[feature-name]
+Branch: aperant/[feature-name]
 
 Ready for human review and merge.
 ```

apps/desktop/prompts/planner.md

@@ -741,7 +741,7 @@ The following files are gitignored and should NOT be committed:
 - `init.sh` - tracked locally only
 - `build-progress.txt` - tracked locally only
 
-These files live in `.auto-claude/specs/` which is gitignored. The orchestrator handles syncing them between worktrees and the main project.
+These files live in `.aperant/specs/` which is gitignored. The orchestrator handles syncing them between worktrees and the main project.
 
 **Only code changes should be committed** - spec metadata stays local.
 

apps/desktop/prompts/qa_fixer.md

@@ -11,10 +11,10 @@ You are the **QA Fix Agent** in an autonomous development process. The QA Review
 ### NEVER edit qa_report.md
 The `qa_report.md` file belongs to the QA Reviewer. You must NEVER modify it. The reviewer writes the verdict; you implement fixes. If you change the report status (e.g., to "FIXES_APPLIED"), the orchestrator won't recognize it as a valid verdict and your fixes will be wasted.
 
-### Fix in the PROJECT SOURCE, not in .auto-claude/specs/
-All your code changes, documentation additions, and new files must go into the **project source tree** (the actual codebase). Never create deliverable files inside `.auto-claude/specs/` — that directory contains gitignored metadata (spec, plan, QA report). The QA reviewer evaluates the project source, not spec artifacts.
+### Fix in the PROJECT SOURCE, not in .aperant/specs/
+All your code changes, documentation additions, and new files must go into the **project source tree** (the actual codebase). Never create deliverable files inside `.aperant/specs/` — that directory contains gitignored metadata (spec, plan, QA report). The QA reviewer evaluates the project source, not spec artifacts.
 
-**Example:** If QA says "missing route inventory document", create it in the project root (e.g., `docs/route-policy.md` or `ROUTE_POLICY.md`), NOT in `.auto-claude/specs/route_access_policy.md`.
+**Example:** If QA says "missing route inventory document", create it in the project root (e.g., `docs/route-policy.md` or `ROUTE_POLICY.md`), NOT in `.aperant/specs/route_access_policy.md`.
 
 ### Fix CODE issues with CODE, not documentation
 If QA reports a missing test, write the test. If QA reports a code bug, fix the code. Don't write a markdown document explaining why the code is fine — write the code that makes it fine.
@@ -204,7 +204,7 @@ Escaping the worktree causes:
 pwd
 
 # 2. Verify the target is within your worktree
-# If pwd shows: /path/to/.auto-claude/worktrees/tasks/spec-name/
+# If pwd shows: /path/to/.aperant/worktrees/tasks/spec-name/
 # Then: cd ./apps/desktop  ✅ SAFE
 # But:  cd /path/to/parent/project  ❌ FORBIDDEN - ESCAPES ISOLATION
 
@@ -338,8 +338,8 @@ ls -la [path-to-files]  # Make sure the path is correct from your current locati
 # FIRST: Make sure you're in the working directory root
 pwd  # Should match your working directory
 
-# Add all files EXCEPT .auto-claude directory (spec files should never be committed)
-git add . ':!.auto-claude'
+# Add all files EXCEPT .aperant directory (spec files should never be committed)
+git add . ':!.aperant'
 
 # If git add fails with "pathspec did not match", you have a path problem:
 # 1. Run pwd to see where you are
@@ -360,7 +360,7 @@ Verified:
 QA Fix Session: [N]"
 ```
 
-**CRITICAL**: The `:!.auto-claude` pathspec exclusion ensures spec files are NEVER committed.
+**CRITICAL**: The `:!.aperant` pathspec exclusion ensures spec files are NEVER committed.
 
 **NOTE**: Do NOT push to remote. All work stays local until user reviews and approves.
 
@@ -490,7 +490,7 @@ npx prisma migrate dev --name [name]
 
 ### Write Deliverables to the Project, Not Spec Artifacts
 - All new files (docs, tests, code) go in the project source tree
-- NEVER create deliverable files in `.auto-claude/specs/` — that directory is gitignored metadata
+- NEVER create deliverable files in `.aperant/specs/` — that directory is gitignored metadata
 
 ### Git Configuration - NEVER MODIFY
 **CRITICAL**: You MUST NOT modify git user configuration. Never run:

apps/desktop/prompts/qa_reviewer.md

@@ -480,7 +480,7 @@ cat > qa_report.md << 'EOF'
 [QA Report content]
 EOF
 
-# Note: qa_report.md and implementation_plan.json are in .auto-claude/specs/ (gitignored)
+# Note: qa_report.md and implementation_plan.json are in .aperant/specs/ (gitignored)
 # Do NOT commit them - the framework tracks QA status automatically
 # Only commit actual code changes to the project
 ```
@@ -517,7 +517,7 @@ Once fixes are complete:
 
 EOF
 
-# Note: QA_FIX_REQUEST.md and implementation_plan.json are in .auto-claude/specs/ (gitignored)
+# Note: QA_FIX_REQUEST.md and implementation_plan.json are in .aperant/specs/ (gitignored)
 # Do NOT commit them - the framework tracks QA status automatically
 # Only commit actual code fixes to the project
 ```

apps/desktop/src/__tests__/e2e/smoke.test.ts

@@ -127,7 +127,7 @@ function setupTestDirs(): void {
   TEST_PROJECT_PATH = path.join(TEST_DIR, 'test-project');
   mkdirSync(TEST_PROJECT_PATH, { recursive: true });
   // Create a minimal project structure
-  mkdirSync(path.join(TEST_PROJECT_PATH, '.auto-claude'), { recursive: true });
+  mkdirSync(path.join(TEST_PROJECT_PATH, '.aperant'), { recursive: true });
 }
 
 // Cleanup test directories

apps/desktop/src/__tests__/integration/rate-limit-subtask-recovery.test.ts

@@ -23,7 +23,7 @@ let PLAN_PATH: string;
 // Setup test directories
 function setupTestDirs(): void {
   TEST_DIR = mkdtempSync(path.join(tmpdir(), 'rate-limit-recovery-test-'));
-  TEST_SPEC_DIR = path.join(TEST_DIR, '.auto-claude/specs/001-test-feature');
+  TEST_SPEC_DIR = path.join(TEST_DIR, '.aperant/specs/001-test-feature');
   PLAN_PATH = path.join(TEST_SPEC_DIR, 'implementation_plan.json');
   mkdirSync(TEST_SPEC_DIR, { recursive: true });
 }

apps/desktop/src/__tests__/integration/task-lifecycle.test.ts

@@ -94,7 +94,7 @@ function setupTestDirs(): void {
   // Create secure temp directory with random suffix
   TEST_DIR = mkdtempSync(path.join(tmpdir(), 'task-lifecycle-test-'));
   TEST_PROJECT_PATH = path.join(TEST_DIR, 'test-project');
-  TEST_SPEC_DIR = path.join(TEST_PROJECT_PATH, '.auto-claude/specs/001-test-feature');
+  TEST_SPEC_DIR = path.join(TEST_PROJECT_PATH, '.aperant/specs/001-test-feature');
   mkdirSync(TEST_SPEC_DIR, { recursive: true });
 }
 

apps/desktop/src/__tests__/setup.ts

@@ -48,7 +48,7 @@ if (typeof global.requestAnimationFrame === 'undefined') {
 }
 
 // Test data directory for isolated file operations
-export const TEST_DATA_DIR = '/tmp/auto-claude-ui-tests';
+export const TEST_DATA_DIR = '/tmp/aperant-ui-tests';
 
 // Create fresh test directory before each test
 beforeEach(() => {

apps/desktop/src/main/__tests__/file-watcher.test.ts

@@ -74,7 +74,7 @@ describe('FileWatcher concurrency', () => {
   // -------------------------------------------------------------------------
   describe('deduplication: second watch() with same specDir is a no-op', () => {
     it('should only create one FSWatcher when watch() is called twice with the same specDir while the first is still in-flight', async () => {
-      const specDir = '/project/.auto-claude/specs/001-task';
+      const specDir = '/project/.aperant/specs/001-task';
       const taskId = 'task-1';
 
       // To create a real async gap we need an existing watcher whose close() is slow.
@@ -111,8 +111,8 @@ describe('FileWatcher concurrency', () => {
   describe('supersession: watch() with different specDir replaces the in-flight call', () => {
     it('should let the second call win when the first is awaiting close()', async () => {
       const taskId = 'task-2';
-      const specDir1 = path.join('/project', '.auto-claude', 'specs', '001-first');
-      const specDir2 = path.join('/project', '.auto-claude', 'specs', '002-second');
+      const specDir1 = path.join('/project', '.aperant', 'specs', '001-first');
+      const specDir2 = path.join('/project', '.aperant', 'specs', '002-second');
 
       // First call installs an existing watcher (simulate: the watcher for
       // specDir1 is already set up so the second watch() needs to close it).
@@ -148,8 +148,8 @@ describe('FileWatcher concurrency', () => {
 
     it('first watch() bails when pendingWatches changes to a different specDir', async () => {
       const taskId = 'task-super';
-      const specDir1 = path.join('/project', '.auto-claude', 'specs', 'super-first');
-      const specDir2 = path.join('/project', '.auto-claude', 'specs', 'super-second');
+      const specDir1 = path.join('/project', '.aperant', 'specs', 'super-first');
+      const specDir2 = path.join('/project', '.aperant', 'specs', 'super-second');
 
       // Make the first watcher's close() slow so we can interleave.
       let resolveFirstClose!: () => void;
@@ -187,7 +187,7 @@ describe('FileWatcher concurrency', () => {
   describe('cancellation: unwatch() during in-flight watch() prevents watcher creation', () => {
     it('should not create a watcher when unwatch() is called before the async gap resolves', async () => {
       const taskId = 'task-3';
-      const specDir = '/project/.auto-claude/specs/003-cancel';
+      const specDir = '/project/.aperant/specs/003-cancel';
 
       // There's no pre-existing watcher, so watch() won't call close(). But it
       // does go async (chokidar.watch is sync but we can test the cancellation
@@ -207,7 +207,7 @@ describe('FileWatcher concurrency', () => {
       );
 
       // Start a second watch() — it will await the slow close().
-      const specDir2 = '/project/.auto-claude/specs/003-cancel-v2';
+      const specDir2 = '/project/.aperant/specs/003-cancel-v2';
       const watchPromise = fw.watch(taskId, specDir2);
 
       // While watch() is in-flight, call unwatch().
@@ -231,8 +231,8 @@ describe('FileWatcher concurrency', () => {
     it('should cancel pending watch() calls and clear pendingWatches', async () => {
       const taskId1 = 'task-4a';
       const taskId2 = 'task-4b';
-      const specDir1 = '/project/.auto-claude/specs/004a';
-      const specDir2 = '/project/.auto-claude/specs/004b';
+      const specDir1 = '/project/.aperant/specs/004a';
+      const specDir2 = '/project/.aperant/specs/004b';
 
       // Set up slow-close scenario for taskId1 (so watch() is in-flight).
       await fw.watch(taskId1, specDir1);
@@ -243,7 +243,7 @@ describe('FileWatcher concurrency', () => {
       );
 
       // Start a new watch for taskId1 with a different specDir — this is now in-flight.
-      const newSpecDir1 = '/project/.auto-claude/specs/004a-v2';
+      const newSpecDir1 = '/project/.aperant/specs/004a-v2';
       const watchPromise1 = fw.watch(taskId1, newSpecDir1);
 
       // Start a fresh watch for taskId2.
@@ -262,7 +262,7 @@ describe('FileWatcher concurrency', () => {
 
       // pendingWatches should be cleared (we verify indirectly: a fresh
       // watch() call for taskId1 must succeed without treating it as a duplicate).
-      const specDirFresh = path.join('/project', '.auto-claude', 'specs', '004a-fresh');
+      const specDirFresh = path.join('/project', '.aperant', 'specs', '004a-fresh');
       await fw.watch(taskId1, specDirFresh);
       expect(fw.isWatching(taskId1)).toBe(true);
       expect(fw.getWatchedSpecDir(taskId1)).toBe(specDirFresh);
@@ -275,7 +275,7 @@ describe('FileWatcher concurrency', () => {
   describe('getWatchedSpecDir()', () => {
     it('returns the specDir that was passed to watch()', async () => {
       const taskId = 'task-5';
-      const specDir = path.join('/project', '.auto-claude', 'specs', '005-specdir');
+      const specDir = path.join('/project', '.aperant', 'specs', '005-specdir');
 
       await fw.watch(taskId, specDir);
 
@@ -288,8 +288,8 @@ describe('FileWatcher concurrency', () => {
 
     it('returns updated specDir after re-watch with different specDir', async () => {
       const taskId = 'task-5b';
-      const specDir1 = path.join('/project', '.auto-claude', 'specs', '005b-first');
-      const specDir2 = path.join('/project', '.auto-claude', 'specs', '005b-second');
+      const specDir1 = path.join('/project', '.aperant', 'specs', '005b-first');
+      const specDir2 = path.join('/project', '.aperant', 'specs', '005b-second');
 
       await fw.watch(taskId, specDir1);
       expect(fw.getWatchedSpecDir(taskId)).toBe(specDir1);

apps/desktop/src/main/__tests__/insights-config.test.ts

@@ -45,7 +45,7 @@ describe('InsightsConfig', () => {
 
   it('should build process env with profile settings', async () => {
     const config = new InsightsConfig();
-    vi.spyOn(config, 'loadAutoBuildEnv').mockReturnValue({ CUSTOM_ENV: '1' });
+    vi.spyOn(config, 'loadAperantEnv').mockReturnValue({ CUSTOM_ENV: '1' });
 
     const env = await config.getProcessEnv();