oa-frontend-postdeploy-public-verification 建档公网稳态验证方案

这个提交包含在:
2026-05-26 17:37:46 +08:00
父节点 892de7dd34
当前提交 126629f6db
共修改 5 个文件,包含 205 行新增和 0 行删除
@@ -0,0 +1,39 @@
# 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.