egg/DashBoard
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity
Files
c38b5f646a46239b1701cac82a6ab30463088336
DashBoard/openspec/changes/archive/2026-02-12-deferred-route-modernization-follow-up/proposal.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

2.1 KiB
Raw Blame History

Why

full-modernization-architecture-blueprint intentionally deferred these routes:

  • /tables
  • /excel-query
  • /query-tool
  • /mid-section-defect

Those routes still run on legacy posture (direct-entry-first + fallback continuity + mixed style ownership). A dedicated follow-up change is required to finish modernization without reopening scope in phase 1.

What Changes

  • Promote all deferred routes to first-class in-scope shell-governed targets.
  • Apply canonical shell routing policy and explicit direct-entry compatibility behavior for each deferred route.
  • Modernize deferred route page-content flow (filters/charts/interactions) with contract-first parity gates.
  • Require route-by-route pre-change confirmation records before any implementation work starts on each deferred route.
  • Apply the same mandatory manual acceptance + BUG revalidation blocking policy used in phase 1.
  • Move deferred routes from fallback-era runtime posture to asset-readiness + governed retirement posture.

Capabilities

Modified Capabilities

  • unified-shell-route-coverage: deferred routes become in-scope and CI-blocking for route contract completeness.
  • spa-shell-navigation: deferred routes adopt canonical shell entry policy and governed compatibility behavior.
  • page-content-modernization-safety: deferred routes require contract baselines, parity evidence, manual sign-off, and known-bug revalidation.
  • asset-readiness-and-fallback-retirement: deferred routes adopt release-time asset checks and governed fallback retirement milestones.

Impact

  • Frontend route modules for /tables, /excel-query, /query-tool, /mid-section-defect.
  • Shell contract and navigation governance in frontend/src/portal-shell/**.
  • Backend route handlers serving deferred routes and compatibility behavior.
  • Quality gate artifacts, runbook updates, and rollout/rollback policy for deferred-route cutover.
  • Scope boundary clarification: this follow-up explicitly targets deferred routes (currently dev in page status) and does not require routes to already be released before modernization.