Skip to content

R9 phase A desktop validation batch - #4

Draft
mycyg wants to merge 10 commits into
mainfrom
codex/r9-stage-a-desktop-validation
Draft

R9 phase A desktop validation batch#4
mycyg wants to merge 10 commits into
mainfrom
codex/r9-stage-a-desktop-validation

Conversation

@mycyg

@mycyg mycyg commented Jul 6, 2026

Copy link
Copy Markdown
Owner

Phase A desktop-validation branch for the remaining batch2-5 commits after PR #3 merged the safe prefix.\n\nScope:\n- Five desktop commits are preserved as separate commits and each is marked 待真机验证.\n- Includes the remaining Cuu proposal title, DB repository guard tests, OpenAPI mutation contract, and R9 test-integrity audit commits.\n- No R9.0+ army commits are included.\n\nLocal validation before push:\n- pnpm -r typecheck: PASS\n- pnpm test: PASS\n- pnpm qa:r2-release-gate: PASS (README 183/183, secret_like_diff_count=0)\n- pnpm audit:migrations: PASS\n- PATH=$HOME/.cargo/bin:$PATH pnpm qa:r4-rust-system-i18n: PASS\n- R1 PG smoke on Docker temp db workhub_r9_desktop_validation_20260706: PASS ok=true/run_status=succeeded; temp db dropped\n- pnpm qa:r4-web-live-route-interaction: PASS ok=true/steps=80\n- git diff --check / git diff --cached --check: PASS\n\nMerge status:\n- Draft only. Do not merge until a real macOS .app validation confirms desktop glass/animation/vibrancy behavior.

mycyg and others added 10 commits July 6, 2026 19:18
发布版 Tauri 窗内搜索框选字仍触发窗口拖拽(真机发现 3-2):
- .wh-spot-field 显式 -webkit-app-region:no-drag(翻转旧钉死断言,原断言迁就了误行为)
- isSpotlightDragExcludedPointer 补 excludedElements 几何兜底(事件 retarget
  不可靠时按已知文本控件 bounds 判定),并在 mousedown/pointerdown 两处接线

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
mycyg pushed a commit that referenced this pull request Jul 16, 2026
Execute-class action-card items that couldn't be dispatched (enqueue/notify
failed after the work item existed) only marked the row `escalated` and never
wrote an ai_decisions row — so the failure never reached the decision inbox and
had no recovery entry, while decide-class items always fell an escalation.

Separate work-item creation from dispatch so a failure still has a work_item to
hang an escalation on: create a real escalation_event (trigger unqualified,
suggested lead = assignee, handoff tagged execute_dispatch_failed), push the
work item to escalated, and post a hand-off system note. The owner-less !assignee
corner stays escalated-without-work-item, matching the decide path.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant