/root/.openclaw/workspace/scripts/wpp-as-role DEV git -C /root/.openclaw/workspace/repos/weirsoe-party-protocol ls-remote --heads origin
/root/.openclaw/workspace/scripts/wpp-as-role DEV git -C /root/.openclaw/workspace/repos/weirsoe-party-protocol push --dry-run origin HEAD:refs/heads/dev/preflight-issue-201
/root/.openclaw/workspace/scripts/wpp-as-role DEV ./.venv/bin/python manage.py test lobby.tests.UiScreenTests.test_legacy_templates_are_used_when_spa_flag_is_off lobby.tests.UiScreenTests.test_host_screen_can_render_angular_shell_when_feature_flag_enabled lobby.tests.UiScreenTests.test_host_screen_deeplink_preserves_spa_path_when_feature_flag_enabled lobby.tests.UiScreenTests.test_player_screen_can_render_angular_shell_when_feature_flag_enabled
Closes #201
## Summary
- add explicit staging rollout checklist for `USE_SPA_UI` cutover
- define smoke-gate criteria before flag activation
- document rollback checkpoints + required evidence fields for staging smoke artifact
## Validation
- `/root/.openclaw/workspace/scripts/wpp-as-role DEV git -C /root/.openclaw/workspace/repos/weirsoe-party-protocol ls-remote --heads origin`
- `/root/.openclaw/workspace/scripts/wpp-as-role DEV git -C /root/.openclaw/workspace/repos/weirsoe-party-protocol push --dry-run origin HEAD:refs/heads/dev/preflight-issue-201`
- `/root/.openclaw/workspace/scripts/wpp-as-role DEV ./.venv/bin/python manage.py test lobby.tests.UiScreenTests.test_legacy_templates_are_used_when_spa_flag_is_off lobby.tests.UiScreenTests.test_host_screen_can_render_angular_shell_when_feature_flag_enabled lobby.tests.UiScreenTests.test_host_screen_deeplink_preserves_spa_path_when_feature_flag_enabled lobby.tests.UiScreenTests.test_player_screen_can_render_angular_shell_when_feature_flag_enabled`
✅ Rollout-checklist for USE_SPA_UI in staging is clearly documented (docs/spa-cutover-flag.md).
✅ Smoke-gate criteria are explicit and actionable before enabling flag (docs/UI_SMOKE.md + artifact template updates).
✅ Rollback path to legacy (USE_SPA_UI=false) is documented with verification + logging expectations.
Risk assessment:
Docs-only change (no runtime code/tests affected), so regression risk is low.
Guidance is consistent with issue #201 scope (staging prep only, no prod cutover policy change).
No blockers found.
Independent review (issue #201 acceptance):
- ✅ Rollout-checklist for `USE_SPA_UI` in staging is clearly documented (`docs/spa-cutover-flag.md`).
- ✅ Smoke-gate criteria are explicit and actionable before enabling flag (`docs/UI_SMOKE.md` + artifact template updates).
- ✅ Rollback path to legacy (`USE_SPA_UI=false`) is documented with verification + logging expectations.
Risk assessment:
- Docs-only change (no runtime code/tests affected), so regression risk is low.
- Guidance is consistent with issue #201 scope (staging prep only, no prod cutover policy change).
No blockers found.
Review notes (independent QA against issue #201 acceptance):
✅docs/spa-cutover-flag.md now contains a clear staging rollout checklist for USE_SPA_UI.
✅ Smoke-gate criteria before activation are explicit and testable.
✅ Rollback checkpoints and post-rollback verification to legacy routes are documented.
Assessment:
Docs-only PR (no runtime code changes), low regression risk.
Scope aligns with #201 (staging prep + verification criteria; no prod-cutover policy change).
No blockers from review side.
Review notes (independent QA against issue #201 acceptance):
- ✅ `docs/spa-cutover-flag.md` now contains a clear staging rollout checklist for `USE_SPA_UI`.
- ✅ Smoke-gate criteria before activation are explicit and testable.
- ✅ Rollback checkpoints and post-rollback verification to legacy routes are documented.
Assessment:
- Docs-only PR (no runtime code changes), low regression risk.
- Scope aligns with #201 (staging prep + verification criteria; no prod-cutover policy change).
No blockers from review side.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Closes #201
Summary
USE_SPA_UIcutoverValidation
/root/.openclaw/workspace/scripts/wpp-as-role DEV git -C /root/.openclaw/workspace/repos/weirsoe-party-protocol ls-remote --heads origin/root/.openclaw/workspace/scripts/wpp-as-role DEV git -C /root/.openclaw/workspace/repos/weirsoe-party-protocol push --dry-run origin HEAD:refs/heads/dev/preflight-issue-201/root/.openclaw/workspace/scripts/wpp-as-role DEV ./.venv/bin/python manage.py test lobby.tests.UiScreenTests.test_legacy_templates_are_used_when_spa_flag_is_off lobby.tests.UiScreenTests.test_host_screen_can_render_angular_shell_when_feature_flag_enabled lobby.tests.UiScreenTests.test_host_screen_deeplink_preserves_spa_path_when_feature_flag_enabled lobby.tests.UiScreenTests.test_player_screen_can_render_angular_shell_when_feature_flag_enabledIndependent review (issue #201 acceptance):
USE_SPA_UIin staging is clearly documented (docs/spa-cutover-flag.md).docs/UI_SMOKE.md+ artifact template updates).USE_SPA_UI=false) is documented with verification + logging expectations.Risk assessment:
No blockers found.
LGTM
Review notes (independent QA against issue #201 acceptance):
docs/spa-cutover-flag.mdnow contains a clear staging rollout checklist forUSE_SPA_UI.Assessment:
No blockers from review side.