egg/DashBoard
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity
Files
5b358d71c1bd2344ec57c0c50c65c69cf42893de
DashBoard/docs/migration/deferred-route-modernization-follow-up/rollout_runbook.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.7 KiB
Raw Blame History

Deferred Route Modernization Rollout Runbook

Upstream Reference

  • Phase 1 runbook: docs/migration/full-modernization-architecture-blueprint/rollout_runbook.md

Phase Sequence

  1. Governance freeze
  • Confirm route_scope_matrix.json has deferred routes promoted to in-scope.
  • Confirm pre-change confirmations recorded for all 4 routes.
  • Confirm exception registry has no unresolved blocking entries.
  1. Route governance enforcement
  • Run route contract completeness checks in warn mode.
  • Fix all deferred-route metadata gaps.
  • Promote route governance checks to block mode.
  1. Per-route content modernization (sequential)
  • Enable content cutover flag for first route (/tables).
  • Execute parity checks and manual acceptance.
  • Run known-bug replay checks.
  • On pass: sign off and proceed to next route.
  • On fail: rollback flag and investigate.
  1. Cutover sequence
  • /tables -> /excel-query -> /query-tool -> /mid-section-defect
  • Next route blocked until current route has approved sign-off.
  1. Asset/gate enforcement
  • Validate deferred route asset readiness.
  • Run quality gate suite (functional, visual, accessibility, performance).
  • Promote gate severity from warn to block per milestones.
  1. Fallback retirement
  • Retire runtime fallback for deferred routes after all acceptance gates pass.

Hold Points

  • Hold-1: Any deferred route missing contract metadata or pre-change confirmation.
  • Hold-2: Any parity failure or known-bug replay failure.
  • Hold-3: Any mandatory quality gate failure in block mode.
  • Hold-4: Cutover attempted before previous route sign-off complete.

Promotion Rule

Promotion is allowed only when all hold points are clear for the current route in sequence.