hyb-oa/issues/2026-04-29_10-14-27-r78-reimbursement-payment-tail.csv

"ID","Title","Description","Acceptance","Test_Method","Tools","Dev_Status","Review1_Status","Regression_Status","Files","Dependencies","Notes"
"A1","R78 执行合同建档与范围冻结","创建并校验 R78 合同，范围仅覆盖“报销 approved -> 创建支付批次 -> 复核 -> 执行 -> 报销 paid -> AP/支付批次页可见结果”本地 focused regression；不包含真实 ERP 出站、企微、HTTPS、高风险二次复核。","issues/2026-04-29_10-14-27-r78-reimbursement-payment-tail.csv 列完整并通过校验；A2-A5 依赖顺序清晰；Notes 明确本轮无 Prisma 迁移、无外部环境专项。","命令：`python3 /home/shunli/.codex/skills/plan/scripts/validate_issues_csv.py issues/2026-04-29_10-14-27-r78-reimbursement-payment-tail.csv`。检查：12 列完整、Dependencies 为 JSON 数组字符串、Files 为实际路径或哨兵值。","manual","DONE","DONE","DONE","issues/2026-04-29_10-14-27-r78-reimbursement-payment-tail.csv","[]","回滚路径：删除本 CSV；不影响业务运行。2026-04-29：合同已写入并通过 validate_issues_csv.py 校验。"
"A2","支付批次报销付款后端回归补齐","围绕 `paymentBatches` 的 reimbursement execute 路径补 focused 后端测试，覆盖 approved 报销进入批次后执行支付、报销变 paid、已绑定发票归档、失败条件与 maker-checker 边界；必要时补最小修复与专用回归脚本。","新增或补强的后端测试能稳定覆盖 reimbursement payment batch happy path；执行后报销状态/付款字段/发票归档行为正确；不引入 schema 变更。","命令：`cd server && npm run prisma:validate && node --check src/routes/paymentBatches.js && node --check src/routes/reimbursements.js && npm test -- tests/unit/routes/paymentBatches.reimbursement.test.js`。业务：approved 报销进入 payment batch，execute 后 reimbursement=paid，关联发票 archived。","manual","DONE","DONE","DONE","server/src/routes/paymentBatches.js|server/src/routes/reimbursements.js|server/tests/unit/routes/paymentBatches.reimbursement.test.js|server/scripts/regression-payment-batches.sh","[""A1""]","涉及付款状态流与票据归档，回滚路径：回退 payment batch reimbursement 执行逻辑改动、删除新增测试与脚本。2026-04-29：已补 payment batch reimbursement route 回归 3 条用例，覆盖 happy path、maker-checker 边界与 invalid pay status 失败路径；并补 `server/scripts/regression-payment-batches.sh`。当前 reimbursement payment batch 成功路径会在支付后补 ERP outbox 与已付款通知。"
"A3","报销支付批次 Playwright 主链路补齐","新增 focused E2E：员工创建并提交流程、经理/财务审批、finance 创建 reimbursement payment batch、finance_mgr 复核、finance 执行、验证 PaymentBatchesPage / ApOperationsPage / reimbursement detail 的下游结果一致；若本地 trialrun 默认种子未打开 payment batch / erp sync，则补最小可复现的本地开关引导。","新增 Playwright 用例通过；至少验证 1) 批次从 draft/reviewed 到 executed；2) 报销单状态变 paid；3) 支付后票据进入 archived；4) AP/支付批次页能看到执行结果；5) ERP preview 可见 pending outbox；6) 本地 focused 回归可通过显式开关重复启动，不依赖手工改库。","命令：`cd client && E2E_BASE_URL=http://127.0.0.1:3002 npx playwright test tests/e2e/reimbursement-payment-batch-flow.spec.ts --workers=1 --reporter=list`。业务：employee->manager->finance->finance_mgr 四角色完成低风险报销支付批次闭环。","playwright","DONE","DONE","DONE","client/tests/e2e/reimbursement-payment-batch-flow.spec.ts|client/tests/e2e/helpers/auth.ts|client/tests/e2e/helpers/navigation.ts|client/src/pages/PaymentBatchesPage.tsx|client/src/pages/ApOperationsPage.tsx|server/src/scripts/seed-trialrun.js","[""A2""]","优先复用现有 reimbursement / workflow / invoice helper；若现有 UI 标识不足，仅补最小测试可观测性。本地 focused finance 回归不改变默认试运行上线建议，只允许显式 opt-in 打开 `payment_batch_v1`、`erp_sync`。2026-04-29：已补 `reimbursement-payment-batch-flow.spec.ts`，并通过 `TRIALRUN_EXTRA_FORCE_ON_FLAGS='payment_batch_v1 erp_sync'` 重复 seed 在 `http://127.0.0.1:3002` 跑通 focused E2E；覆盖 draft/reviewed/executed、reimbursement=paid、invoice=archived、ERP preview pending outbox。"
"A4","付款状态流与权限 reviewer 复核","对 A2-A3 做独立复核，重点检查 maker-checker、payment.batch.manage 与 risk.review.manage 权限边界、报销 paid 与发票 archived 状态流、以及 AP/批次页是否误放大入口。","review 结论覆盖：1) finance 不能自审自己创建的批次；2) finance_mgr 复核后 finance 可执行；3) 失败路径不会错误归档发票；4) AP/批次页未新增越权操作。","人工 review：对照 server/src/routes/paymentBatches.js、server/src/routes/reimbursements.js 与新增 Playwright/单测断言输出 reviewer 结论；若发现权限/状态回归，A5 前必须先修复。","manual","DONE","DONE","DONE","server/src/routes/paymentBatches.js|server/src/routes/reimbursements.js|client/tests/e2e/reimbursement-payment-batch-flow.spec.ts","[""A2"",""A3""]","本 Issue 只输出 review 结论，不扩展新需求。2026-04-29 reviewer 结论：`paymentBatches` 复核路由继续拦截 maker 自审与二次复核人冲突；`PaymentBatchesPage` / `ApOperationsPage` 仍按 `payment.batch.manage` 与 `risk.review.manage` 分离入口；focused 单测确认 invalid reimbursement status 不会错误归档发票，也不会误入 ERP / 通知 follow-up；本轮无阻塞问题。"
"A5","R78 回归收口与覆盖矩阵回填","执行 R78 post-check，回填合同、coverage matrix 与试运行报告，明确‘报销/票据/OCR’域剩余缺口是否仅剩外部专项与高风险付款场景。","A2-A4 通过后，R78 CSV 状态回填完整；coverage matrix 与 manual trialrun report 结论一致；可明确说明本地试运行对财务付款后链路的覆盖边界。","命令：`cd server && ./scripts/regression-payment-batches.sh`；`cd client && E2E_BASE_URL=http://127.0.0.1:3002 npx playwright test tests/e2e/reimbursement-payment-batch-flow.spec.ts --workers=1 --reporter=list`。业务：汇总批次执行、报销 paid、AP/支付批次结果与报告回填。","manual|playwright","DONE","DONE","DONE","issues/2026-04-29_10-14-27-r78-reimbursement-payment-tail.csv|artifacts/r75/coverage-matrix.csv|artifacts/r70/manual-trialrun-report.md","[""A4""]","若 R78 通过，下一步再决定是否单开高风险二次复核专项；本轮不进入真实 ERP/企微/HTTPS。2026-04-29：`./scripts/regression-payment-batches.sh` 与 focused Playwright 均通过；coverage matrix 已将报销/票据/OCR 域提升为 done，并把 payment batch / AP happy path 收口到 partial_done；manual trialrun report 已补 R78 财务支付尾链结论。"