egg/DashBoard
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity
Files
c38b5f646a46239b1701cac82a6ab30463088336
DashBoard/docs/migration/deferred-route-modernization-follow-up/rollback_controls.md
egg c38b5f646a feat(modernization): promote deferred routes to in-scope and unify page header styles 
Promote /tables, /excel-query, /query-tool, /mid-section-defect from
deferred to full shell-governed in-scope routes with canonical redirects,
content contracts, governance artifacts, and updated CI gates.

Unify all page header gradients to #667eea → #764ba2 and h1 font-size
to 24px for visual consistency across all dashboard pages. Remove
Native Route-View dev annotations from job-query, excel-query, and
query-tool headers.

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

1.4 KiB
Raw Blame History

Deferred Route Modernization Rollback Controls

Route-Level Reversion Controls

  • Content cutover feature flag: Set content_cutover_enabled: false in data/modernization_feature_flags.json for the affected route to immediately revert to legacy content path.
  • PORTAL_SPA_ENABLED=false: Disable shell-first navigation runtime globally (affects all routes).
  • Route-scoped contract fallback: Mark route contract with fallback strategy and redeploy shell assets.

Per-Route Rollback Procedure

  1. Set content_cutover_enabled: false for the affected route in modernization_feature_flags.json.
  2. Restart workers to pick up the flag change.
  3. Verify legacy content path is serving correctly.
  4. Record rollback in manual acceptance records with reason and timestamp.
  5. Investigate root cause before re-enabling cutover.

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 route.
  • Gate IDs that triggered rollback.
  • Feature flag state before/after rollback.
  • Manual acceptance and known-bug replay references.