egg/DashBoard
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity
Files
5b358d71c1bd2344ec57c0c50c65c69cf42893de
DashBoard/docs/migration/full-modernization-architecture-blueprint/rollout_runbook.md
egg 7cb0985b12 feat(modernization): full architecture blueprint with hardening follow-up 
Implement phased modernization infrastructure for transitioning from
multi-page legacy routing to SPA portal-shell architecture, plus
post-delivery hardening fixes for policy loading, fallback consistency,
and governance drift detection.

Key changes:
- Add route contract enrichment with scope/visibility/compatibility policies
- Canonical 302 redirects from legacy direct-entry to /portal-shell/ routes
- Asset readiness enforcement and runtime fallback retirement for in-scope routes
- Shared feature-flag helpers (env > config > default) replacing duplicated _to_bool
- Defensive copy for lru_cached policy payloads preventing mutation corruption
- Unified retired-fallback response helper across app and blueprint routes
- Frontend/backend route-contract cross-validation in governance gates
- Shell CSS token fallback values for routes rendered outside shell scope
- Local-safe .env.example defaults with production recommendation comments
- Legacy contract fallback warning logging and single-hop redirect optimization

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-12 11:26:02 +08:00

1.1 KiB
Raw Blame History

Full Modernization Rollout Runbook

Phase Sequence

  1. Governance freeze
  • Confirm route_scope_matrix.json has no pending route-scope changes.
  • Confirm exception registry entries include owner + milestone.
  1. Route governance enforcement
  • Run route contract completeness checks in warn mode.
  • Fix all in-scope metadata gaps.
  • Promote route governance checks to block mode.
  1. Style/content hardening
  • Apply style isolation checks for in-scope routes.
  • Execute parity checks and manual acceptance route-by-route.
  • Run known-bug replay checks per route.
  1. Asset/gate enforcement
  • Validate in-scope asset readiness.
  • Run quality gate suite (functional, visual, accessibility, performance).
  • Promote gate severity from warn to block according to policy.

Hold Points

  • Hold-1: Any in-scope route missing contract metadata.
  • Hold-2: Any unresolved style exception past milestone.
  • Hold-3: Any parity failure or known-bug replay failure.
  • Hold-4: Any mandatory quality gate failure in block mode.

Promotion Rule

Promotion is allowed only when all hold points are clear and no deferred-route checks were incorrectly included as blockers.