40 行
1.1 KiB
Markdown
40 行
1.1 KiB
Markdown
# Implementation Plan
|
|
|
|
## Sequence
|
|
|
|
1. Confirm explicit user approval for public deployment.
|
|
2. Run deployment preflight checks:
|
|
- clean working tree
|
|
- client build
|
|
- UI design rules
|
|
- `git diff --check`
|
|
3. Deploy with safe env boundary:
|
|
- `SYNC_ENV=0 bash deploy/trialrun/deploy.sh`
|
|
- do not sync or overwrite remote `.env`
|
|
4. Run post-deploy public checks:
|
|
- live smoke readiness
|
|
- permission matrix
|
|
- OAFRONT3 PC readonly visual matrix
|
|
- mobile entry matrix
|
|
- WeCom rendering matrix
|
|
5. Save/redact report references under this task research directory.
|
|
6. If green, conclude `READY_FOR_TRIAL_START_CONFIRMATION`.
|
|
|
|
## Stop Conditions
|
|
|
|
- User has not explicitly approved deployment.
|
|
- Working tree is dirty outside the task.
|
|
- Deployment script fails.
|
|
- Public `/ready` fails.
|
|
- Permission matrix has issues.
|
|
- PC visual matrix has P1 blocker.
|
|
- Any report contains sensitive data.
|
|
|
|
## Safety Boundaries
|
|
|
|
- No production `.env` overwrite.
|
|
- No real payment.
|
|
- No Enterprise WeChat writes.
|
|
- No true business write automation.
|
|
- No database reset, restore, or manual migration.
|