hyb-oa/.trellis/tasks/05-28-frontend-ux-wave3-business-mobile/implement.md

Implementation Plan

Current Decision

This task is a Wave3 refresh after the newer Wave0-2 baseline, not a blank Wave3 rebuild.

Recommended Implementation Order

1. PC detail surfaces:
   • WorkflowTaskDetailPage
   • ProjectDetailPage
   • ContractsRegistryPage
2. Mobile key surfaces:
   • MobileApprovalsPage
   • MobileNotificationsPage
   • MobileReimbursementsPage
   • MobileReimbursementDetailPage
   • MobilePurchaseRequestDetailPage only for deeplink/detail consistency
3. Test baseline:
   • update focused Wave3 Playwright spec
   • run typecheck/build/design rules/trellis gates
4. Deployment:
   • only after user approval
   • run trialrun deploy and public checks

Guardrails

• No backend, schema, permission or workflow-state changes.
• Do not remove existing business actions.
• Do not add a new contract detail route in this task.
• For mobile pages, no desktop tables, no horizontal overflow and no sticky action overlap.

Completed Implementation

2026-05-29:

• Refreshed PC workflow task detail with a next-action command panel, clearer title/subtitle and evidence-oriented side meta.
• Refreshed PC project detail with a current project command panel covering next action, closure, risk and evidence counts.
• Refreshed PC contract registry with lifecycle summary metrics, expiring-contract command area and ledger row styling.
• Refreshed mobile approvals, notifications, reimbursements, reimbursement detail and purchase detail with mobile focus summaries.
• Cleaned residual forbidden UI copy in Sidebar and Portal home so the UI design rule scan has zero findings.
• Extended client/tests/e2e/pc-detail-mobile-visual-wave3.spec.ts to cover project detail, contract registry, mobile reimbursement detail and mobile purchase detail.

Local Verification

• cd client && npm run build passed on 2026-05-29.
• cd client && npx playwright test tests/e2e/pc-detail-mobile-visual-wave3.spec.ts --workers=1 --reporter=list passed: 2 tests.
• node scripts/qa/check-ui-design-rules.mjs passed with 0 findings.
• python3 ./.trellis/scripts/task.py validate 05-28-frontend-ux-wave3-business-mobile passed.
• node scripts/qa/check-trellis-governance.mjs passed.
• git diff --check passed.

Public Deployment Verification

2026-05-29 deployment and public verification were completed after explicit user approval.

• Commit deployed: 2b5fd6b 重构 Wave3 详情与移动体验（05-28-frontend-ux-wave3-business-mobile）.
• Deploy command: SYNC_ENV=0 LIVE_SMOKE_BASE_URL=https://oa.hyinda.com bash deploy/trialrun/deploy.sh.
• Deploy script passed env contract, remote build, migration check, config seed, trialrun seed, /ready, external dependency smoke, runtime smoke and public bundle copy scan.
• Deploy note: rsync reported one non-fatal leftover historical artifacts/qa-flow/... directory that could not be deleted because it was non-empty.
• Public readiness passed: run-live-smoke-readiness.sh wrote report research/postdeploy-20260529-wave3-public/live-smoke-readiness/.
• Readiness note: pending OCR was skipped because the local script environment did not include DATABASE_URL; live OCR sample execution itself passed with the expected duplicate/same-invoice style sample result.
• OAOPS1 passed: run-oa-real-use-daily.sh wrote report research/postdeploy-20260529-wave3-public/oa-real-use-daily/ with status PASS_OA_REAL_USE_DAILY_READY.
• OAOPS1 steps passed: public ready, live smoke env, live readiness, OA-only smoke readiness, feature flags, authenticated read-only probe, mobile entry matrix, WeCom rendering matrix, WeCom entry and report privacy smoke.
• Public automation stayed read-only: no business writes, file uploads, exports, WeCom writes, payment execution or database reset.

Spec Update Decision

No .trellis/spec/ update is needed for this task. The deployed change did not add or change API signatures, schema, env keys, permission rules, Enterprise WeChat write behavior or deployment command contracts; the existing deployment-trialrun.md, docs-and-evidence.md and security-privacy.md specs already cover the evidence and privacy handling used here.