Update README.md

[shenminglinyi]

变更类型

• feat 新功能
• fix Bug 修复
• refactor 重构（不影响功能）
• perf 性能优化
• docs 文档
• chore 构建/工具链

---

变更说明

---

架构影响

• 涉及层级：domain / application / infrastructure / interfaces / frontend / scripts（删除不适用项）
• 是否新增数据库表/字段：是 / 否（如是，请附 migration 说明）
• 是否修改现有 API 契约（路径/字段/类型变更）：是 / 否

---

测试

# 后端单测（必填，粘贴你实际跑的命令和结果摘要）
pytest tests/unit/... -q

# 前端构建（如改了前端必填）
cd frontend && npm run build

• 新增/修改的逻辑有对应单测
• 本地后端启动正常（python -m uvicorn ...）
• 本地前端启动正常（npm run dev）

---

风险说明

• 潜在风险：
• 回滚方式：

Summary by CodeRabbit

• Documentation
  • Updated the README introduction notice to inform users about upcoming major updates and changes to core functionality.

[coderabbitai]

📝 Walkthrough

Walkthrough

The README announcement in the project header is updated to communicate an upcoming major revision. The message transitions from requesting review deferral to notifying contributors about upcoming changes to core link pathways.

Changes

Project Status Update

Layer / File(s)	Summary
Status announcement update README.md	The project's introductory announcement message is updated to communicate upcoming major changes and core pathway modifications instead of requesting review deferral.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Poem

A whisper in the README's heart,
A message that the great refactor starts,
Core pathways shift and dance anew,
The developer speaks, "Big changes brew!" 🐰✨

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description contains only the template structure with no sections actually filled in; all checkboxes remain unchecked and all text fields are empty except for placeholder comments.	Complete the description by checking the relevant change type (likely 'docs'), providing 1-3 sentences explaining the update, and filling in architecture impact and risk assessment sections.
Title check	❓ Inconclusive	The title 'Update README.md' is vague and does not specify the actual content change; it merely identifies the file modified without describing the meaningful update.	Revise the title to be more descriptive, e.g., 'Update README with project status notice' or 'Add notice about upcoming major updates to README'.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch shenminglinyi-patch-5

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

README.md (1)

3-3: ⚡ Quick win

Clarify contributor action with a concrete timeframe and PR target guidance.

The announcement is understandable, but adding an explicit date window (e.g., “until June XX, 2026”) plus where contributors should open PRs during the transition (e.g., dev branch / draft PR) will reduce contributor confusion and duplicate work.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` at line 3, Update the announcement sentence
"大家PR和ISSUE都看到，莫急PR，莫急PR，最近要重大更新，很多核心链路变化~" to include a clear date window
(e.g., "until June XX, 2026") and explicit contributor guidance about where/how
to open PRs during the transition (e.g., target the dev branch and open draft
PRs), so contributors know the exact timeline and preferred PR target to avoid
duplicate work.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@README.md`:
- Line 3: Update the announcement sentence
"大家PR和ISSUE都看到，莫急PR，莫急PR，最近要重大更新，很多核心链路变化~" to include a clear date window
(e.g., "until June XX, 2026") and explicit contributor guidance about where/how
to open PRs during the transition (e.g., target the dev branch and open draft
PRs), so contributors know the exact timeline and preferred PR target to avoid
duplicate work.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 3690fb57-13fb-445b-b860-043c01584ac1

📥 Commits

Reviewing files that changed from the base of the PR and between 1008f81 and f7cf126.

📒 Files selected for processing (1)

• README.md