In src/tests/adminCommands.test.ts at line 8, the named imports from
'vitest' are not alphabetized; reorder them alphabetically so the import reads:
afterEach, beforeEach, describe, expect, it, vi (i.e., alphabetize the import
members) and save the file to unblock CI.

In src/tests/adminCommands.test.ts around lines 72 to 76, the test file
imports getCompanyName, GlobalTemplateManager, ValidationService and
SetupCallbackProcessor but never uses them; remove those unused named imports
(or replace the named imports with side-effect imports like import '...';) so
the vi.mock calls remain but no unused bindings exist, ensuring the test file no
longer triggers no-unused-vars.

In src/tests/adminCommands.test.ts around lines 280 to 286, the
mockGroupConfig object uses property names and types that don't match the
GroupConfig interface in src/sdk/types.ts; open src/sdk/types.ts, copy the exact
property names and required types from that GroupConfig definition, then update
the mock object to use those exact keys and value types (including required
optional/nullable fields, correct id types, timestamp formats, and any nested
shapes). Ensure imports/reference to GroupConfig remain correct and the mock
satisfies the interface so the test type-checks.

In src/tests/baseCommand.test.ts around line 4, the vitest named imports are
not alphabetized; reorder the import specifiers into alphabetical order
(afterEach, beforeEach, describe, expect, it, vi) so the import line reads the
members sorted and maintains existing spacing and punctuation.

In src/tests/baseCommand.test.ts around lines 131-134 (and also lines
146-147) the variable adminCommand is declared/assigned but never used; remove
the adminCommand declaration and any assignments or setup related to it (and any
unused imports solely for it) to satisfy no-unused-vars — keep the remaining
test variables intact and run the tests to ensure nothing else depended on
adminCommand.

In src/tests/commandExecutor.test.ts around lines 4 to 11, the BotContext
import path is wrong for tests and the named imports are not alphabetized;
change the BotContext import to ../types/index.js (one level up from
src/tests) and reorder the named imports from 'vitest' and from
'../commands/utils/commandExecutor.js' into alphabetical order (put type-only
imports last or follow your project's grouping rule) so ESLint sort-imports and
module resolution errors are resolved.

In src/tests/commandExecutor.test.ts around lines 19 to 29, the module
specifiers used in vi.mock do not match the actual imports used by the SUT
(src/commands/utils/commandExecutor.ts), causing mocks to not apply; update the
vi.mock calls to use the exact import specifiers used by the SUT (e.g.,
'../base/CommandRegistry.js' and '../../utils/errorContextBuilder.js') or update
your test runner/module resolver to use a shared alias so the mocked paths
precisely match the SUT imports.

In src/tests/commandRegistry.test.ts around lines 4 to 6, the import lines
are wrong: update the BotContext import path from '../../types/index.js' to
'../types' (relative to src/tests) and reorder the vitest named imports
alphabetically (afterEach, beforeEach, describe, expect, it, vi) so the import
list is sorted; make sure to remove any .js extension in the test import and
keep consistent quoting/style with the file.

In src/tests/commandRegistry.test.ts around lines 26 to 35, the mocked
module paths use '../utils/logConfig.js' and '../config/env.js' but the
CommandRegistry under test imports '../../utils/logConfig.js' and
'../../config/env.js'; update the vi.mock calls to use the same relative paths
as the source (../../utils/logConfig.js and ../../config/env.js) so the test
mocks the actual modules CommandRegistry imports, keeping the same mock
implementations (StartupLogger with
logCommandRegistration/logProcessorRegistration and isAdminUser returning
false).

In src/tests/commands.index.test.ts around line 4, the vitest named imports
should be alphabetized to unblock CI; reorder the import list to alphabetical
order (afterEach, beforeEach, describe, expect, it, vi) so the single import
line reads with the names sorted and save the file.

In src/tests/commands.index.test.ts around lines 7 to 31, the large named
import list from '../commands/index.js' is not alphabetically sorted; reorder
all imported identifiers into ascending alphabetical order (A–Z) while
preserving the existing comma/newline formatting and keeping any related grouped
imports intact so the import statement satisfies sort-imports.

In src/tests/enhancedEmailManager.test.ts around lines 33 to 45, the
imported types EmailValidationResult and UserEmailPreferences are unused and
causing ESLint complaints; remove those two type imports from the import list
(leave the other imports intact) so the import statement only brings in the
actual functions and values used by the test file.

In src/tests/enhancedEmailManager....