docs: create TASK_067 files

Author: cahaseler

.claude/plans/067.md

@@ -0,0 +1,36 @@
+# Plan: 067
+
+Captured: 2025-09-17T01:37:10.549Z
+
+## Fix GitHub Release Pipeline - mock.module Cross-Test Pollution
+
+### Root Cause Identified
+The CI tests are failing due to `mock.module` pollution between test files. Specifically:
+
+1. `index.test.ts` uses `mock.module('./coderabbit', ...)` to mock the entire coderabbit module
+2. This mock returns `{ success: true, review: 'CodeRabbit review content' }`
+3. In CI, this mock persists and affects `coderabbit.test.ts` tests
+4. The coderabbit tests expect their own mocks to work but get the index.test.ts mock instead
+
+### Evidence:
+- CI errors show "CodeRabbit review content" - a string only found in index.test.ts
+- Tests run at 1ms in CI (mocked speed) but return wrong values
+- Tests pass locally but fail in CI (different test execution order/parallelization)
+- The mock.module calls in index.test.ts aren't properly isolated
+
+### Solution:
+Fix the mock isolation in `index.test.ts` by:
+
+1. **Add proper cleanup in afterEach**:
+   - Call `mock.restore()` after each test
+   - Ensure mock.module effects don't persist
+
+2. **Or switch to dependency injection pattern**:
+   - Instead of mock.module, pass mocked dependencies directly
+   - This matches the pattern used in coderabbit.test.ts
+
+3. **Verify fix**:
+   - Run tests in different orders to ensure no pollution
+   - Test passes in CI environment
+
+This will fix the release pipeline by preventing test interference.

.claude/tasks/TASK_067.md

@@ -0,0 +1,49 @@
+# TASK_067: Fix GitHub Release Pipeline - mock.module Cross-Test Pollution
+
+**Purpose**: Fix CI test failures in GitHub release pipeline caused by mock.module pollution between test files, specifically where index.test.ts mocks persist and interfere with coderabbit.test.ts execution.
+
+**Status**: in_progress
+
+**Started**: 2025-09-17 21:37
+
+## Requirements
+- [ ] Analyze current mock.module usage in index.test.ts and coderabbit.test.ts
+- [ ] Identify the specific mock pollution causing CI failures
+- [ ] Fix mock isolation in index.test.ts by adding proper cleanup
+- [ ] Ensure mock.module effects don't persist between test files
+- [ ] Verify tests pass in different execution orders
+- [ ] Validate fix works in CI environment
+- [ ] Document the solution for future reference
+
+## Success Criteria
+- [ ] All tests pass consistently in CI pipeline
+- [ ] No mock pollution between test files
+- [ ] Tests return expected values (not "CodeRabbit review content" from wrong mock)
+- [ ] GitHub release pipeline completes successfully
+- [ ] Tests maintain proper isolation and can run in any order
+
+## Technical Approach
+### Root Cause Analysis
+- `index.test.ts` uses `mock.module('./coderabbit', ...)` returning `{ success: true, review: 'CodeRabbit review content' }`
+- This mock persists in CI and affects `coderabbit.test.ts` tests
+- Tests expect their own mocks but get the index.test.ts mock instead
+- Results in 1ms execution times (mocked speed) with wrong return values
+
+### Solution Options
+1. **Add proper cleanup in afterEach** (Primary approach):
+   - Call `mock.restore()` after each test in index.test.ts
+   - Ensure mock.module effects don't persist
+
+2. **Switch to dependency injection** (Alternative):
+   - Pass mocked dependencies directly instead of using mock.module
+   - Match the pattern used in coderabbit.test.ts
+
+## Current Focus
+Implementing proper mock cleanup in index.test.ts to prevent cross-test pollution while maintaining test functionality.
+
+## Next Steps
+1. Examine current test files to understand mock usage patterns
+2. Implement mock.restore() calls in appropriate locations
+3. Test locally with different execution orders
+4. Validate fix resolves CI failures
+5. Update release pipeline if needed