docs: update formatting and examples in documentation files

Author: WCY-dt

.github/copilot-instructions.md

@@ -67,7 +67,7 @@ Follow the [Conventional Commits](https://www.conventionalcommits.org/) specific
 
 ### Format
 
-```
+```plaintext
 <type>(<scope>): <description>
 
 [optional body]
@@ -97,12 +97,13 @@ docs(readme): update installation instructions
 test(client): add FileChunkManager unit tests
 refactor(utils): extract ID generation to utils
 ci: add automated testing to GitHub Actions
+chore(dependencies): update dependencies to latest versions
 ```
 
 ### Best Practices
 
-- Use present tense ("add" not "added")
-- Use imperative mood ("move" not "moves")
+- Use present tense (`add` not `added`)
+- Use imperative mood (`move` not `moves`)
 - Keep first line under 72 characters
 - Reference issues/PRs in footer: `Fixes #123`
 - Break long descriptions into body paragraphs

AGENTS.md

@@ -92,7 +92,7 @@ Follow the [Conventional Commits](https://www.conventionalcommits.org/) specific
 
 ### Format
 
-```
+```plaintext
 <type>(<scope>): <description>
 
 [optional body]
@@ -116,18 +116,19 @@ Follow the [Conventional Commits](https://www.conventionalcommits.org/) specific
 ### Examples
 
 ```bash
-feat(client): add dark mode theme support
+feature(client): add dark mode theme support
 fix(server): resolve connection timeout issue
 docs(readme): update installation instructions
 test(client): add FileChunkManager unit tests
 refactor(utils): extract ID generation to utils
 ci: add automated testing to GitHub Actions
+chore(dependencies): update dependencies to latest versions
 ```
 
 ### Best Practices
 
-- Use present tense ("add" not "added")
-- Use imperative mood ("move" not "moves")
+- Use present tense (`add` not `added`)
+- Use imperative mood (`move` not `moves`)
 - Keep first line under 72 characters
 - Reference issues/PRs in footer when applicable
 - Break long descriptions into body paragraphs

CHANGELOG.md

@@ -6,14 +6,11 @@ All notable changes to this project will be documented in this file.
 
 ### Added
 
-- Comprehensive unit tests (170 total: 13 server, 157 client)
-- Vitest testing framework for both client and server
-- Test scripts in package.json (test, test:watch, test:ui)
+- Comprehensive unit tests
 - Automated testing in GitHub Actions CI/CD pipeline
 
 ### Changed
 
-- GitHub Actions workflow now includes build and test steps
 - Improved ID generation algorithm for better reliability
 - Refactored server code to extract testable utility functions
 

CONTRIBUTING.md

@@ -64,14 +64,15 @@ npm run build
 ## Making Changes
 
 1. **Follow the project's coding standards**:
+
    - Use TypeScript for type safety
    - Follow existing code patterns and conventions
    - Keep functions small and focused
    - Write clear, self-documenting code
 
 2. **Write semantic commit messages** following [Conventional Commits](https://www.conventionalcommits.org/):
 
-   ```
+   ```plaintext
    <type>(<scope>): <description>
    
    [optional body]
@@ -82,6 +83,7 @@ npm run build
    **Types**: `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `build`, `ci`, `chore`
 
    **Examples**:
+
    ```bash
    feat(client): add support for drag-and-drop file upload
    fix(server): resolve WebRTC connection timeout
@@ -90,11 +92,13 @@ npm run build
    ```
 
 3. **Write tests** for new features or bug fixes:
+
    - Add unit tests in the appropriate test file
    - Ensure all tests pass before submitting
    - Aim for comprehensive test coverage
 
 4. **Test your changes thoroughly**:
+
    - Test WebRTC connections on different networks
    - Verify file transfers work correctly
    - Check UI responsiveness
@@ -111,17 +115,20 @@ npm run build
 2. **Open a pull request** on the original repository.
 
 3. **Provide a clear description**:
+
    - Explain what changes you made and why
    - Reference any related issues (e.g., "Fixes #123")
    - Include screenshots for UI changes
    - List any breaking changes
 
 4. **Ensure CI checks pass**:
+
    - All tests must pass
    - Code must be properly linted and formatted
    - Build must succeed
 
 5. **Respond to review feedback**:
+
    - Address reviewer comments promptly
    - Make requested changes
    - Re-request review after updates

README.md

@@ -44,34 +44,6 @@ What makes EasyTransfer different? It's these features:
 
 For specific deployment methods, please refer to the [Project Wiki](https://github.com/WCY-dt/EasyTransfer/wiki/Navigator).
 
-## Development
-
-### Client Commands (in `/client` directory)
-
-```bash
-npm run dev       # Start development server
-npm run build     # Build for production
-npm run preview   # Preview production build
-npm run lint      # Run ESLint with auto-fix
-npm run format    # Format code with Prettier
-npm test          # Run tests
-npm run test:watch  # Run tests in watch mode
-npm run test:ui   # Run tests with UI
-```
-
-### Server Commands (in `/server` directory)
-
-```bash
-npm run dev       # Build and start with nodemon
-npm run build     # Compile TypeScript
-npm run start     # Start production server
-npm run lint      # Run ESLint with auto-fix
-npm run format    # Format code with Prettier
-npm test          # Run tests
-npm run test:watch  # Run tests in watch mode
-npm run test:ui   # Run tests with UI
-```
-
 ## Contributing
 
 If you want to contribute code to this project, please refer to the [Contribution Guide](https://github.com/WCY-dt/EasyTransfer/blob/main/CONTRIBUTING.md).

SECURITY.md

@@ -7,11 +7,9 @@ We release patches for security vulnerabilities in the following versions:
 | Component | Version | Supported          |
 | --------- | ------- | ------------------ |
 | Client    | 3.4.x   | :white_check_mark: |
-| Client    | 3.3.x   | :white_check_mark: |
-| Client    | < 3.3   | :x:                |
+| Client    | < 3.4   | :x:                |
 | Server    | 3.4.x   | :white_check_mark: |
-| Server    | 3.3.x   | :white_check_mark: |
-| Server    | < 3.3   | :x:                |
+| Server    | < 3.4   | :x:                |
 
 ## Reporting a Vulnerability