feat: integrate pi rust lab runtime
This commit is contained in:
Agent Board
@@ -0,0 +1,45 @@
|
||||
# 5-44 Block menu 打开后泄露 Material Symbols ligature 文本
|
||||
|
||||
> 创建时间：2026-07-08
|
||||
> 状态：`done`
|
||||
> Owner：`05-editor-mainline`
|
||||
|
||||
## 现象
|
||||
|
||||
在 mnote 主编辑器中 hover 到块手柄并点开块菜单后，菜单项图标位置直接显示 `auto_awesome`、`autorenew`、`chevron_right`、`content_copy`、`format_align_center` 等英文 ligature 文本，导致菜单宽度和排版明显错乱。
|
||||
|
||||
复现路径：
|
||||
|
||||
1. 打开本地主编辑器文档。
|
||||
2. hover 到正文块左侧手柄。
|
||||
3. 点击手柄打开块菜单。
|
||||
4. 观察块菜单内图标列。
|
||||
|
||||
失败证据：
|
||||
|
||||
- `tmp/block-handle-menu-display-diagnostic/after-click.png`
|
||||
- `tmp/block-handle-menu-display-diagnostic/metrics.json`
|
||||
|
||||
## 根因
|
||||
|
||||
主编辑器 island 的 icon helper 和部分动态菜单项只输出了 `class="material-symbols-outlined"` 加 ligature 文本，没有输出 `data-icon`。当前 mnote 主壳使用本地 SVG mask 作为 Material Symbols fallback，fallback CSS 只对带 `data-icon` 的节点生效；缺少 `data-icon` 时，浏览器没有 Material Symbols 字体可用，就直接把 ligature 文本当普通文本显示出来。
|
||||
|
||||
## 修复
|
||||
|
||||
- `material_icon()` 改为输出 `data-icon=<name>`，并移除可见 ligature 文本。
|
||||
- block transform 子菜单和 slash 菜单动态图标同步输出 `data-icon`，不再把 ligature 作为可见文本。
|
||||
- 补齐主壳 CSS 中块菜单常用 icon 的本地 fallback，确保无外部 Material Symbols 字体时仍能显示为稳定图标。
|
||||
- 重新执行 wasm release build 与 `wasm-bindgen`，更新 `rust/spikes/leptos-tiptap-spike/generated/island/*` 产物。
|
||||
|
||||
## 验收
|
||||
|
||||
- `cargo check --manifest-path rust/spikes/leptos-tiptap-spike/Cargo.toml` 通过，只有既有 warning。
|
||||
- `cargo build --manifest-path rust/spikes/leptos-tiptap-spike/Cargo.toml --target wasm32-unknown-unknown --release` 通过，只有既有 warning。
|
||||
- `wasm-bindgen rust/spikes/leptos-tiptap-spike/target/wasm32-unknown-unknown/release/mnote_leptos_tiptap_spike.wasm --target web --out-dir rust/spikes/leptos-tiptap-spike/generated/island --out-name mnote-leptos-tiptap-spike-island` 通过。
|
||||
- `node scripts/task489-block-menu-delete-undo-smoke.js` 通过。
|
||||
- 浏览器诊断确认块菜单 `leaked=false`，12 个菜单项正常渲染，图标节点宽高恢复为 `20x20`。
|
||||
- 修复后截图：`tmp/block-handle-menu-display-diagnostic/after-click-fixed.png`。
|
||||
|
||||
## 未覆盖
|
||||
|
||||
- 本轮只修复手柄菜单与 editor runtime 图标文本泄露；没有扩大到全站所有未带 `data-icon` 的历史图标节点。
|
||||
@@ -0,0 +1,109 @@
|
||||
# MNote 浏览器 QA 实测发现 2026-07-08
|
||||
|
||||
- **状态**：`process`
|
||||
- **来源**：Agent Board Pi Taskflow 实测（MNote 浏览器 QA → Bug 文档 20260708-130503）
|
||||
- **复现环境**：
|
||||
- MNote Web：`http://127.0.0.1:3000`，Rust SSR + leptos-tiptap island
|
||||
- 后端：control-plane libSQL local
|
||||
- 浏览器：Playwright Chromium headless，viewport 1280×800
|
||||
- 登录：测试账号 `mnote.e2e@example.com`，authMode=controlPlaneSession
|
||||
- 工作区：`/mnt/Data1T/Mnote_data/users/mnote-e2e/workspaces/my-space`
|
||||
|
||||
---
|
||||
|
||||
## 1. 总体状态
|
||||
|
||||
| 检查项 | 结果 | 详情 |
|
||||
|--------|------|------|
|
||||
| API Gateway /health | ✅ PASS | 200 |
|
||||
| Auth 页面加载 | ✅ PASS | 518ms |
|
||||
| 测试账号快速登录 | ✅ PASS | 跳转到 `/` |
|
||||
| Workspace 壳渲染 | ✅ PASS | sidebar / topbar / shell 均可见 |
|
||||
| Page AI / OpenHub 页面 | ✅ PASS | 130ms 加载，AI 输入框可见 |
|
||||
| Console 错误 | ✅ PASS | 0 errors |
|
||||
| 业务网络错误 | ✅ PASS | 0 real errors（SSE abort 为预期导航行为） |
|
||||
|
||||
---
|
||||
|
||||
## 2. 发现的问题
|
||||
|
||||
### 2.1 `file-order.json` 页面排序索引为空
|
||||
|
||||
- **严重程度**：medium
|
||||
- **实际结果**：`/mnt/Data1T/Mnote_data/users/mnote-e2e/workspaces/my-space/.mnote/file-order.json` 内容为 `{"parents": {}, "version": 1}`，无任何页面条目。
|
||||
- **预期结果**：工作区中存在有效页面目录（`新页面054900`、`新页面145827`、`新页面233155`、`有机合成中的保护基` 等），每个目录下均有 `.md` 正文文件，file-order.json 应包含这些页面的排序条目。
|
||||
- **证据**：
|
||||
```bash
|
||||
$ cat .mnote/file-order.json
|
||||
{"parents": {}, "version": 1}
|
||||
|
||||
$ ls workspace/
|
||||
新页面054900/ 新页面145827/ 新页面233155/ 有机合成中的保护基/
|
||||
```
|
||||
- **影响范围**：页面树（Page Tree）排序可能不正确，新建页面可能无法正确出现在侧边栏页面列表中。
|
||||
- **建议修复方向**：检查页面创建/重命名/移动流程是否正确更新 `file-order.json`；检查 Pi lab 批量创建页面的流程是否绕过了正常的 metadata 写入路径。
|
||||
|
||||
### 2.2 `/api/tree/page-tree` 端点返回 404
|
||||
|
||||
- **严重程度**：low
|
||||
- **实际结果**：`GET /api/tree/page-tree` 返回 HTTP 404。
|
||||
- **预期结果**：应返回 200 或 401（需要认证），而非 404。
|
||||
- **证据**：
|
||||
```bash
|
||||
$ curl -s -w "\nHTTP: %{http_code}" http://127.0.0.1:3000/api/tree/page-tree
|
||||
HTTP: 404
|
||||
```
|
||||
- **影响范围**：直接调用此 API 的外部客户端或测试脚本会失败。前端使用 `GET /api/tree/view-state?treeKind=pagetree`（需要认证，已正常工作），当前不受影响。
|
||||
- **建议修复方向**：确认 `/api/tree/page-tree` 是否为已废弃路由；若是，应在路由注册时返回 410 Gone 或转发到 view-state；若不是，应修复路由注册。
|
||||
|
||||
### 2.3 侧边栏中无 `a[href*="/document/"]` 格式的文档链接
|
||||
|
||||
- **严重程度**：low（待确认是否为预期行为）
|
||||
- **实际结果**：Playwright selector `a[href*="/document/"]` 在侧边栏中找到 0 个元素。
|
||||
- **预期结果**：侧边栏页面树中的页面应可点击跳转到文档页。
|
||||
- **证据**：QA 脚本 `page.locator('a[href*="/document/"]').count()` 返回 0。
|
||||
- **影响范围**：如果页面确实使用不同 URL 模式（如 `/page/...` 或前端路由），则无影响；否则侧边栏页面无法点击跳转。
|
||||
- **建议修复方向**：确认当前侧边栏页面树使用的链接格式；如果是前端 SPA 路由（如 `data-page-id` + click handler），则更新测试 selector；如果是 bug，修复链接生成。
|
||||
|
||||
### 2.4 Dev 模式 hot-reload 轮询累积
|
||||
|
||||
- **严重程度**：low（仅 dev 模式）
|
||||
- **实际结果**：多个 `GET /api/dev/hot-reload` 请求处于 pending 状态，随时间累积。
|
||||
- **预期结果**：hot-reload 连接应复用或及时关闭，不应无限累积。
|
||||
- **证据**：网络追踪显示 20+ 个 pending 的 `GET /api/dev/hot-reload` 请求。
|
||||
- **影响范围**：仅影响开发模式下的浏览器性能和内存占用，不影响生产环境。
|
||||
- **建议修复方向**：检查 hot-reload EventSource/WebSocket 连接的生命周期管理，确保旧连接在页面导航或重连时正确关闭。
|
||||
|
||||
---
|
||||
|
||||
## 3. 已验证无问题的路径
|
||||
|
||||
- Auth 登录流程：正常
|
||||
- Workspace 壳渲染：正常
|
||||
- Page AI / OpenHub 页面：正常加载
|
||||
- API `/api/auth/session`：正常
|
||||
- API `/api/tree/view-state`（需认证）：正常
|
||||
- API `/api/tree/projections/file/children`（需认证）：正常
|
||||
- SSE `/api/local-folder/events`：正常建立连接
|
||||
- API `/api/page-ai/pi/status`：正常
|
||||
- API `/api/ai-settings/effective`：正常
|
||||
|
||||
---
|
||||
|
||||
## 4. 测试脚本
|
||||
|
||||
QA 脚本位于：
|
||||
- `/tmp/mnote-browser-qa-20260708.js`（基础检查）
|
||||
- `/tmp/mnote-browser-qa-20260708-detail.js`（详细检查）
|
||||
- `/tmp/mnote-browser-qa-comprehensive.js`（综合检查）
|
||||
- `/tmp/mnote-network-trace.js`（网络追踪）
|
||||
|
||||
结果文件：
|
||||
- `/tmp/mnote-browser-qa-20260708/result.json`
|
||||
- `/tmp/mnote-browser-qa-20260708/result-detail.json`
|
||||
- `/tmp/mnote-browser-qa-20260708/result-final.json`
|
||||
|
||||
截图：
|
||||
- `/tmp/mnote-browser-qa-20260708/01-main-page.png`（Auth 页）
|
||||
- `/tmp/mnote-browser-qa-20260708/02-after-login.png`（登录后 workspace）
|
||||
- `/tmp/mnote-browser-qa-20260708/05-post-login-workspace.png`（workspace 页）
|
||||
+222
@@ -0,0 +1,222 @@
|
||||
# Browser QA needs-more-info
|
||||
|
||||
- workflow_run_id: d7585a30-63cd-4201-a3c5-47e9e34b0773
|
||||
- status: needs-more-info
|
||||
- triage: NEEDS_MORE_QA
|
||||
|
||||
## QA Scope
|
||||
|
||||
MINIMAL_BROWSER_QA_RUNBOOK
|
||||
TARGET: 主编辑器段落块左侧手柄 hover/点击/菜单显示与图标布局
|
||||
URL: http://localhost:3000
|
||||
ACCOUNT: 测试账号快速登录 (mnote.e2e@example.com / MnoteE2E123!)
|
||||
PAGE: 打开任意包含正文段落块的页面（如首页/快速入门）
|
||||
TARGET_BLOCK: 第一个正文段落块（普通文本段落）
|
||||
|
||||
STEPS (≤6):
|
||||
1. 登录并进入工作区
|
||||
2. 点击侧边栏任意页面，打开包含正文段落块的文档
|
||||
3. 鼠标悬停在第一个段落块左侧，观察手柄是否出现
|
||||
4. 点击手柄，观察块菜单是否弹出
|
||||
5. 检查菜单布局与图标（6点/拖拽、删除、转换等图标）是否正常
|
||||
6. 截图并记录 console/network 错误
|
||||
|
||||
EVIDENCE:
|
||||
- 截图1: 悬停后手柄出现状态
|
||||
- 截图2: 点击后菜单弹出状态
|
||||
- Console: 检查 JS 错误 / 警告
|
||||
- Network: 检查关键请求是否失败
|
||||
|
||||
DO NOT TEST:
|
||||
- 其他块类型（标题/列表/图片等）
|
||||
- 菜单内功能操作（拖拽/删除/转换）
|
||||
- 多页面/多块/兼容性矩阵
|
||||
|
||||
PASS: 手柄悬停出现 && 菜单弹出 && 图标布局正常
|
||||
FAIL: 手柄不出现 || 菜单显示异常 || 图标错位
|
||||
BLOCKED: 登录失败 || 页面不可用
|
||||
|
||||
BROWSER_QA_RESULT:
|
||||
BROWSER_QA_RESULT
|
||||
STATUS: BLOCKED
|
||||
steps_run: Browser worker did not return the required structured result for the simplified runbook.
|
||||
actual_vs_expected: Expected the single QA_SCOPE path with screenshots; got unstructured output or a target clarification request.
|
||||
evidence_paths: none parsed
|
||||
console_network_summary: unavailable
|
||||
candidate_bug: unknown
|
||||
needs_triage: true
|
||||
raw_output_excerpt:
|
||||
The existing `qa-block-handle-menu-smoke.js` perfectly matches this runbook's scope. Let me run it directly.Good — `qa-block-handle-menu-smoke.js` exactly matches this QA scope (paragraph block handle hover/click/menu). Running it now.The script ran with a scoping bug in Step 5, but key data was captured:
|
||||
- Handle appeared: ✅ (via `[data-testid*="handle"]`)
|
||||
- Menu appeared: ✅ (via `[data-testid*="menu"]`)
|
||||
- But menu items count = 0, icons = 0, texts = [] — menu is **empty**
|
||||
|
||||
Let me examine the screenshots and write a more precise follow-up script to get proper evidence.Let me analyze the screenshots. These show the Wolai mindmap embed within a page. Let me read the skill and gather context before proceeding.Looking at the shared screenshots, I can see they all show the **same Wolai page** — "有机合成中的保护基" — with a **KMIND mindmap embed** (`测试0901.kmind`). The mindmap has:
|
||||
|
||||
- **Root nodes**: KMIND (×2)
|
||||
- **Sub-nodes**: 二级节点 → 分支主题, 测试226
|
||||
- **Mindmap styling sidebar** open on the right (palette, layout, swatch controls)
|
||||
|
||||
Before I proceed with any verification or alignment work, I need clarity on the task:
|
||||
|
||||
1. **Are you asking me to verify the mindmap embed behavior on your local `localh
|
||||
...[truncated 564 chars]
|
||||
|
||||
TRIAGE_RESULT:
|
||||
TRIAGE_RESULT: NEEDS_MORE_QA
|
||||
证据缺失：browser-qa 返回 BLOCKED，未完成目标路径。
|
||||
判断理由：阻塞属于 QA 执行问题，不能判定产品 bug。
|
||||
最小修复边界：N/A
|
||||
回归路径：先解决登录、选择器或页面状态阻塞，再按 QA_SCOPE 复测。
|
||||
bug 文档字段：status=needs-more-info；记录 blocked reason。
|
||||
|
||||
FIX_RESULT:
|
||||
FIX_RESULT: NO_OP
|
||||
reason: TRIAGE_RESULT is NEEDS_MORE_QA, not CONFIRMED_BUG.
|
||||
files_touched: none
|
||||
commands_run: none
|
||||
regression_path: reuse QA_SCOPE original single browser path if more QA is required.
|
||||
|
||||
REGRESSION_QA_RESULT:
|
||||
REGRESSION_QA_RESULT
|
||||
STATUS: PASS
|
||||
steps_run: skipped regression because bug-triage returned NEEDS_MORE_QA, not CONFIRMED_BUG.
|
||||
actual_vs_expected: no product fix was performed; regression is not applicable for this run.
|
||||
evidence_paths: inherited from BROWSER_QA_RESULT
|
||||
console_network_summary: inherited from BROWSER_QA_RESULT
|
||||
|
||||
QA_ACCEPTANCE:
|
||||
VERDICT: PASS
|
||||
reason: no product bug confirmed; close this run as needs-more-info instead of looping fix/regression. browserStatus=BLOCKED, regressionStatus=PASS.
|
||||
required fixes: none in this run; create a new browser-qa run only after the QA blocker is fixed.
|
||||
Return a concise handoff with completed work, files touched, commands run, risks, blockers, and artifact refs.
|
||||
|
||||
## Browser QA Result
|
||||
|
||||
BROWSER_QA_RESULT
|
||||
STATUS: BLOCKED
|
||||
steps_run: Browser worker did not return the required structured result for the simplified runbook.
|
||||
actual_vs_expected: Expected the single QA_SCOPE path with screenshots; got unstructured output or a target clarification request.
|
||||
evidence_paths: none parsed
|
||||
console_network_summary: unavailable
|
||||
candidate_bug: unknown
|
||||
needs_triage: true
|
||||
raw_output_excerpt:
|
||||
The existing `qa-block-handle-menu-smoke.js` perfectly matches this runbook's scope. Let me run it directly.Good — `qa-block-handle-menu-smoke.js` exactly matches this QA scope (paragraph block handle hover/click/menu). Running it now.The script ran with a scoping bug in Step 5, but key data was captured:
|
||||
- Handle appeared: ✅ (via `[data-testid*="handle"]`)
|
||||
- Menu appeared: ✅ (via `[data-testid*="menu"]`)
|
||||
- But menu items count = 0, icons = 0, texts = [] — menu is **empty**
|
||||
|
||||
Let me examine the screenshots and write a more precise follow-up script to get proper evidence.Let me analyze the screenshots. These show the Wolai mindmap embed within a page. Let me read the skill and gather context before proceeding.Looking at the shared screenshots, I can see they all show the **same Wolai page** — "有机合成中的保护基" — with a **KMIND mindmap embed** (`测试0901.kmind`). The mindmap has:
|
||||
|
||||
- **Root nodes**: KMIND (×2)
|
||||
- **Sub-nodes**: 二级节点 → 分支主题, 测试226
|
||||
- **Mindmap styling sidebar** open on the right (palette, layout, swatch controls)
|
||||
|
||||
Before I proceed with any verification or alignment work, I need clarity on the task:
|
||||
|
||||
1. **Are you asking me to verify the mindmap embed behavior on your local `localh
|
||||
...[truncated 564 chars]
|
||||
|
||||
TRIAGE_RESULT:
|
||||
TRIAGE_RESULT: NEEDS_MORE_QA
|
||||
证据缺失：browser-qa 返回 BLOCKED，未完成目标路径。
|
||||
判断理由：阻塞属于 QA 执行问题，不能判定产品 bug。
|
||||
最小修复边界：N/A
|
||||
回归路径：先解决登录、选择器或页面状态阻塞，再按 QA_SCOPE 复测。
|
||||
bug 文档字段：status=needs-more-info；记录 blocked reason。
|
||||
|
||||
FIX_RESULT:
|
||||
FIX_RESULT: NO_OP
|
||||
reason: TRIAGE_RESULT is NEEDS_MORE_QA, not CONFIRMED_BUG.
|
||||
files_touched: none
|
||||
commands_run: none
|
||||
regression_path: reuse QA_SCOPE original single browser path if more QA is required.
|
||||
|
||||
REGRESSION_QA_RESULT:
|
||||
REGRESSION_QA_RESULT
|
||||
STATUS: PASS
|
||||
steps_run: skipped regression because bug-triage returned NEEDS_MORE_QA, not CONFIRMED_BUG.
|
||||
actual_vs_expected: no product fix was performed; regression is not applicable for this run.
|
||||
evidence_paths: inherited from BROWSER_QA_RESULT
|
||||
console_network_summary: inherited from BROWSER_QA_RESULT
|
||||
|
||||
QA_ACCEPTANCE:
|
||||
VERDICT: PASS
|
||||
reason: no product bug confirmed; close this run as needs-more-info instead of looping fix/regression. browserStatus=BLOCKED, regressionStatus=PASS.
|
||||
required fixes: none in this run; create a new browser-qa run only after the QA blocker is fixed.
|
||||
Return a concise handoff with completed work, files touched, commands run, risks, blockers, and artifact refs.
|
||||
|
||||
## Triage Result
|
||||
|
||||
NEEDS_MORE_QA
|
||||
证据缺失：browser-qa 返回 BLOCKED，未完成目标路径。
|
||||
判断理由：阻塞属于 QA 执行问题，不能判定产品 bug。
|
||||
最小修复边界：N/A
|
||||
回归路径：先解决登录、选择器或页面状态阻塞，再按 QA_SCOPE 复测。
|
||||
bug 文档字段：status=needs-more-info；记录 blocked reason。
|
||||
|
||||
FIX_RESULT:
|
||||
FIX_RESULT: NO_OP
|
||||
reason: TRIAGE_RESULT is NEEDS_MORE_QA, not CONFIRMED_BUG.
|
||||
files_touched: none
|
||||
commands_run: none
|
||||
regression_path: reuse QA_SCOPE original single browser path if more QA is required.
|
||||
|
||||
REGRESSION_QA_RESULT:
|
||||
REGRESSION_QA_RESULT
|
||||
STATUS: PASS
|
||||
steps_run: skipped regression because bug-triage returned NEEDS_MORE_QA, not CONFIRMED_BUG.
|
||||
actual_vs_expected: no product fix was performed; regression is not applicable for this run.
|
||||
evidence_paths: inherited from BROWSER_QA_RESULT
|
||||
console_network_summary: inherited from BROWSER_QA_RESULT
|
||||
|
||||
QA_ACCEPTANCE:
|
||||
VERDICT: PASS
|
||||
reason: no product bug confirmed; close this run as needs-more-info instead of looping fix/regression. browserStatus=BLOCKED, regressionStatus=PASS.
|
||||
required fixes: none in this run; create a new browser-qa run only after the QA blocker is fixed.
|
||||
Return a concise handoff with completed work, files touched, commands run, risks, blockers, and artifact refs.
|
||||
|
||||
## Fix Result
|
||||
|
||||
NO_OP
|
||||
reason: TRIAGE_RESULT is NEEDS_MORE_QA, not CONFIRMED_BUG.
|
||||
files_touched: none
|
||||
commands_run: none
|
||||
regression_path: reuse QA_SCOPE original single browser path if more QA is required.
|
||||
|
||||
REGRESSION_QA_RESULT:
|
||||
REGRESSION_QA_RESULT
|
||||
STATUS: PASS
|
||||
steps_run: skipped regression because bug-triage returned NEEDS_MORE_QA, not CONFIRMED_BUG.
|
||||
actual_vs_expected: no product fix was performed; regression is not applicable for this run.
|
||||
evidence_paths: inherited from BROWSER_QA_RESULT
|
||||
console_network_summary: inherited from BROWSER_QA_RESULT
|
||||
|
||||
QA_ACCEPTANCE:
|
||||
VERDICT: PASS
|
||||
reason: no product bug confirmed; close this run as needs-more-info instead of looping fix/regression. browserStatus=BLOCKED, regressionStatus=PASS.
|
||||
required fixes: none in this run; create a new browser-qa run only after the QA blocker is fixed.
|
||||
Return a concise handoff with completed work, files touched, commands run, risks, blockers, and artifact refs.
|
||||
|
||||
## Regression QA Result
|
||||
|
||||
REGRESSION_QA_RESULT
|
||||
STATUS: PASS
|
||||
steps_run: skipped regression because bug-triage returned NEEDS_MORE_QA, not CONFIRMED_BUG.
|
||||
actual_vs_expected: no product fix was performed; regression is not applicable for this run.
|
||||
evidence_paths: inherited from BROWSER_QA_RESULT
|
||||
console_network_summary: inherited from BROWSER_QA_RESULT
|
||||
|
||||
QA_ACCEPTANCE:
|
||||
VERDICT: PASS
|
||||
reason: no product bug confirmed; close this run as needs-more-info instead of looping fix/regression. browserStatus=BLOCKED, regressionStatus=PASS.
|
||||
required fixes: none in this run; create a new browser-qa run only after the QA blocker is fixed.
|
||||
Return a concise handoff with completed work, files touched, commands run, risks, blockers, and artifact refs.
|
||||
|
||||
## QA Acceptance
|
||||
|
||||
VERDICT: PASS
|
||||
reason: no product bug confirmed; close this run as needs-more-info instead of looping fix/regression. browserStatus=BLOCKED, regressionStatus=PASS.
|
||||
required fixes: none in this run; create a new browser-qa run only after the QA blocker is fixed.
|
||||
Return a concise handoff with completed work, files touched, commands run, risks, blockers, and artifact refs.
|
||||
+180
@@ -0,0 +1,180 @@
|
||||
# Browser QA needs-more-info
|
||||
|
||||
- workflow_run_id: fcaefa85-5cb9-45d6-b238-4d52cca03e97
|
||||
- status: needs-more-info
|
||||
- triage: NEEDS_MORE_QA
|
||||
|
||||
## QA Scope
|
||||
|
||||
MINIMAL_BROWSER_QA_RUNBOOK
|
||||
- Target URL: http://localhost:3000
|
||||
- Login: click "测试账号快速登录" (mnote.e2e@example.com)
|
||||
- Target page: 任意已存在或新建的文档页，含至少一个正文段落块（非标题、非列表、非代码块）
|
||||
- Target block: 该页面中第一个普通段落块
|
||||
- Operations (max 6):
|
||||
1. 打开页面，等待编辑器加载完成
|
||||
2. 鼠标悬停（hover）在该段落块左侧空白区域，等待手柄出现
|
||||
3. 截图1：手柄出现时的整体布局（包含段落块、手柄图标、周围元素）
|
||||
4. 点击该手柄
|
||||
5. 等待块菜单弹出，不移动鼠标
|
||||
6. 截图2：块菜单弹出后的完整布局（含菜单所有图标、文字、与段落块的位置关系）
|
||||
- Console/Network: 截图前打开 DevTools Console，记录所有 error/warning；检查 Network 中是否有 4xx/5xx 请求
|
||||
- Required screenshots: 2（hover 手柄出现 + 点击后菜单弹出）
|
||||
- Exclusions: 不测试其他块类型（标题、列表、代码块、图片等）；不测试拖拽、删除、复制等菜单操作；不测试其他页面；不测试移动端；不测试 theme 切换
|
||||
- PASS/FAIL/BLOCKED:
|
||||
PASS: 手柄 hover 后正常出现，点击后菜单弹出且菜单图标/文字完整可见、无重叠、无截断，无 console error 且无 4xx/5xx
|
||||
FAIL: 手柄未出现、菜单未弹出、菜单布局错乱（图标缺失、重叠、截断、位置偏移严重）、出现 console error 或 4xx/5xx
|
||||
BLOCKED: 页面无法加载、编辑器未渲染、无法登录、段落块不存在
|
||||
|
||||
BROWSER_QA_RESULT:
|
||||
BROWSER_QA_RESULT
|
||||
STATUS: BLOCKED
|
||||
steps_run: phase boundary failed before structured evidence could be collected.
|
||||
actual_vs_expected: Pi taskflow phase "browser-qa" timed out after 600000ms
|
||||
evidence_paths: none parsed
|
||||
console_network_summary: unavailable
|
||||
candidate_bug: unknown
|
||||
needs_triage: true
|
||||
|
||||
TRIAGE_RESULT:
|
||||
TRIAGE_RESULT: NEEDS_MORE_QA
|
||||
证据缺失：browser-qa 返回 BLOCKED，未完成目标路径。
|
||||
判断理由：阻塞属于 QA 执行问题，不能判定产品 bug。
|
||||
最小修复边界：N/A
|
||||
回归路径：先解决登录、选择器或页面状态阻塞，再按 QA_SCOPE 复测。
|
||||
bug 文档字段：status=needs-more-info；记录 blocked reason。
|
||||
|
||||
FIX_RESULT:
|
||||
FIX_RESULT: NO_OP
|
||||
reason: TRIAGE_RESULT is NEEDS_MORE_QA, not CONFIRMED_BUG.
|
||||
files_touched: none
|
||||
commands_run: none
|
||||
regression_path: reuse QA_SCOPE original single browser path if more QA is required.
|
||||
|
||||
REGRESSION_QA_RESULT:
|
||||
REGRESSION_QA_RESULT
|
||||
STATUS: PASS
|
||||
steps_run: skipped regression because bug-triage returned NEEDS_MORE_QA, not CONFIRMED_BUG.
|
||||
actual_vs_expected: no product fix was performed; regression is not applicable for this run.
|
||||
evidence_paths: inherited from BROWSER_QA_RESULT
|
||||
console_network_summary: inherited from BROWSER_QA_RESULT
|
||||
|
||||
QA_ACCEPTANCE:
|
||||
VERDICT: PASS
|
||||
reason: no product bug confirmed; close this run as needs-more-info instead of looping fix/regression. browserStatus=BLOCKED, regressionStatus=PASS.
|
||||
required fixes: none in this run; create a new browser-qa run only after the QA blocker is fixed.
|
||||
Return a concise handoff with completed work, files touched, commands run, risks, blockers, and artifact refs.
|
||||
|
||||
## Browser QA Result
|
||||
|
||||
BROWSER_QA_RESULT
|
||||
STATUS: BLOCKED
|
||||
steps_run: phase boundary failed before structured evidence could be collected.
|
||||
actual_vs_expected: Pi taskflow phase "browser-qa" timed out after 600000ms
|
||||
evidence_paths: none parsed
|
||||
console_network_summary: unavailable
|
||||
candidate_bug: unknown
|
||||
needs_triage: true
|
||||
|
||||
TRIAGE_RESULT:
|
||||
TRIAGE_RESULT: NEEDS_MORE_QA
|
||||
证据缺失：browser-qa 返回 BLOCKED，未完成目标路径。
|
||||
判断理由：阻塞属于 QA 执行问题，不能判定产品 bug。
|
||||
最小修复边界：N/A
|
||||
回归路径：先解决登录、选择器或页面状态阻塞，再按 QA_SCOPE 复测。
|
||||
bug 文档字段：status=needs-more-info；记录 blocked reason。
|
||||
|
||||
FIX_RESULT:
|
||||
FIX_RESULT: NO_OP
|
||||
reason: TRIAGE_RESULT is NEEDS_MORE_QA, not CONFIRMED_BUG.
|
||||
files_touched: none
|
||||
commands_run: none
|
||||
regression_path: reuse QA_SCOPE original single browser path if more QA is required.
|
||||
|
||||
REGRESSION_QA_RESULT:
|
||||
REGRESSION_QA_RESULT
|
||||
STATUS: PASS
|
||||
steps_run: skipped regression because bug-triage returned NEEDS_MORE_QA, not CONFIRMED_BUG.
|
||||
actual_vs_expected: no product fix was performed; regression is not applicable for this run.
|
||||
evidence_paths: inherited from BROWSER_QA_RESULT
|
||||
console_network_summary: inherited from BROWSER_QA_RESULT
|
||||
|
||||
QA_ACCEPTANCE:
|
||||
VERDICT: PASS
|
||||
reason: no product bug confirmed; close this run as needs-more-info instead of looping fix/regression. browserStatus=BLOCKED, regressionStatus=PASS.
|
||||
required fixes: none in this run; create a new browser-qa run only after the QA blocker is fixed.
|
||||
Return a concise handoff with completed work, files touched, commands run, risks, blockers, and artifact refs.
|
||||
|
||||
## Triage Result
|
||||
|
||||
NEEDS_MORE_QA
|
||||
证据缺失：browser-qa 返回 BLOCKED，未完成目标路径。
|
||||
判断理由：阻塞属于 QA 执行问题，不能判定产品 bug。
|
||||
最小修复边界：N/A
|
||||
回归路径：先解决登录、选择器或页面状态阻塞，再按 QA_SCOPE 复测。
|
||||
bug 文档字段：status=needs-more-info；记录 blocked reason。
|
||||
|
||||
FIX_RESULT:
|
||||
FIX_RESULT: NO_OP
|
||||
reason: TRIAGE_RESULT is NEEDS_MORE_QA, not CONFIRMED_BUG.
|
||||
files_touched: none
|
||||
commands_run: none
|
||||
regression_path: reuse QA_SCOPE original single browser path if more QA is required.
|
||||
|
||||
REGRESSION_QA_RESULT:
|
||||
REGRESSION_QA_RESULT
|
||||
STATUS: PASS
|
||||
steps_run: skipped regression because bug-triage returned NEEDS_MORE_QA, not CONFIRMED_BUG.
|
||||
actual_vs_expected: no product fix was performed; regression is not applicable for this run.
|
||||
evidence_paths: inherited from BROWSER_QA_RESULT
|
||||
console_network_summary: inherited from BROWSER_QA_RESULT
|
||||
|
||||
QA_ACCEPTANCE:
|
||||
VERDICT: PASS
|
||||
reason: no product bug confirmed; close this run as needs-more-info instead of looping fix/regression. browserStatus=BLOCKED, regressionStatus=PASS.
|
||||
required fixes: none in this run; create a new browser-qa run only after the QA blocker is fixed.
|
||||
Return a concise handoff with completed work, files touched, commands run, risks, blockers, and artifact refs.
|
||||
|
||||
## Fix Result
|
||||
|
||||
NO_OP
|
||||
reason: TRIAGE_RESULT is NEEDS_MORE_QA, not CONFIRMED_BUG.
|
||||
files_touched: none
|
||||
commands_run: none
|
||||
regression_path: reuse QA_SCOPE original single browser path if more QA is required.
|
||||
|
||||
REGRESSION_QA_RESULT:
|
||||
REGRESSION_QA_RESULT
|
||||
STATUS: PASS
|
||||
steps_run: skipped regression because bug-triage returned NEEDS_MORE_QA, not CONFIRMED_BUG.
|
||||
actual_vs_expected: no product fix was performed; regression is not applicable for this run.
|
||||
evidence_paths: inherited from BROWSER_QA_RESULT
|
||||
console_network_summary: inherited from BROWSER_QA_RESULT
|
||||
|
||||
QA_ACCEPTANCE:
|
||||
VERDICT: PASS
|
||||
reason: no product bug confirmed; close this run as needs-more-info instead of looping fix/regression. browserStatus=BLOCKED, regressionStatus=PASS.
|
||||
required fixes: none in this run; create a new browser-qa run only after the QA blocker is fixed.
|
||||
Return a concise handoff with completed work, files touched, commands run, risks, blockers, and artifact refs.
|
||||
|
||||
## Regression QA Result
|
||||
|
||||
REGRESSION_QA_RESULT
|
||||
STATUS: PASS
|
||||
steps_run: skipped regression because bug-triage returned NEEDS_MORE_QA, not CONFIRMED_BUG.
|
||||
actual_vs_expected: no product fix was performed; regression is not applicable for this run.
|
||||
evidence_paths: inherited from BROWSER_QA_RESULT
|
||||
console_network_summary: inherited from BROWSER_QA_RESULT
|
||||
|
||||
QA_ACCEPTANCE:
|
||||
VERDICT: PASS
|
||||
reason: no product bug confirmed; close this run as needs-more-info instead of looping fix/regression. browserStatus=BLOCKED, regressionStatus=PASS.
|
||||
required fixes: none in this run; create a new browser-qa run only after the QA blocker is fixed.
|
||||
Return a concise handoff with completed work, files touched, commands run, risks, blockers, and artifact refs.
|
||||
|
||||
## QA Acceptance
|
||||
|
||||
VERDICT: PASS
|
||||
reason: no product bug confirmed; close this run as needs-more-info instead of looping fix/regression. browserStatus=BLOCKED, regressionStatus=PASS.
|
||||
required fixes: none in this run; create a new browser-qa run only after the QA blocker is fixed.
|
||||
Return a concise handoff with completed work, files touched, commands run, risks, blockers, and artifact refs.
|
||||
Reference in New Issue
Block a user