feat(backend): 同步 ZZZ backend 演进（open_game + click/input/screen_area CRUD，7→11 tool）

[DoctorReid]

概述

同步 ZZZ（绝区零一条龙）backend 最新演进到 SR。open_and_enter_game 被更细粒度工具取代，7 → 11 tool。照搬 ZZZ 已验证实现 + token 清单（common-package-sync.md §5）适配。承接已关闭的 #604（其 review 修复 c4743d81 未进 main，本 PR 一并带入）。

工具变化（7 → 11）

新增	取代/说明
open_game(enter=True, block=True)	取代 open_and_enter_game；enter=False 只打开不登录（分步驱动登录）
click_game(x, y, press_time=0)	1080p 游戏空间坐标点击
input_text(text, use_clipboard=None)	剪贴板/逐键（跟 game_config.type_input_way，可覆盖），返回脱敏文本
upsert_screen_area(...)	screen area CRUD（新增/更新，写 yml + reload）
delete_screen_area(screen_name, area_name)	screen area 删除

保留：check_game_window / capture_game_screen / analyze_screen（+screenshot 参）/ close_game / get_run_status / stop_run。

改动

• common screen_info.py：+upsert_area / remove_area_by_name（screen_area 工具依赖，one_dragon 公共框架）
• backend backend_context.py：+ click_game / input_text / upsert_screen_area / delete_screen_area 切片 + analyze 按截图文件/图名解析；重提 RunSlot executor shutdown（ZZZ 仍未修，照搬会丢失，SR 保留修复）
• mcp/app.py：open_and_enter_game → open_game + 4 新工具
• docs：mcp 工具表 7→11（ZZZ doc 漏列 upsert/delete_screen_area，SR 补上）；architecture/mcp/http 等随 ZZZ 最新
• feat: MCP backend 运行态完善 + AI 编码 harness + runtime 启动器 + dev skills #604 review 修复（c4743d81）：build_full.bat config 目录、common-sync 表格 \|、daemon 精确 argv 匹配、backend_context executor shutdown —— 本 PR 带入 main

验证

• 108 测试全过（sr-od-test be58691：test_mcp_app 更新 + 5 新测试含 test_click_game/input_text/run_slot/close_game + conftest）
• pyright 0 error（backend + screen_info）
• 残留 grep CLEAN（含 ZPcController→SrPcController、spec 路径 2026-07-05、裸端口等 token 缺口）
• 静态装配 ok；RunSlot.shutdown 就位

照搬 ZZZ commit

2d73af97(open_game+click+input MCP) · 80bf5bd3(input_text 切片) · 7b102f38(click_game 切片) · 9972ba18(screen_info area CRUD) · 53bc2823(analyze 按截图解析) · 8087f220(mcp doc 7→9)

端口

主 server 24001、daemon 24000（避与 ZZZ 同机冲突）。

🤖 Generated with Claude Code

Summary by CodeRabbit

• 新功能
  • 新增后端 MCP/HTTP（/game/*）能力：支持一条龙与独立应用运行、任务状态查询，并提供常驻远程管理（启动/停止/重启）。
  • 新增“应用通知设置”，并支持上下文通知弹窗展示。
• 改进与修复
  • OCR 能力增强：加入 PP-OCRv6，模型/字典自动识别与更稳的加载控制；改进屏幕作用域匹配。
  • 界面滚动组件整体优化（FastScrollArea），并增强“更多/通知”联动；自动更新改为密码保护。
• 文档与构建
  • 更新开发/测试与打包构建流程（含 CI 与 RuntimeLauncher 同步/清理方式）。

[coderabbitai]

Walkthrough

本次 PR 新增 sr_od 后端服务及 MCP/HTTP 适配器，并同步重构通知、OCR、屏幕匹配、运行时打包、开发规范、基础工具和 Qt 界面。

Changes

后端服务与 MCP 适配

Layer / File(s)	Summary
后端核心与数据契约 src/sr_od/backend/*	新增 SrBackendContext、RunSlot、结构化返回模型和 operation 注册能力。
MCP、HTTP 与服务入口 src/sr_od/backend/entry/*, src/sr_od/backend/mcp/*, src/sr_od/backend/http/*	将后端能力注册为 MCP 工具、prompts 和 HTTP 路由，并由 uvicorn 统一启动。
服务管理与 GUI 接入 tools/mcp/daemon/*, src/sr_od/gui/interface/devtools/*	新增 daemon、启动脚本和开发工具页面，用于管理服务进程并展示状态与日志。

运行时与模型执行

Layer / File(s)	Summary
打包、代码同步与启动器 deploy/*, src/one_dragon/envs/*, src/one_dragon/launcher/*, src/sr_od/win_exe/*	新增 RuntimeLauncher 构建链路、模块清单、运行时 hook，并为代码同步增加进度与模块清理处理。
OCR 与 ONNX 执行 src/onnxocr/*, src/one_dragon/base/matcher/ocr/*, src/one_dragon/utils/gpu_executor.py, src/one_dragon/yolo/*	支持 PPOCRv6，统一 ONNX 会话创建，并为 DirectML 增加串行执行封装。
屏幕加载与匹配 src/one_dragon/base/screen/*	支持插件屏幕、应用作用域、额外 screen 持久化和结构化匹配结果。

通知与 Qt 界面

Layer / File(s)	Summary
通知配置与发送 src/one_dragon/base/config/notify_config.py, src/one_dragon/base/operation/operation_notify.py	通知配置改为生命周期与节点细节双模式，并更新迁移、发送和消息池逻辑。
通知设置与上下文通知 src/one_dragon_qt/view/setting/*, src/one_dragon_qt/widgets/app_setting/*, src/one_dragon_qt/windows/*	新增应用通知设置界面、飞出面板和主线程通知展示。
Qt 滚动组件 src/one_dragon_qt/widgets/*, src/one_dragon_qt/view/*	新增 FastScrollArea，并接入多个页面和开发工具。

规范、配置与基础工具

Layer / File(s)	Summary
开发规范与构建配置 AGENTS.md, .claude/*, docs/develop/*, skills/*, pyproject.toml, .github/*, .devin/*	新增 AI 入口、harness、skills、后端设计文档、quickstart、Wiki 配置，并更新依赖、工具链和 CI。
基础配置与工具行为 src/one_dragon/base/config/*, src/one_dragon/utils/*, src/one_dragon/envs/*	调整 YAML 写入、日志、下载、路径、点击、OCR 配置、自动更新和运行环境同步行为。

Estimated code review effort: 5 (Critical) | ~120 minutes

Poem

兔子敲键盘，月光落满章，
后端搭好台，MCP 来登场；
通知分两层，OCR 添新光，
滚轮轻轻转，代码稳稳航。

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	标题准确概括了本次后端同步与工具集扩展，且点出了 7→11 tool 的核心变化。
Docstring Coverage	✅ Passed	Docstring coverage is 87.00% which is sufficient. The required threshold is 80.00%.
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.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/mcp-backend-sync2

---

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.}

[coderabbitai]

Actionable comments posted: 19

🧹 Nitpick comments (5)

.github/workflows/test-check.yml (1)

18-21: 🔒 Security & Privacy | 🔵 Trivial | ⚡ Quick win

通过管道执行未锁版本的远程安装脚本。

Invoke-WebRequest ... | Invoke-Expression 直接执行 astral.sh 提供的最新安装脚本，未锁定版本/哈希，若上游被篡改会直接在 CI 中执行任意代码。可考虑固定到具体版本的安装脚本 URL，或改用官方 astral-sh/setup-uv Action（内置版本锁定与缓存）。

🤖 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 @.github/workflows/test-check.yml around lines 18 - 21, The Install uv step
in the workflow is piping a remote install script directly into
Invoke-Expression, so replace that unsafe pattern with a pinned, verifiable
installation approach. Update the "Install uv" step to use a fixed-version
script URL or, preferably, the official astral-sh/setup-uv Action so the
workflow relies on version-locked installation and caching. Keep the change
scoped to the workflow job that runs this step.

.github/dev.md (1)

5-5: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Python 补丁版本与 CI 不一致。

此处写死 Python 3.11.9，但 .github/workflows/test-check.yml 中 CI 使用 --python=3.11.12。建议统一版本描述（或只标注 3.11.x/3.11，与 AGENTS.md 保持一致），避免开发者本地环境与 CI 环境的补丁版本产生分歧。

📝 建议修改

-- Python 3.11.9；包管理用 uv。
+- Python 3.11（与 CI 保持一致，具体补丁版本见 workflow）；包管理用 uv。

🤖 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 @.github/dev.md at line 5, The Python version note in the docs is pinned to
3.11.9 while CI uses 3.11.12, so align the version text in the dev guide with
the workflow and AGENTS.md. Update the wording in the document section that
mentions Python and uv to use a consistent 3.11.x/3.11 reference or the CI patch
version, so developers follow the same environment as the test-check setup.

docs/develop/harness/README.md (1)

38-38: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

文档描述的 MCP 工具数量/阶段可能与本 PR 的实际实现脱节。

本文件多处（如 Line 38 "4 个感知 / 操作 tool"，Line 65 B-1 状态，Line 66 B-2 "⏳ 规划"）描述当前只落地 4 个感知/操作类 MCP 工具、原子操作工具（B-2）仍待规划。但根据 PR 描述，同一 PR 已将 MCP 工具从 7 个扩展到 11 个，新增了 click_game、input_text、upsert_screen_area、delete_screen_area 等原子操作与屏幕区域管理能力，这些能力看起来正对应 B-2 阶段的内容。请确认此文档是否需要同步更新工具数量与路线图状态，避免刚引入就与代码现状不一致。Based on learnings, 修改代码后应同步更新对应的 docs/develop/ 文档。

Also applies to: 59-70

🤖 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 `@docs/develop/harness/README.md` at line 38, Update the harness README to
match the current MCP implementation: the “4 个感知 / 操作 tool” wording and the
B-1/B-2 roadmap in the sections around the MCP tool overview should be revised
to reflect that `SrBackendContext` now exposes 11 tools, including the new
atomic operation and screen-area management capabilities such as `click_game`,
`input_text`, `upsert_screen_area`, and `delete_screen_area`. Keep the
tool-stage descriptions aligned with the actual state of the backend and ensure
the route/map text in the README is synchronized with the symbols introduced in
the PR.

Source: Learnings

src/one_dragon/base/operation/operation_notify.py (1)

62-99: 🚀 Performance & Scalability | 🔵 Trivial | ⚡ Quick win

热路径中重复构造 notify_config，建议本地缓存引用。

operation.ctx.notify_config 是一个属性，每次访问都会重新构造 NotifyConfig（进而触发 YamlConfig 加载）。send_node_notify 单次调用中最多访问该属性 4 次（Line 244、249、345、352），send_application_notify 通过 _get_lifecycle_mode/_get_detail_mode（各自内部又访问两次）合计可达 4-6 次。由于 send_node_notify 会在每个节点结束时高频调用，重复构造可能带来不必要的 I/O/对象开销。

建议在函数入口处缓存一次 notify_config 引用后复用，例如：

⚡ 建议的优化方向（示意）

     app_id, app_name = _get_app_info(operation)
+    notify_config = operation.ctx.notify_config
     detail_mode = (
         NotifyDetailMode.ALL.value.value
         if app_id is None
-        else operation.ctx.notify_config.get_app_detail_mode(app_id)
+        else notify_config.get_app_detail_mode(app_id)
     )
     app_lifecycle_mode = (
         NotifyLifecycleMode.FINISH_ONLY.value.value
         if app_id is None
-        else operation.ctx.notify_config.get_app_lifecycle_mode(app_id)
+        else notify_config.get_app_lifecycle_mode(app_id)
     )

由于 src/one_dragon/ 属于从 ZZZ 上游整包同步的公共框架代码，本地补丁在下次同步时可能被覆盖，若确认此问题成立，建议优先在上游 ZZZ 项目修复后再同步回来。

Also applies to: 237-265, 340-352

🤖 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 `@src/one_dragon/base/operation/operation_notify.py` around lines 62 - 99,
send_application_notify and send_node_notify are repeatedly accessing
operation.ctx.notify_config, which can reconstruct NotifyConfig and trigger
extra YamlConfig loading on hot paths. Cache the notify_config once at the start
of these functions (and reuse it in _get_lifecycle_mode / _get_detail_mode or
inline their calls) so lifecycle/detail mode lookups use the same local
reference instead of re-fetching the property multiple times. Use the existing
symbols send_application_notify, send_node_notify, _get_lifecycle_mode, and
_get_detail_mode to keep the change localized and avoid repeated property
access.

Source: Learnings

pyproject.toml (1)

54-72: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

建议将 RUF002 加入忽略列表，与中文注释规范保持一致。

ignore 只包含 RUF001、RUF003，未包含 RUF002（docstring 中全角标点歧义）。由于路径指导要求注释与 docstring 必须使用中文，中文语境下全角逗号/括号非常普遍，会产生大量噪音警告（本次静态分析已在多个文件中命中），建议一并忽略。

♻️ 建议修改

-ignore = ["RUF001", "RUF003"]
+ignore = ["RUF001", "RUF002", "RUF003"]

As per path instructions, "注释与 docstring 必须使用中文，并保持现有项目风格。"

🤖 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 `@pyproject.toml` around lines 54 - 72, The Ruff lint configuration is missing
the `RUF002` rule in the ignore list, which will keep producing noisy warnings
for Chinese docstrings and comments. Update the `[tool.ruff.lint]` settings in
the `ignore` entry alongside `RUF001` and `RUF003` so `RUF002` is also ignored,
keeping the existing project style intact.

Source: Path instructions

🤖 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.

Inline comments:
In @.github/workflows/test-check.yml:
- Around line 13-16: The actions/checkout step currently relies on the default
credential persistence, which leaves git credentials available to later steps.
Update each checkout usage in this workflow, including the Checkout code step
and the other two checkout calls referenced in the job, to explicitly disable
credential persistence with persist-credentials set to false. Use the
actions/checkout configuration blocks to locate and apply the change
consistently across all checkout steps.
- Around line 9-11: Explicitly add a permissions block to the test-check job so
it follows least-privilege instead of inheriting repository defaults. Update the
job definition under test-check in the workflow to declare only the minimum
required scope, using contents: read unless a specific step in this job needs
more. This change should be made in the job configuration for test-check so the
workflow’s permissions are clear and constrained.

In `@deploy/build_full.bat`:
- Around line 17-32: Several `copy` steps in `build_full.bat` can prompt for
overwrite confirmation on reruns, which can hang unattended builds. Update the
`copy` commands used for `OneDragon-Installer.exe`, `OneDragon-Launcher.exe`,
`OneDragon-RuntimeLauncher.exe`, `project.yml`, and `pyproject.toml` to use
non-interactive overwrite behavior, or clear `TARGET_DIR` before the packaging
steps. Keep the existing `xcopy` calls for directories, and make the change in
the same build flow around the `TARGET_DIR`/`DIST_DIR` copy sequence.

In `@deploy/module_manifest.py`:
- Line 66: The manifest still contains legacy sr.* imports that will fail under
the current package layout; update the import entries in the manifest generation
logic to use sr_od.* instead of sr.app.*, sr.context.*, sr.operation.*, and
sr.treasures_lightward.*. Keep valid imports like from unittest import result
unchanged, and adjust the affected manifest-building code in module_manifest.py
so all referenced modules match the current package structure.

In `@docs/develop/one_dragon/common-package-sync.md`:
- Around line 39-44: The validation section currently limits linting to only
sr_od files, which can miss syntax or import issues introduced in the synced
public packages. Update the verification steps in the common-package sync guide
so the post-sync checks also cover the synchronized one_dragon, one_dragon_qt,
and onnxocr content with a minimal validation pass, while still keeping
sr_od-specific checks separate where appropriate.

In `@docs/develop/one_dragon/runtime_launcher.md`:
- Around line 93-95: The wording in the runtime launcher docs is too broad
because it says SR has “no CI,” which is no longer accurate after the new test
CI was added. Update the related bullet in the documentation to use the correct
scope, and make sure the description around generate_module_manifest.py and
build_full.bat clearly says there is no automated packaging/release CI rather
than no CI at all.

In `@docs/develop/setup/ai_coding.md`:
- Around line 144-146: The fenced block in the documentation snippet is missing
a language identifier, causing markdownlint MD040 to fire. Update the fenced
block around the Co-Authored-By footer in the setup guide by adding an
appropriate language tag such as text or gitcommit, and keep the content
unchanged so the markdown remains valid and lint-friendly.

In `@docs/develop/setup/claude-code/commit-trailer.md`:
- Around line 107-111: The early exit in the commit trailer update flow is too
broad: in the trailer handling logic, do not return just because a Claude Code
co-author trailer already exists, since that prevents --amend from refreshing
the model-specific trailer. Update the behavior in the trailer-writing step to
detect and replace or refresh the existing model trailer while preserving the
Claude Code trailer, and keep the logic centered around the trailer
insertion/rewriting path that uses git interpret-trailers.

In `@docs/develop/sr_od/backend/architecture.md`:
- Around line 17-30: Update the architecture doc’s tool/method inventory to
match the actual backend symbols. In the `mcp/app.py` section, replace the
outdated “7 个 `@mcp.tool`” count with the current 11 tools and keep the list
aligned with `create_mcp_server`; in `backend_context.py`, extend the method
list beyond `close_game` to include the existing `click_game`, `input_text`,
`upsert_screen_area`, and `delete_screen_area`. Make sure the counts and names
stay consistent with the current implementation.

In `@docs/develop/sr_od/backend/design-principles.md`:
- Around line 20-25: Update the “读源码 / Read / Grep / Glob” example in
design-principles.md because it still references the old OpenAndEnterGame entry
name; replace it with the current finer-grained tool name(s) used in this
codebase or rephrase the example as a generic “进游戏链路” description so readers are
not directed to a stale API. Use the existing table entry and surrounding
guidance to keep the wording aligned with the current tool surface.

In `@docs/develop/sr_od/backend/remote-ssh.md`:
- Around line 22-24: The daemon port numbers are inconsistent between the
startup command and the MCP client registration example, so unify them to a
single port throughout this section. Update the start_daemon.ps1 default port
reference, the example MCP URL, and any related wording so they all match the
same daemon port, keeping the remote-ssh.md guidance consistent for readers.
- Around line 13-18: Update the topology diagram fenced block in the remote SSH
markdown doc to include a language tag, using the existing diagram section so it
is marked as text instead of a bare fence. Keep the content unchanged and adjust
the opening fence in the diagram block to use text, which will satisfy
markdownlint MD040.

In `@skills/sr-od-dev-deciding-a-fix/SKILL.md`:
- Around line 32-40: In the Quick Reference table within SKILL.md, add the
missing blank line separation before and after the markdown table so it complies
with markdownlint MD058. Keep the table content unchanged and adjust the
surrounding spacing around the Quick Reference section to remove the lint
warning.

In `@skills/sr-od-dev-pr-finishing/SKILL.md`:
- Around line 21-24: The fenced shell command blocks in SKILL.md are missing the
bash language tag, causing markdownlint MD040. Update both command blocks around
the gh api graphql examples (including the later block referenced by the
comment) to use bash-labeled fences so they render and lint correctly.

In `@src/one_dragon_qt/widgets/horizontal_setting_card_group.py`:
- Around line 32-36: The add_card method in HorizontalSettingCardGroup is making
each card participate in horizontal stretch by using a nonzero stretch factor,
which causes cards to expand instead of keeping their natural width. Update
add_card so the card is added to h_layout with a stretch of 0 while keeping the
existing alignment, and leave the placeholder/spacer logic to absorb extra
space.

In `@src/one_dragon/base/screen/screen_info.py`:
- Around line 96-110: `upsert_area` in `ScreenInfo` is not propagating the
screen-level `pc_alt`, so inserted or replaced `ScreenArea` entries can drift
from the `ScreenInfo.__init__` YAML normalization. Update `upsert_area` to
ensure any incoming `ScreenArea` is aligned with `self.pc_alt` before storing
it, both in the replace path and the append path, so downstream logic that reads
`area.pc_alt` always sees the current screen configuration.

In `@src/onnxocr/logger.py`:
- Around line 23-41: _LoggerShim in logger.py is dropping logging kwargs such as
exc_info because info/debug/warning/error only format the message and never
forward the remaining keyword arguments to od_log. Update the upstream
implementation of _LoggerShim so these methods preserve and pass through logging
kwargs while still supporting message formatting, then sync the fix back into
this shared package rather than patching it locally in the SR repo.

In `@src/sr_od/backend/backend_context.py`:
- Around line 375-389: The analyze() OCR/matching path is not serialized and can
race with background operations, causing DirectML session contention and cache
corruption. Update backend_context.analyze() so the calls to
OcrService.get_ocr_result_list() and find_screen_matches() run through the same
GPU execution guard used elsewhere, or add a shared lock inside
OcrService/OnnxOcrMatcher to protect _cache, _cache_list, and self._model.ocr()
from concurrent access, keeping the current write_back behavior unchanged.

In `@tools/mcp/daemon/sr_od_daemon.py`:
- Around line 90-121: `start_sr_od_mcp_server` has a TOCTOU race between
`find_sr_od_mcp_server_process()`, `is_port_in_use(port)`, and the
`subprocess.Popen` launch, so concurrent calls can both pass the checks and
start duplicate servers. Add a mutual-exclusion guard around the entire
check-and-start flow (for example a process-wide lock or other startup
serialization in `sr_od_daemon.py`) so only one caller can evaluate
`existing_proc`/port state and invoke `Popen` at a time. Keep the existing
`process.poll()` and logging behavior, but ensure the lock covers the full
critical section from the initial checks through process creation.

---

Nitpick comments:
In @.github/dev.md:
- Line 5: The Python version note in the docs is pinned to 3.11.9 while CI uses
3.11.12, so align the version text in the dev guide with the workflow and
AGENTS.md. Update the wording in the document section that mentions Python and
uv to use a consistent 3.11.x/3.11 reference or the CI patch version, so
developers follow the same environment as the test-check setup.

In @.github/workflows/test-check.yml:
- Around line 18-21: The Install uv step in the workflow is piping a remote
install script directly into Invoke-Expression, so replace that unsafe pattern
with a pinned, verifiable installation approach. Update the "Install uv" step to
use a fixed-version script URL or, preferably, the official astral-sh/setup-uv
Action so the workflow relies on version-locked installation and caching. Keep
the change scoped to the workflow job that runs this step.

In `@docs/develop/harness/README.md`:
- Line 38: Update the harness README to match the current MCP implementation:
the “4 个感知 / 操作 tool” wording and the B-1/B-2 roadmap in the sections around the
MCP tool overview should be revised to reflect that `SrBackendContext` now
exposes 11 tools, including the new atomic operation and screen-area management
capabilities such as `click_game`, `input_text`, `upsert_screen_area`, and
`delete_screen_area`. Keep the tool-stage descriptions aligned with the actual
state of the backend and ensure the route/map text in the README is synchronized
with the symbols introduced in the PR.

In `@pyproject.toml`:
- Around line 54-72: The Ruff lint configuration is missing the `RUF002` rule in
the ignore list, which will keep producing noisy warnings for Chinese docstrings
and comments. Update the `[tool.ruff.lint]` settings in the `ignore` entry
alongside `RUF001` and `RUF003` so `RUF002` is also ignored, keeping the
existing project style intact.

In `@src/one_dragon/base/operation/operation_notify.py`:
- Around line 62-99: send_application_notify and send_node_notify are repeatedly
accessing operation.ctx.notify_config, which can reconstruct NotifyConfig and
trigger extra YamlConfig loading on hot paths. Cache the notify_config once at
the start of these functions (and reuse it in _get_lifecycle_mode /
_get_detail_mode or inline their calls) so lifecycle/detail mode lookups use the
same local reference instead of re-fetching the property multiple times. Use the
existing symbols send_application_notify, send_node_notify, _get_lifecycle_mode,
and _get_detail_mode to keep the change localized and avoid repeated property
access.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 705a9881-22af-4869-8a96-7022dee5409b

📥 Commits

Reviewing files that changed from the base of the PR and between f24784b and a60fcff.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (143)

• .claude/CLAUDE.md
• .github/dev.md
• .github/workflows/test-check.yml
• .gitignore
• AGENTS.md
• config/project.yml
• deploy/OneDragon-RuntimeLauncher.spec
• deploy/build_full.bat
• deploy/generate_module_manifest.py
• deploy/hook_path_inject.py
• deploy/module_manifest.py
• docs/develop/harness/README.md
• docs/develop/harness/ai_tool_rules.md
• docs/develop/harness/context_layering.md
• docs/develop/harness/entry_files.md
• docs/develop/harness/settings_scope.md
• docs/develop/one_dragon/common-package-sync.md
• docs/develop/one_dragon/runtime_launcher.md
• docs/develop/setup/ai_coding.md
• docs/develop/setup/claude-code/commit-trailer.md
• docs/develop/setup/quickstart.md
• docs/develop/sr_od/backend/README.md
• docs/develop/sr_od/backend/architecture.md
• docs/develop/sr_od/backend/design-principles.md
• docs/develop/sr_od/backend/entry.md
• docs/develop/sr_od/backend/http.md
• docs/develop/sr_od/backend/mcp.md
• docs/develop/sr_od/backend/remote-ssh.md
• pyproject.toml
• skills/sr-od-dev-deciding-a-fix/SKILL.md
• skills/sr-od-dev-deciding-a-fix/design.md
• skills/sr-od-dev-pr-finishing/SKILL.md
• skills/sr-od-dev-pr-finishing/design.md
• skills/sr-od-dev-skill-guide/SKILL.md
• skills/sr-od-dev-skill-guide/design.md
• src/one_dragon/base/conditional_operation/state_handler.py
• src/one_dragon/base/config/basic_model_config.py
• src/one_dragon/base/config/game_account_config.py
• src/one_dragon/base/config/notify_config.py
• src/one_dragon/base/config/yaml_operator.py
• src/one_dragon/base/controller/pc_controller_base.py
• src/one_dragon/base/matcher/ocr/onnx_ocr_matcher.py
• src/one_dragon/base/operation/application/application_factory_manager.py
• src/one_dragon/base/operation/application_base.py
• src/one_dragon/base/operation/context_event_bus.py
• src/one_dragon/base/operation/context_notify_event.py
• src/one_dragon/base/operation/notify_pool.py
• src/one_dragon/base/operation/one_dragon_app.py
• src/one_dragon/base/operation/one_dragon_context.py
• src/one_dragon/base/operation/operation_notify.py
• src/one_dragon/base/screen/screen_info.py
• src/one_dragon/base/screen/screen_loader.py
• src/one_dragon/base/screen/screen_match.py
• src/one_dragon/base/screen/screen_utils.py
• src/one_dragon/base/screen/template_info.py
• src/one_dragon/base/screen/template_loader.py
• src/one_dragon/devtools/python_launcher.py
• src/one_dragon/envs/env_config.py
• src/one_dragon/envs/git_service.py
• src/one_dragon/launcher/runtime_launcher.py
• src/one_dragon/utils/app_utils.py
• src/one_dragon/utils/cv2_utils.py
• src/one_dragon/utils/gpu_executor.py
• src/one_dragon/utils/http_utils.py
• src/one_dragon/utils/log_utils.py
• src/one_dragon/yolo/onnx_model_loader.py
• src/one_dragon/yolo/yolov8_onnx_cls.py
• src/one_dragon/yolo/yolov8_onnx_det.py
• src/one_dragon_qt/demo/draggable_list_demo.py
• src/one_dragon_qt/services/app_setting/app_setting_manager.py
• src/one_dragon_qt/view/app_run_interface.py
• src/one_dragon_qt/view/code_interface.py
• src/one_dragon_qt/view/devtools/devtools_image_analysis_interface.py
• src/one_dragon_qt/view/devtools/devtools_screen_manage_interface.py
• src/one_dragon_qt/view/devtools/devtools_template_helper_interface.py
• src/one_dragon_qt/view/one_dragon/one_dragon_run_interface.py
• src/one_dragon_qt/view/setting/app_notify_setting_interface.py
• src/one_dragon_qt/view/setting/resource_download_interface.py
• src/one_dragon_qt/view/setting/setting_env_interface.py
• src/one_dragon_qt/view/setting/setting_instance_interface.py
• src/one_dragon_qt/view/setting/setting_push_interface.py
• src/one_dragon_qt/widgets/app_run_list.py
• src/one_dragon_qt/widgets/app_setting/app_notify_setting_flyout.py
• src/one_dragon_qt/widgets/color_channel_dialog.py
• src/one_dragon_qt/widgets/fast_scroll_area.py
• src/one_dragon_qt/widgets/horizontal_setting_card_group.py
• src/one_dragon_qt/widgets/install_card/code_install_card.py
• src/one_dragon_qt/widgets/notify_dialog.py
• src/one_dragon_qt/widgets/scroll_credits.py
• src/one_dragon_qt/widgets/setting_card/app_run_card.py
• src/one_dragon_qt/widgets/setting_card/password_switch_setting_card.py
• src/one_dragon_qt/widgets/vertical_scroll_interface.py
• src/one_dragon_qt/windows/main_app_window_base.py
• src/onnxocr/inference_engine.py
• src/onnxocr/logger.py
• src/onnxocr/onnx_paddleocr.py
• src/onnxocr/operators.py
• src/onnxocr/predict_base.py
• src/onnxocr/predict_cls.py
• src/onnxocr/predict_det.py
• src/onnxocr/predict_rec.py
• src/onnxocr/predict_system.py
• src/onnxocr/readme.md
• src/onnxocr/utils.py
• src/sr_od/app/sr_application_launcher.py
• src/sr_od/application/div_uni/__init__.py
• src/sr_od/application/div_uni/operations/__init__.py
• src/sr_od/application/div_uni/operations/choose_oe_file.py
• src/sr_od/application/div_uni/operations/choose_oe_support.py
• src/sr_od/application/div_uni/operations/ornamenet_extraction.py
• src/sr_od/application/trailblaze_power/trailblaze_power_app.py
• src/sr_od/application/treasures_lightward/__init__.py
• src/sr_od/application/treasures_lightward/op/__init__.py
• src/sr_od/application/treasures_lightward/op/challenge_mission.py
• src/sr_od/application/treasures_lightward/op/check_max_unlock_mission.py
• src/sr_od/application/treasures_lightward/op/check_mission_star.py
• src/sr_od/application/treasures_lightward/op/check_star.py
• src/sr_od/application/treasures_lightward/op/choose_character.py
• src/sr_od/application/treasures_lightward/op/forgotten_hall/__init__.py
• src/sr_od/application/treasures_lightward/op/forgotten_hall/choose_mission.py
• src/sr_od/application/treasures_lightward/op/forgotten_hall/choose_team_in_fh.py
• src/sr_od/application/treasures_lightward/op/forgotten_hall/get_reward_in_fh.py
• src/sr_od/application/treasures_lightward/op/tl_battle.py
• src/sr_od/application/treasures_lightward/op/tl_wait.py
• src/sr_od/application/treasures_lightward/treasures_lightward_app.py
• src/sr_od/application/treasures_lightward/treasures_lightward_config.py
• src/sr_od/application/treasures_lightward/treasures_lightward_const.py
• src/sr_od/application/treasures_lightward/treasures_lightward_record.py
• src/sr_od/application/treasures_lightward/treasures_lightward_team_module.py
• src/sr_od/backend/__init__.py
• src/sr_od/backend/backend_context.py
• src/sr_od/backend/entry/__init__.py
• src/sr_od/backend/entry/server.py
• src/sr_od/backend/http/__init__.py
• src/sr_od/backend/http/routes.py
• src/sr_od/backend/mcp/__init__.py
• src/sr_od/backend/mcp/app.py
• src/sr_od/backend/schemas.py
• src/sr_od/win_exe/__init__.py
• src/sr_od/win_exe/runtime_launcher.py
• tools/mcp/daemon/create_startup_shortcut.ps1
• tools/mcp/daemon/sr_od_daemon.py
• tools/mcp/daemon/start_daemon.ps1

💤 Files with no reviewable changes (3)

• src/one_dragon/base/conditional_operation/state_handler.py
• src/sr_od/app/sr_application_launcher.py
• src/one_dragon_qt/widgets/notify_dialog.py

[coderabbitai]

🧹 Nitpick comments (2)

.github/workflows/test-check.yml (2)

64-66: 🩺 Stability & Availability | 🔵 Trivial | ⚡ Quick win

下载步骤缺少重试机制，网络抖动可能导致 CI 间歇性失败。

Invoke-WebRequest 未配置重试参数，一次瞬时网络问题就会使整个 job 失败，需要重跑整个 CI。

🔁 建议增加重试参数

-          Invoke-WebRequest -Uri $url -OutFile $tmp
+          Invoke-WebRequest -Uri $url -OutFile $tmp -MaximumRetryCount 3 -RetryIntervalSec 5

🤖 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 @.github/workflows/test-check.yml around lines 64 - 66, The download step in
the workflow lacks retry handling, so a transient network failure can break the
job. Update the PowerShell step that uses Invoke-WebRequest to add retry logic
(for example, retry the download a few times with a short delay) around the $url
and $tmp download block so the CI can recover from intermittent failures without
rerunning the whole workflow.

---

64-68: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

模型版本号在 URL 与目标目录名中重复硬编码，建议提取为变量。

yolov8n-640-simuni-0601 同时出现在下载 URL（Line 64）和解压目标目录名（Line 68）。未来升级模型版本时若只改了其中一处，check_model_exists 可能因目录名不匹配而误判模型不存在，导致该预下载步骤形同虚设且难以排查。

♻️ 建议提取为变量

+          $modelVersion = "yolov8n-640-simuni-0601"
-          $url = "https://github.com/OneDragon-Anything/OneDragon-YOLO/releases/download/sr_model/yolov8n-640-simuni-0601.zip"
+          $url = "https://github.com/OneDragon-Anything/OneDragon-YOLO/releases/download/sr_model/$modelVersion.zip"
           $tmp = "$env:TEMP\yolo.zip"
           foreach ($cat in @("world_patrol", "sim_uni")) {
-            $dst = "assets\models\$cat\yolov8n-640-simuni-0601"
+            $dst = "assets\models\$cat\$modelVersion"
             New-Item -ItemType Directory -Force -Path $dst | Out-Null
             Expand-Archive -Path $tmp -DestinationPath $dst -Force
           }

🤖 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 @.github/workflows/test-check.yml around lines 64 - 68, The model version
string is duplicated in both the download URL and the destination directory
path, which can drift out of sync. Update the workflow block that builds the URL
and the $dst path to use a single shared variable for the model version in this
PowerShell step, so changes to the version only need to be made once and remain
consistent for check_model_exists.

🤖 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 @.github/workflows/test-check.yml:
- Around line 64-66: The download step in the workflow lacks retry handling, so
a transient network failure can break the job. Update the PowerShell step that
uses Invoke-WebRequest to add retry logic (for example, retry the download a few
times with a short delay) around the $url and $tmp download block so the CI can
recover from intermittent failures without rerunning the whole workflow.
- Around line 64-68: The model version string is duplicated in both the download
URL and the destination directory path, which can drift out of sync. Update the
workflow block that builds the URL and the $dst path to use a single shared
variable for the model version in this PowerShell step, so changes to the
version only need to be made once and remain consistent for check_model_exists.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c328489a-2cdf-408e-b35d-c6531daa73bd

📥 Commits

Reviewing files that changed from the base of the PR and between db851d6 and df5ace5.

📒 Files selected for processing (1)

• .github/workflows/test-check.yml

[DoctorReid]

@coderabbitai resume

[coderabbitai]

✅ Action performed

Reviews resumed.

[coderabbitai]

Actionable comments posted: 6

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

src/sr_od/backend/backend_context.py (1)

318-325: 🩺 Stability & Availability | 🟠 Major | 🏗️ Heavy lift

关闭 backend 前先停止并等待活动运行退出。

RunSlot.shutdown() 仅执行 shutdown(wait=False)，不会取消已运行的线程；随后 Line 837 会清理 SrContext 资源，而 Operation 仍可能继续访问控制器、OCR 或配置，且非 daemon 的线程池线程还可能阻止进程退出。请先发送 stop_running()，等待当前 future 结束，再执行 after_app_shutdown()。

Based on learnings, src/sr_od/backend 必须与上游 ZZZ 保持一致；请先在 ZZZ 修复后同步回 SR，避免 backend drift。

Also applies to: 829-837

🤖 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 `@src/sr_od/backend/backend_context.py` around lines 318 - 325, 先在上游 ZZZ 修复对应
backend 关闭流程，再将该修复同步到 SR，避免分叉；更新 RunSlot.shutdown() 及 backend 关闭路径，使其先调用
stop_running() 并等待活动 future 完成，再调用 after_app_shutdown() 清理 SrContext 资源，最后关闭线程池。

Source: Learnings

🧹 Nitpick comments (2)

src/sr_od/backend/mcp/service_app.py (1)

155-156: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

为 op_factory 补上类型注解

def op_factory(ctx) 仍然缺少参数和返回值标注，和项目的强制类型注解要求不一致。这里直接标成 ctx: SrContext、返回 Operation，并去掉 # noqa: ANN202；SrContext 和 Operation 可在 TYPE_CHECKING 下分别从 sr_od.context.sr_context、one_dragon.base.operation.operation 导入。

🤖 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 `@src/sr_od/backend/mcp/service_app.py` around lines 155 - 156, 为 op_factory
补充完整类型注解，将 ctx 标注为 SrContext、返回值标注为 Operation，并移除 # noqa: ANN202；在 TYPE_CHECKING
块中分别导入 sr_od.context.sr_context.SrContext 和
one_dragon.base.operation.operation.Operation。

Source: Coding guidelines

src/sr_od/backend/http/service_routes.py (1)

175-176: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

补齐新函数和 Qt 类成员的类型注解。

• src/sr_od/backend/http/service_routes.py#L175-L176: 为 op_factory 标注 SrContext 参数和 Operation 返回类型，类型专用导入放入 TYPE_CHECKING。
• src/sr_od/gui/interface/devtools/mcp_service_interface.py#L217-L222: 为 finished Signal 补充类型。
• src/sr_od/gui/interface/devtools/mcp_service_interface.py#L264-L270: 为两个 QTimer 成员补充类型。
• src/sr_od/gui/interface/devtools/mcp_service_interface.py#L278-L323: 为新增 card、button 和 message-box 成员补充类型。

As per coding guidelines, **/*.py: 所有函数签名和类成员变量都必须有类型注解。

🤖 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 `@src/sr_od/backend/http/service_routes.py` around lines 175 - 176, 为
src/sr_od/backend/http/service_routes.py:175-176 的 op_factory 补充 SrContext 参数和
Operation 返回类型，并将仅用于类型检查的导入放入 TYPE_CHECKING。为
src/sr_od/gui/interface/devtools/mcp_service_interface.py:217-222 的 finished
Signal、264-270 的两个 QTimer 成员，以及 278-323 新增的 card、button 和 message-box
成员补充准确类型注解，确保所有函数签名和类成员变量符合类型注解要求。

Source: Coding guidelines

🤖 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.

Inline comments:
In `@src/sr_od/backend/backend_context.py`:
- Around line 741-768: 调整 run_standalone_app 与 _start 的默认应用解析时机：显式传入的 app_id
继续立即使用，但未传入时不要在刷新前读取 active_app_id。将默认独立应用的解析移入 refresh_config
执行完成后的槽线程流程，确保使用刷新后的 _ctx.standalone_app_config.active_app_id；无可用应用时仍抛出
BackendNotReadyError。
- Around line 350-355: Update the screenshot-writing flow around cv2.imwrite in
the backend context to encode the BGR image with cv2.imencode and write the
encoded ndarray using tofile, preserving the existing screenshot path and
raising an explicit RuntimeError when encoding or writing fails.

In `@src/sr_od/backend/operation_registry.py`:
- Around line 239-272: 在 validate_args() 中增加未知参数校验：先根据 cls.__init__ 的参数定义排除
self、ctx 及可变参数后，拒绝 args 中未声明的键并返回明确的参数错误。保留现有必填参数、类型和 JSON 可序列化校验逻辑，确保 cls(ctx,
**args) 执行前即可发现拼写错误或额外参数。
- Around line 196-236: 更新 resolve_op_class，使 op_id 只能匹配扫描阶段基于 _SCAN_ROOTS 生成的可运行
Operation 白名单；在 import_module 前拒绝不在白名单中的模块或类，并复用扫描阶段对 Application、抽象类及 *Base
的过滤结果。保留现有格式、定义模块和 Operation 子类校验，避免通过 HTTP/MCP 解析任意未公开内部类。
- Around line 98-120: Update _annotation_json_serializable’s Union handling to
ignore NoneType branches before evaluating serializability, and require every
remaining branch to be JSON-serializable so CustomType | None is rejected while
valid scalar unions remain accepted.

In `@src/sr_od/gui/interface/devtools/mcp_service_interface.py`:
- Around line 82-91: 更新 _find_server_process() 以接收当前端口，严格匹配完整的 “-m
sr_od.backend.entry.server --port <端口>” 参数，并仅返回 cwd 与 _project_root() 一致的进程；同时将
_stop_server() 改为接收 port，并在所有调用处传入当前端口，确保停止操作只针对当前项目和端口的 server。

---

Outside diff comments:
In `@src/sr_od/backend/backend_context.py`:
- Around line 318-325: 先在上游 ZZZ 修复对应 backend 关闭流程，再将该修复同步到 SR，避免分叉；更新
RunSlot.shutdown() 及 backend 关闭路径，使其先调用 stop_running() 并等待活动 future 完成，再调用
after_app_shutdown() 清理 SrContext 资源，最后关闭线程池。

---

Nitpick comments:
In `@src/sr_od/backend/http/service_routes.py`:
- Around line 175-176: 为 src/sr_od/backend/http/service_routes.py:175-176 的
op_factory 补充 SrContext 参数和 Operation 返回类型，并将仅用于类型检查的导入放入 TYPE_CHECKING。为
src/sr_od/gui/interface/devtools/mcp_service_interface.py:217-222 的 finished
Signal、264-270 的两个 QTimer 成员，以及 278-323 新增的 card、button 和 message-box
成员补充准确类型注解，确保所有函数签名和类成员变量符合类型注解要求。

In `@src/sr_od/backend/mcp/service_app.py`:
- Around line 155-156: 为 op_factory 补充完整类型注解，将 ctx 标注为 SrContext、返回值标注为
Operation，并移除 # noqa: ANN202；在 TYPE_CHECKING 块中分别导入
sr_od.context.sr_context.SrContext 和
one_dragon.base.operation.operation.Operation。

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5e3a428e-f0d3-425d-8df6-33644f2adc79

📥 Commits

Reviewing files that changed from the base of the PR and between db851d6 and e492782.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (31)

• .github/workflows/test-check.yml
• deploy/module_manifest.py
• docs/develop/sr_od/backend/README.md
• docs/develop/sr_od/backend/architecture.md
• docs/develop/sr_od/backend/entry.md
• docs/develop/sr_od/backend/http.md
• docs/develop/sr_od/backend/mcp.md
• pyproject.toml
• src/one_dragon/base/operation/application/application_factory.py
• src/one_dragon/base/operation/application/application_run_context.py
• src/one_dragon/base/push/push_service.py
• src/one_dragon/devtools/python_launcher.py
• src/one_dragon/envs/python_service.py
• src/one_dragon/utils/cmd_utils.py
• src/one_dragon/utils/cv2_utils.py
• src/one_dragon/utils/os_utils.py
• src/one_dragon_qt/view/setting/setting_custom_interface.py
• src/one_dragon_qt/view/setting/setting_env_interface.py
• src/one_dragon_qt/view/setting/setting_push_interface.py
• src/onnxocr/predict_det.py
• src/sr_od/backend/backend_context.py
• src/sr_od/backend/entry/server.py
• src/sr_od/backend/http/routes.py
• src/sr_od/backend/http/service_routes.py
• src/sr_od/backend/mcp/app.py
• src/sr_od/backend/mcp/prompts.py
• src/sr_od/backend/mcp/service_app.py
• src/sr_od/backend/operation_registry.py
• src/sr_od/backend/schemas.py
• src/sr_od/gui/interface/devtools/mcp_service_interface.py
• src/sr_od/gui/interface/devtools/sr_devtools_interface.py

💤 Files with no reviewable changes (1)

• src/one_dragon_qt/view/setting/setting_push_interface.py

✅ Files skipped from review due to trivial changes (4)

• deploy/module_manifest.py
• docs/develop/sr_od/backend/mcp.md
• docs/develop/sr_od/backend/http.md
• docs/develop/sr_od/backend/README.md

🚧 Files skipped from review as they are similar to previous changes (3)

• pyproject.toml
• src/onnxocr/predict_det.py
• .github/workflows/test-check.yml

[coderabbitai]

✅ Action performed

Reviews resumed.

[coderabbitai]

Actionable comments posted: 1

♻️ Duplicate comments (1)

src/sr_od/backend/backend_context.py (1)

797-804: 🎯 Functional Correctness | 🟠 Major | 🏗️ Heavy lift

在刷新实例配置后再解析默认独立应用。

从当前缓存读取 active_app_id 时，真正的 _refresh_runtime_config() 尚未在槽线程中执行。如果 GUI 刚刚切换了实例或独立应用，此时获取的 app_id 仍是旧值，导致最终运行错误的应用。

建议将默认独立应用的解析移入 _refresh_runtime_config 执行完成后的槽线程流程中，或者让单跑道 _start 支持延迟解析，以确保始终读取到刷新后的最新配置。

🤖 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 `@src/sr_od/backend/backend_context.py` around lines 797 - 804, Update
run_standalone_app so the default standalone application ID is resolved only
after _refresh_runtime_config completes in the slot-thread flow, rather than
reading _ctx.standalone_app_config.active_app_id immediately. Preserve explicit
app_id behavior, and ensure missing refreshed IDs still raise
BackendNotReadyError before invoking _start_app.

🤖 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.

Inline comments:
In @.devin/wiki.json:
- Around line 12-271: 全面校正 `.devin/wiki.json` 中残留的 ZZZ 术语与引用，确保 Wiki 只描述星穹铁道项目。将
`ZzzBackendContext`、`ZContext`、`zzz_context.py`、`zzz_pc_controller.py` 及相关
`docs/develop/zzz` 引用替换为仓库实际使用的 SR
对应符号和路径，并同步修正“零号空洞”等玩法及其业务目录；涉及内置应用、后端、上下文、控制器和开发文档条目时，应以当前源码与真实文档为准，分别映射到差分宇宙、模拟宇宙、忘却之庭、每日实训、委托等实际功能，避免保留或臆造
ZZZ 内容。

---

Duplicate comments:
In `@src/sr_od/backend/backend_context.py`:
- Around line 797-804: Update run_standalone_app so the default standalone
application ID is resolved only after _refresh_runtime_config completes in the
slot-thread flow, rather than reading _ctx.standalone_app_config.active_app_id
immediately. Preserve explicit app_id behavior, and ensure missing refreshed IDs
still raise BackendNotReadyError before invoking _start_app.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 04539832-d603-4f34-92cf-957107d4a5bf

📥 Commits

Reviewing files that changed from the base of the PR and between e492782 and 191e76f.

📒 Files selected for processing (13)

• .devin/wiki.json
• docs/develop/setup/chrome-devtools-mcp.md
• docs/develop/sr_od/backend/README.md
• docs/develop/sr_od/backend/design-principles.md
• docs/develop/sr_od/backend/mcp-implementation.md
• docs/develop/sr_od/backend/mcp.md
• src/one_dragon/devtools/python_launcher.py
• src/one_dragon/envs/python_service.py
• src/one_dragon_qt/view/setting/setting_instance_interface.py
• src/sr_od/backend/backend_context.py
• src/sr_od/backend/mcp/app.py
• src/sr_od/backend/mcp/prompts.py
• src/sr_od/backend/mcp/service_app.py

🚧 Files skipped from review as they are similar to previous changes (3)

• docs/develop/sr_od/backend/mcp.md
• src/sr_od/backend/mcp/service_app.py
• docs/develop/sr_od/backend/README.md