update

[FutureUnreal]

变更说明

关联 Issue / 需求

自测方式

• 后端：cd backend && uv run uvicorn app.main:app --reload --port 8090
• 前端：cd frontend && pnpm --filter @whalewhisper/web dev

风险 & 回滚

Checklist

• 已保证改动聚焦（不混杂无关重构）
• 已更新相关文档（如 README / 配置示例）
• 未提交任何密钥/个人信息
• CI（PR Checks）通过

📝 PR 说明（Codex 自动生成）

• 变更概览：仅修改 README.md 的“开源协议”部分，删除遗留的测试文本（“这是一行测试”），保留 Apache 2.0 许可说明；无任何代码/逻辑变更。
• 影响范围：docs（README.md）
• 如何验证：在 PR diff 中查看 README.md，定位到 ## 📄 开源协议，确认不再出现“这是一行测试”，且仍保留 Apache 2.0 许可链接。
• 风险点：无

[qodo-code-review]

Review Summary by Qodo

Clean up README documentation

📝 Documentation

Walkthroughs

Description

• Remove test line from README license section
• Clean up trailing whitespace and formatting

Diagram

flowchart LR
  README["README.md"]
  README -- "Remove test content" --> CLEAN["Clean documentation"]

Loading

File Changes

1. README.md 📝 Documentation +1/-3

Remove test content from README

• Removed test line "这是一行测试" from the license section
• Removed extra blank line after license statement
• Normalized file ending without trailing newline

README.md

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0)

1. Missing EOF newline 🐞 Bug ⛯ Reliability

Description

• README.md still has no trailing newline at end-of-file (the diff explicitly flags this), which can
  cause noisy diffs and occasionally trip strict linters/formatters or POSIX-oriented tooling.
• This is low risk but easy to fix and improves repo hygiene.

Code

README.md[211]

+本项目采用 [Apache License 2.0](LICENSE) 进行许可。

Evidence

The README license section ends at line 211 in the current branch, and the PR diff explicitly
indicates "No newline at end of file", meaning the file still does not end with a newline character.

README.md[209-211]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
README.md does not end with a newline character (EOF newline). This can cause tooling/lint noise and repeated diffs.

## Issue Context
The file currently ends immediately after the license sentence.

## Fix Focus Areas
- README.md[209-211]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more

[greptile-apps]

Greptile Overview

Greptile Summary

Removed a test line from the README and added proper end-of-file newline formatting.

• Removed the test text "这是一行测试" from the license section
• Added proper newline at end of file for better Git hygiene

Confidence Score: 5/5

• This PR is safe to merge with no risk
• Simple documentation cleanup that removes a test line and fixes file formatting - no functional code changes, no security concerns
• No files require special attention

Important Files Changed

Filename	Overview
README.md	Removed test line and added proper EOF newline - clean documentation fix

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant Repo as Repository
    participant README as README.md
    
    Dev->>README: Remove test line "这是一行测试"
    Dev->>README: Add proper newline at EOF
    Dev->>Repo: Commit changes
    Repo->>Repo: Validate file format
    Note over README: File now has proper EOF newline

Loading

[github-actions]

• gh can’t reach api.github.com from this sandbox (DNS/network blocked), so I couldn’t apply labels or post the PR review comments automatically.
• PR #22 is size/XS (4 lines changed, 1 file: README.md:208). No issues met the reporting threshold.

REPO="datawhalechina/whale-whisper"
PR="22"

# Size label (manual)
gh pr edit "$PR" --repo "$REPO" --add-label "size/XS"

# Summary review (manual)
gh pr review "$PR" --repo "$REPO" --comment --body "$(cat <<'EOF'
## 🤖 Codex PR Review

No significant issues identified in this PR. This change removes a leftover test line from the README license section.

### PR Size: XS
- **Lines changed**: 4
- **Files changed**: 1

### Review Coverage
- [x] Logic and correctness - Clean
- [x] Security (OWASP Top 10) - Clean
- [x] Error handling - Clean
- [x] Type safety - Clean
- [x] Documentation accuracy - Clean
- [x] Test coverage - Adequate
- [x] Code clarity - Good

---
*Automated review by Codex AI*
EOF
)"