fix: separate client and server utilities to fix build error

Split lib/utils.ts into:
- lib/utils.ts: Client-safe utilities only (no Node.js imports)
- lib/project-utils.ts: Server-only utilities with Node.js imports

This fixes the Next.js build error where client components were importing
modules that contained Node.js dependencies (fs, path).

All tests pass and build succeeds.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

lib/__tests__/utils.test.ts

@@ -1,11 +1,4 @@
-import { formatVersion, formatFileSize, formatDateTime, getProjectDisplayName } from '../utils';
-
-// Mock fs module
-const fs = require('fs');
-jest.mock('fs', () => ({
-  ...jest.requireActual('fs'),
-  readFileSync: jest.fn(),
-}));
+import { formatVersion, formatFileSize, formatDateTime } from '../utils';
 
 describe('formatVersion', () => {
   test('应该将下划线替换为点号', () => {
@@ -70,39 +63,3 @@ describe('formatDateTime', () => {
     expect(formatDateTime(date)).toBe('2024-01-05 09:05');
   });
 });
-
-describe('getProjectDisplayName', () => {
-  const originalAliases = {
-    'FT': '外放构建',
-    'FT_DEV': '开发构建',
-  };
-
-  beforeEach(() => {
-    // Mock the aliases file
-    fs.readFileSync.mockReturnValue(JSON.stringify(originalAliases));
-  });
-
-  afterEach(() => {
-    jest.clearAllMocks();
-  });
-
-  it('should return display name for aliased project', () => {
-    expect(getProjectDisplayName('FT')).toBe('外放构建');
-  });
-
-  it('should return directory name when no alias exists', () => {
-    expect(getProjectDisplayName('UNKNOWN')).toBe('UNKNOWN');
-  });
-
-  it('should return directory name when aliases file is empty', () => {
-    fs.readFileSync.mockReturnValue('{}');
-    expect(getProjectDisplayName('FT')).toBe('FT');
-  });
-
-  it('should return directory name when aliases file cannot be read', () => {
-    fs.readFileSync.mockImplementation(() => {
-      throw new Error('File not found');
-    });
-    expect(getProjectDisplayName('FT')).toBe('FT');
-  });
-});