egg/DashBoard
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity
Files
7cb0985b1228dcb69f33c865827658605a843cac
DashBoard/openspec/changes/archive/2026-02-12-full-modernization-architecture-blueprint/specs/frontend-quality-gate-modernization/spec.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

1.4 KiB
Raw Blame History

ADDED Requirements

Requirement: Modernization releases SHALL pass multi-dimensional frontend quality gates

In-scope modernization releases SHALL pass functional, visual, accessibility, and performance gates before promotion.

Scenario: Gate bundle at release candidate

  • WHEN a release candidate includes in-scope modernization changes
  • THEN it SHALL execute functional behavior parity checks for affected routes
  • THEN it SHALL execute critical-state visual regression checks for affected routes
  • THEN it SHALL execute accessibility checks for keyboard and reduced-motion behavior
  • THEN it SHALL execute performance budget checks for defined shell/route thresholds

Requirement: Gate failures SHALL block release promotion

Blocking quality gates SHALL prevent release promotion for in-scope modernization changes.

Scenario: Blocking gate failure

  • WHEN any mandatory modernization quality gate fails
  • THEN release promotion SHALL be blocked until the failure is resolved or explicitly waived per governance policy

Requirement: Deferred routes SHALL be excluded from this phase gate baseline

The route baseline for this modernization phase SHALL exclude deferred routes.

Scenario: Deferred route baseline exclusion

  • WHEN gate baseline is computed for this phase
  • THEN /tables, /excel-query, /query-tool, and /mid-section-defect SHALL be excluded from mandatory modernization gate coverage