R7P 准备扩大试运行草案与运维培训材料

2026-05-12 17:58:49 +08:00
@@ -107,4 +107,4 @@ Final responses should include:
 - Role-specific pages should use one shared OA/mobile framework and tailor summaries, entries, actions, and sensitive fields by role. Do not create unrelated UI systems for employee, approver, finance, admin, or CEO views.
 - After MUD6, `R6-ISSUE-001` is treated as resolved based on representative real-device confirmation; future mobile regressions should be recorded as new Issues rather than reopening the old WCM6/MME6 gate unless the same production behavior returns.
 - After AP6, approval reminder, overdue reminder, and workflow productivity summary are current product facts, not open planning items. Reuse `POST /api/workflow/tasks/:taskId/remind`, `GET /api/workflow/tasks/summary`, `job:workflow-overdue-reminders`, existing workflow history, audit logs, notifications, and WeCom personal app delivery semantics. Do not add a parallel reminder channel, change approval status from reminders, or expand into complex BPM/SLA escalation without a new Issue.
- After RI6 and LP6, the default next implementation batch is ME6 mobile second-pass experience, then QG6 QA governance, then a new R7 expanded-trialrun preparation contract. Keep existing ME6/QG6 CSV contracts instead of creating duplicate roadmap contracts. If ME6 automation/deployment is done but representative real-device testing is paused, keep `ME6-3` open and allow only non-business QG6 governance, documentation, and R7 draft preparation; do not treat QG6 as a real-device substitute and do not start real R7 without a dedicated Issue CSV plus user-confirmed participants, roles, window, rollback contact, and daily closeout.
+- After RI6, LP6, ME6 automation, QG6, and R7/OPS7/DOC7 draft materials, keep `ME6-3` open until representative real-device testing passes or the user explicitly accepts that risk. R7 draft rows may be `DONE`, but `R7E-*` true execution rows must stay `TODO` until the user confirms participants, roles, window, rollback contact, issue owner, and daily closeout. Do not treat QG6 or public mobile visual automation as a real-device substitute, and do not start real R7 from documentation alone.