egg/DashBoard
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity
Files
7cb0985b1228dcb69f33c865827658605a843cac
DashBoard/openspec/changes/deferred-route-modernization-follow-up/specs/page-content-modernization-safety/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.5 KiB
Raw Blame History

MODIFIED Requirements

Requirement: Deferred-route content modernization SHALL remain contract-first

Before deferred routes are cut over to modernized implementations, each route SHALL define filter/query/data-state contracts and critical interaction expectations.

Scenario: Deferred-route contract baseline defined

  • WHEN /tables, /excel-query, /query-tool, or /mid-section-defect enters modernization
  • THEN a route-level baseline SHALL capture filter input semantics, query payload shape, and critical state expectations

Requirement: Deferred-route cutover SHALL require parity + manual acceptance

Deferred routes SHALL NOT complete cutover without parity evidence and explicit manual sign-off.

Scenario: Parity and sign-off before route progression

  • WHEN a deferred route reports implementation complete
  • THEN golden fixture parity checks and interaction parity checks SHALL pass
  • THEN manual acceptance checklist sign-off SHALL be recorded
  • THEN next deferred route cutover SHALL be blocked until sign-off is complete

Requirement: Legacy bug carry-over SHALL be blocked for deferred routes

Known legacy bugs in deferred-route migrated scope SHALL be replayed during acceptance and SHALL block sign-off if reproduced.

Scenario: Deferred-route bug replay gate

  • WHEN deferred-route manual acceptance executes
  • THEN known-bug replay checks SHALL run
  • THEN reproduced known bugs SHALL fail route sign-off and block legacy retirement