G1-G6 同步 R6 前置规约与最佳实践

.agents/skills/hyb-oa-delivery/SKILL.md

@@ -12,7 +12,9 @@ Use this skill when working in `/home/shunli/Projects/hyb-oa` or when the user a
 Read only what is relevant:
 
 - Always read `AGENTS.md` and the newest relevant `issues/*.csv`.
-- For UI/page work, read `docs/product-design-rules.md` and `references/visual-qa.md`.
+- After R5, first check the main R5/R6 contract status before planning trial-run or follow-up work; R5 must remain the completed gate and R6 must have its own Issue CSV before expanding scope.
+- For UI/page work, PC/mobile/WeCom experience, approval UX, or domestic OA benchmarking, read `docs/product-design-rules.md` and `references/visual-qa.md`.
+- For approval workflow, roles, self-approval, notification, deeplink, reminder, or escalation work, read `docs/需求-统一审批中心规约.md`.
 - For reimbursement, invoice, OCR, duplicate invoice, or attachment work, read `docs/reimbursement-invoice-rules.md` and `references/reimbursement.md`.
 - For local/WeCom/public trial-run, OCR runtime, Caddy, or DB drift work, read `docs/trialrun-runbook.md` and `references/trialrun.md`.
 - For how this skill should evolve, read `docs/agent-development-practices.md`.
@@ -32,10 +34,10 @@ Default behavior:
 ## Delivery Loop
 
 1. Check `git status --short`; do not revert unrelated user changes.
-2. Identify or create the current Issue CSV before non-trivial work.
+2. Identify or create the current Issue CSV before non-trivial work; after R5, distinguish R6 preparation from actual trial-run execution.
 3. State the implementation approach before editing code; if already approved, proceed.
 4. Keep changes scoped to the current Issue.
-5. Prefer existing project patterns and official SDKs.
+5. Prefer existing project patterns, official SDKs, and principles from documented domestic OA/approval/mobile references; do not copy competitor flows or text directly.
 6. Verify with the narrowest relevant automated tests, then expand by risk.
 7. Use Playwright screenshots or visual metrics for PC/mobile/WeCom UI changes.
 8. Update Issue CSV statuses only after the stated `Test_Method` passes.
@@ -92,3 +94,11 @@ Final responses should include:
 - 面向用户可测改动的部署状态：commit hash、公网 URL、`/ready`、公网前端资源/文案检查，以及用户现在是否可以测试。
 - What remains blocked and why.
 - Commit hashes when commits were made.
+
+## R6 and Trial-Run Defaults
+
+- R6 can start only from a new Issue CSV that fixes users, roles, time window, rollback contact, issue log, and daily closeout rhythm.
+- R6 scope defaults to reimbursement, leave, procurement, approval, Enterprise WeChat entry/notification, finance payment/export.
+- Do not expand to budget, ERP, AI, full travel, or complex BPM during R6; record those as follow-up Issues.
+- Enterprise WeChat personal app message is the formal approval notification channel after R5; mock and group bots are not acceptance evidence for R6 business notification.
+- Approval-chain correctness can be proven by PC or automation, while Enterprise WeChat validates entry, binding,免登录, notification, deeplink, and mobile layout.