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/asset-readiness-and-fallback-retirement/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.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