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/unified-shell-route-coverage/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.6 KiB
Raw Blame History

ADDED Requirements

Requirement: In-scope routes SHALL be shell-contract governed

All in-scope modernization routes SHALL be represented in shell route contracts, loader registration policy, and navigation visibility governance.

Scenario: In-scope coverage validation

  • WHEN shell route contract validation is executed
  • THEN every in-scope route SHALL have route metadata, ownership metadata, and visibility policy metadata
  • THEN missing in-scope route contracts SHALL fail validation

Scenario: Admin route inclusion

  • WHEN shell navigation is built for admin users
  • THEN /admin/pages and /admin/performance SHALL be represented as governed navigation targets according to visibility/access policy

Requirement: Out-of-scope routes SHALL not block this phase

Routes explicitly marked as out-of-scope for this modernization phase SHALL be excluded from required shell-coverage gates in this phase.

Scenario: Deferred route exclusion

  • WHEN modernization gates execute for this phase
  • THEN /tables, /excel-query, /query-tool, and /mid-section-defect SHALL be treated as deferred routes
  • THEN deferred route absence from new shell-governance gates SHALL NOT fail this phase

Requirement: Route coverage governance SHALL be CI-enforced

Route coverage and contract completeness checks for in-scope routes SHALL run as CI gates.

Scenario: CI gate failure on in-scope gap

  • WHEN CI detects an in-scope route without required contract metadata
  • THEN the modernization gate SHALL fail
  • THEN release promotion SHALL be blocked until resolved