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/rollback_controls.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

926 B
Raw Blame History

Full Modernization Rollback Controls

Route-Level Reversion Controls

  • PORTAL_SPA_ENABLED=false: Disable shell-first navigation runtime globally.
  • Route-scoped contract fallback: Mark route contract with fallback strategy and redeploy shell assets.
  • Content cutover feature flag: Disable route-level modernized content path while keeping shell runtime up.

False-Positive Gate Handling

  1. Capture failing gate output and route impact.
  2. Confirm whether failure is test flake or product defect.
  3. If false-positive and production risk is high:
  • Temporarily switch gate severity from block to warn.
  • Record waiver with owner, reason, expiry.
  1. Restore block mode after corrective action.

Required Rollback Evidence

  • Incident timestamp and impacted routes.
  • Gate IDs that triggered rollback.
  • Route contract state before/after rollback.
  • Manual acceptance and known-bug replay references.