Fix mock path misalignment in src/tests/commandExecutor.test.ts

Problem: The vi.mock() calls use incorrect relative paths that don't match the actual imports in src/commands/utils/commandExecutor.ts, causing mocks to not be applied during tests.

Required changes in src/tests/commandExecutor.test.ts:

1. Around line 21, change:
   FROM: vi.mock('../commands/base/CommandRegistry.js', () => ({
   TO: vi.mock('../base/CommandRegistry.js', () => ({

   Explanation: Remove the extra '/commands' segment to match the SUT's import path.

2. Around line 27, change:
   FROM: vi.mock('../utils/errorContextBuilder.js', () => ({
   TO: vi.mock('../../utils/errorContextBuilder.js', () => ({

   Explanation: Add the missing '../' to navigate up two directory levels, matching the SUT's import path.

Context: The test file is located at src/tests/commandExecutor.test.ts and the system under test (SUT) is at src/commands/utils/commandExecutor.ts. The mock paths must exactly match the import specifiers used in the SUT for Vitest to properly intercept and mock these dependencies.

---

Fix mock path misalignment in src/tests/commandRegistry.test.ts

ISSUE:
The vi.mock() calls don't match the actual import paths used by CommandRegistry.ts, preventing proper mocking during tests.

CURRENT STATE (INCORRECT):

• Line 26: vi.mock('../utils/logConfig.js', ...)
• Line 33: vi.mock('../config/env.js', ...)

REQUIRED STATE (CORRECT):

• Line 26: vi.mock('../../utils/logConfig.js', ...)
• Line 33: vi.mock('../../config/env.js', ...)

REASON:
CommandRegistry.ts imports from:

• Line 13: '../../utils/logConfig.js'
• Line 14: '../../config/env.js'

Mock module IDs must exactly match the import paths in the system under test (SUT) for Vitest to intercept them.

ACTION:
Update both vi.mock() calls in src/tests/commandRegistry.test.ts (lines 26-36) by adding one additional '../' to each path. Keep all mock implementations unchanged (StartupLogger with logCommandRegistration/logProcessorRegistration, and isAdminUser/getAdminUsers functions).

FILE: src/tests/commandRegistry.test.ts
LINES: 26-36

---

In src/tests/setEmailCommand.test.ts, the formatEmailForDisplay function is mocked and imported from the wrong module, causing test mocks to misalign with production code. Fix this by relocating the mock and updating imports:

Step 1: Update the emailManager mock (around line 13-19)
Remove formatEmailForDisplay from this mock block:
vi.mock('../utils/emailManager.js', () => ({
deliverPendingAgentMessages: vi.fn(),
// REMOVE THIS LINE: formatEmailForDisplay: vi.fn(),
getUserEmailPreferences: vi.fn(),
updateUserEmail: vi.fn(),
validateEmail: vi.fn(),
}));

Step 2: Update the markdownEscape mock (around line 21-23)
Add formatEmailForDisplay to this mock block:
vi.mock('../utils/markdownEscape.js', () => ({
escapeMarkdown: vi.fn((text) => text),
formatEmailForDisplay: vi.fn(), // ADD THIS LINE
}));

Step 3: Update the import statements (around line 42-49)
Change from:
import {
deliverPendingAgentMessages,
formatEmailForDisplay, // REMOVE from here
getUserEmailPreferences,
updateUserEmail,
validateEmail
} from '../utils/emailManager.js';
import { escapeMarkdown } from '../utils/markdownEscape.js';

To:
import {
deliverPendingAgentMessages,
getUserEmailPreferences,
updateUserEmail,
validateEmail
} from '../utils/emailManager.js';
import { escapeMarkdown, formatEmailForDisplay } from '../utils/markdownEscape.js'; // ADD formatEmailForDisplay here

This aligns the test mocks with production code, ensuring formatEmailForDisplay is mocked where SetEmailCommand actually imports it from (markdownEscape module).

---

Use the dev branch as the base code and then PR this to dev branch, make sure that changes made are compatible with the dev branch. All changes should be KISS approach and no over engineering.