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/specs/asset-readiness-and-fallback-retirement/spec.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.0 KiB
Raw Blame History

MODIFIED Requirements

Requirement: Deferred-route assets SHALL be release-ready before promotion

Deferred routes SHALL adopt release-time asset-readiness checks and SHALL fail promotion when required assets are missing.

Scenario: Deferred-route readiness validation

  • WHEN release artifacts are prepared for follow-up phase promotion
  • THEN required assets for /tables, /excel-query, /query-tool, and /mid-section-defect SHALL be validated
  • THEN missing required assets SHALL fail release gating

Requirement: Deferred-route runtime fallback SHALL be retired by governed policy

Deferred routes SHALL not remain on runtime fallback posture after follow-up modernization completion criteria are met.

Scenario: Deferred-route fallback retirement

  • WHEN a deferred route passes readiness + parity + manual acceptance gates
  • THEN runtime fallback posture for that route SHALL be retired according to milestone policy
  • THEN rollback control SHALL remain available via explicit route-level governance switch