feat: 自动更新

platform_web/README.md

@@ -89,16 +89,16 @@ Server list and server detail surfaces expose runtime actions through platform A
 
 These screens show safe availability reasons, run online/offline status, job/build/dependency progress, artifact IDs, checksums, key generations, fingerprints, and redacted `secret://runtime-keys/.../current` refs. They must not render raw run/client-manager keys, FTP passwords, database DSNs, RCON passwords, host paths, direct run sockets, backend storage URLs, or large inline log bodies.
 
-Browser walkthrough baseline:
+Manual UI smoke checklist:
 
 1. Start `npm run dev`.
 2. Open the local Vite URL.
 3. Verify 首页、服务器管理、插件市场、用户管理、AI 提供商管理 render without visible overlap on desktop and mobile widths.
-4. In 服务器管理, verify the server card action menu contains runtime actions without turning the whole card into an accidental click target.
+4. In 服务器管理, verify the server card action menu contains runtime actions as a compact anchored dropdown/popover. It must not become a tall vertical button tower, reflow the card, cover server metrics/progress bars/status badges, or turn the whole card into an accidental click target.
 5. In a server detail route, verify the overview renders the 运行分发 section, action availability reasons, dependency/log controls, and safe redacted refs only.
 6. Switch black mecha and magical-girl themes when UI styling changed; runtime controls must keep the shared translucent console surfaces and avoid nested double frames.
 
-Automated browser acceptance uses the repository local debug stack:
+Automated browser acceptance remains available for deeper local debug verification:
 
 ```bash
 LOCAL_DEBUG_PLATFORM_PORT=18189 LOCAL_DEBUG_WEB_PORT=5183 LOCAL_DEBUG_ROOT=/private/tmp/browser-local-debug-acceptance ../scripts/browser-acceptance.sh