# Implementation Plan

## Sequence

1. Finish task planning artifacts and validate the Trellis task.
2. Build the second wave before/after comparison:
   - Capture "before" screenshots from the commit before `5f10b83`.
   - Capture "after" screenshots from current `main`.
   - Use the existing Playwright mock visual suites so business data is synthetic.
   - Write `output/playwright/frontend-simplification-wave2-compare/index.html`.
3. Run deployment preflight checks:
   - frontend typecheck/build
   - UI design rule checker
   - deployment env contract checker
   - `git diff --check`
4. Deploy with the approved safe command:
   - `SYNC_ENV=0 bash deploy/trialrun/deploy.sh`
5. Run post-deploy readonly verification:
   - live smoke readiness
   - permission matrix
   - PC readonly visual matrix
   - mobile entry matrix
   - WeCom rendering matrix
6. Record a concise postdeploy summary under `research/`, using only relative report references and redacted conclusions.
7. Run Trellis governance and final whitespace check.

## Screenshot Strategy

- Prefer a temporary git worktree for the "before" commit so the current working tree remains intact.
- Do not use destructive checkout/reset commands in the main worktree.
- Reuse test-generated screenshots where available:
  - `output/playwright/pc-core-workflow-visual-wave2/`
  - `output/playwright/pc-detail-mobile-visual-wave3/`
- If the old and new screenshot filenames differ, normalize them by copying the selected images into the comparison output directory with stable names.

## Stop Conditions

- Unexpected dirty files outside the current task or generated comparison output.
- Deployment script fails.
- Public `/ready` fails.
- Permission matrix reports a blocker.
- PC readonly visual matrix reports a P1 blocker.
- Any generated report contains secrets, raw payloads, full accounts or full local paths.

## Safety Boundaries

- No remote `.env` overwrite.
- No real business write automation.
- No Enterprise WeChat writes.
- No real payment, bank import or ERP write.
- No database reset, restore or manual migration.
- No production config edits.